TAILIEUCHUNG - Testing Computer Software phần 4

Làm thế nào để tìm ra những lỗi quan trọng một cách nhanh chóng? Làm thế nào để mô tả các lỗi phần mềm một cách rõ ràng? Làm thế nào để thiết kế và sử dụng hệ thống hiệu chỉnh lỗi phần mềm? Làm thế nào để tạo ra 1 kế hoạch kiểm thử với ít thủ tục giấy tờ nhất? | Our strongest recommendation for improving legibility is to use a computerized problem tracking system see Chapter 6 . Make the computer type your reports. NON-JUDGMENTAL Nobody likes being told that what they did was wrong wrong wrong. As a tester that s what you tell people every day. You can ensure your unpopularity by describing problems in a way that tells the programmer you think she is sloppy stupid or unprofessional. Even if you think she is keep it out of the report. If the programmer considers you a jerk and your reports vindictive she will want to ignore your reports and complain about you to her management. Complaints about maliciously written Problem Reports can have serious consequences. First they reduce your chances of raises and promotions and may cost you your job. Some testers think their straight nasty reporting style is more courageous than foolish. But malice leads to a justifiable movement to censor Problem Reports. Because of censorship only some reports reach the programmers and censors don t just reject inappropriate wording. They also suppress reports of problems they consider too minor or that they decide will have political repercussions they don t care to face. Once censorship starts some testers will stop reporting some classes of problems because they know that these reports will never make it past review anyway. Under these conditions many fixable problems are never reported and never fixed. Think twice and twice again before declaring war on programmers by expressing personal judgments in your reports. You will almost certainly lose that war. Even if you keep your job you will create an adversarial relationship that will cost you reporting freedom. It will not improve product quality even if every judgment you express is correct. We are not saying never express a judgment. Occasionally you may have to write a powerful bluntly worded report to alert management to a serious problem that a programmer will not acknowledge or fix. Fine.

• Kỹ thuật lập trình
• thủ thuật tin học
• mẹo hay cho windows 7
• lập trình ứng dụng windows
• ngôn ngữ lập trình
• nền tảng lập trình
• thủ thuật máy tính
• thủ thuật công nghệ thông tin
• tài liệu tin học
• thông tin công nghệ thông tin
• tuần báo Công Nghệ Thông Tin