TAILIEUCHUNG - Testing Computer Software phần 10

Các chuyên viên kiểm thử sẽ rất cảm kích những lời khuyên của tác giả bởi tính hiệu quả của sự phân tích, báo cáo về lỗi kỹ thuật, bởi kiểm thử hộp đen (Black-box Testing), tính tương thích của máy in. Mang tính thực tế và định hướng thực tiễn, quyển sách chỉ ra vô số đường dẫn và mẹo kinh doanh, bao gồm cả những cách giảm thiểu rủi ro cho sản phẩm và hơn nữa là chi phí kiểm thử sản phẩm bằng các thử nghiệm mang tính trật tự hiệu quả. . | Test all data files including clip art templates tutorials samples etc. Testers almost always underestimate the time this takes. Try a small representative group of files and clock your time. Work out the average and multiply it by the number of files to check. This gives you the time required for one cycle of testing of these files. You must also estimate the time required to retest revised files. Make the testing status clear and get Problem Report issues resolved Circulate summary and status reports that summarize open problems and provide various project statistics. You have probably already been circulating reports like these but as the project progresses there are probably more reports prepared more formally and circulated to more senior people in the company. Use good sense with statistics. Don t treat the number of open reports and newly reported problems as meaningful and important without further interpretation. This late in the schedule senior manage ment will believe you or act as if they believe you to put pressure on the project manager . These numbers convey false impressions. For more discussion see Chapter 6 Users of the tracking system Senior managers. Be careful when you add testers near the end of the project A new tester who writes a stack of reports that essentially say this Amiga program should follow Macintosh user interface rules is wasting valuable last minute time. Late-joining testers who combine enthusiasm poor judgment and obsti nacy can cost a project much more than they benefit it. Circulate lists of deferred problems and call or participate in meetings to review the deferrals. By beta or soon after these meetings should be weekly. Later they might be every few days. It s important to get these decisions considered now rather than a day or two before shipping the product. Highlight any reports you want reconsidered pick your appeals carefully. Circulate a Hit of open user interface design issues and call or join in a review meeting

Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.