About test type
Jackei by 2003-11-10
Now there are still many peers for test types, test methods, and test phases. In fact, these concepts are more likely to distinguish. There is some relationship between them, such as the definition of the test phase should be the biggest, such as component testing, integration testing, system testing, which is the most common different phase test. The test method is mainly four of the four: static black boxes, dynamic black boxes, static white boxes, dynamic white boxes. The type of test is very rich: function test, performance test, integrity test, structural test, configuration test, installation test, safety test, capacity test, benchmark, competitive test, load test, intensity test, UI test, data related Sexual and integrity testing, database testing, ease of use testing, document testing, etc. However, these three concepts are associated with each other. For example, the black box method can be used for the component test phase and the integrated test phase, and a white box method can also be used; and in the system test phase, it is mainly used to use a black box test method. Note that the distinction between the black / white box here is whether or not the code is tested, not whether or not some books are in the internal implementation of the system. It can usually be done, first, clear your current test phase, is the component test phase, or integrate test phases or system testing phases, then determine that you will perform those tests - that is, the test type; final, for Different test types determine if those test techniques and test methods. Oh, here added a noun called "testing technology", including those technologies? I haven't considered it yet. In short, it can be clearly clear: test phase - test type - test method and technology. Well, in the actual work of the current project, although the Development Department is ready to use the new three-layer architecture in the next job, it is limited to the current actual situation of my technical capabilities and projects, I am still ready to limit the work to the system test. The stage, and component testing and integrated tests are not allowed to be involved in north. For many test types in system testing, it will only include 4 test types, which are defined as follows: 1. Function testing. The functional test here will include only tests related to the actual business, that is, the user works in the same way without using computer software. For the design of the function test case, you can start immediately after the requirements verification phase, and basically start with the program design of the development department. Because of this, the function test case that is completed at this stage does not have any association with the implementation, it is entirely only for the actual business - that is, the user considers what users need to do when they work. At the end of the program design and use case design phase, it is necessary to verify the test case and program design, including the correctness of the programming, and adjustment, delete, and modify the test case. So far, all completed function test cases still do not generate any association with the implementation, and the function test case should also be basically completed. The description of the use case will only include the specific business operation, and the results of the verification are required, without describing the items implemented by using those functions and methods - such as the item in the selection menu, click That Edit. Enter content. In addition, for functional testing, different subsystems are considered, and each subsystem will establish a separate directory to save. At the same time, in the above test, it is also included in the data accuracy test, usability test, but because both aspects belong to a basic functional requirement, so as not to be partially processed. Final a basic principle: Functional test will be the only standard for demand, everything comes from demand, and needs to verify other phases as a standard. 2.UI test. For UI tests, it is always the most easy to test the confusing part, where the definition of the UI test is helped by clear definition of functional testing.
In my plan, the UI test will only include content related to the ultimate implementation, and what the UI itself is related. For example, shortcut keys, prompt information, text content display, input length limit, data type limit, and so on. In summary, it is not described in the demand document, but is the content considering, it is not actual connection with the actual business of the user, and the computer has a strong part. 3. Performance test. Consider the main performance test. 4. Data correlation and integrity test. Here is mainly related to functional testing, functional testing for data guarantees of data is the accuracy and integrity of data related to the current subsystem business, and here is considered to operate in a subsystem, but can be other subsystems The data used is affected, but the current subsystem user does not care about these effects - of course, the user of another subsystem will inevitably care.
The above content is very imperfect, but also need to continue thinking.
