Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Phần này sẽ bao gồm việc phát triển các kế hoạch thử nghiệm của bạn, mà tự nó đã có một số khía cạnh: Xác định những gì làm cho một thử nghiệm thành công Tổng quan về các tài liệu hướng dẫn lập kế hoạch kiểm tra các thông số trong đó bạn sẽ thử nghiệm Xác định các số liệu mà bạn sẽ thu thập dữ liệu theo dõi lỗi sự cố báo cáo và theo dõi | This material is copyright and is licensed for the sole use by Thomas Rosenblum on 4th December 2008 1010 SW High Ave. Topeka 66604 Chapter 2 Developing Your Test Plan This section will cover the development of your test plan which in itself has several aspects Determining what makes for a successful test Overview of the test plan documentation Establishing the parameters within which you will test Defining the metrics with which you will collect data Tracking bugs Incident reporting and tracking The purpose of the plan is no different than a road map it directs you to your destination. Just as you would carry a road map in your automobile for a trip to somewhere unknown you should develop a test plan. In our test plan or road map you will need to cover several items to ensure that you reach your destination. Essential Parameters for a Successful Test Purpose of This Test Why are we testing Have we upgraded and now we need to make sure it works Are we adding a brand new feature Identify in your test plan the reason for the test. If it is a simple patch then testing for what was failing will be the purpose of our test. Assume that you put in a major feature upgrade. Then you will need to test for interoperability backup and restore user documentation and potential user training. This will spawn several sub-tasks. What system s will be impacted The downstream effects of this may be small or large. In the case of an upgrade the developer is likely to have tested all the canned configurations and noted where something breaks because of the upgrade. Again your situation is unique and you are going to be running something that they might not have tested the upgrade with. In a hypothetical configuration you could be running a Search Engine Friendly SEF tool that was not tested with the upgrade of your core extension. After the upgrade if all you test for is the functionality of the upgraded extension then you may miss where the SEF extension stopped working. The .
