The following books will

[mstfizbdt32]

At the same time, in different sources, the same types of tests may calle differently, and the list will supplemente or, conversely, truncate. testing Each test is performe for a specific purpose, not just to test the overall performance of the application. In general, you nee to make sure that it works correctly in any or certain circumstances and meets the state requirements, as well as user expectations. These will the goals of the experiments. Testing steps include Analysis of the software to teste. Studying product requirements and user expectations.

Development of test script and checkpoint. At this stage, it is important to fix how quality control will carrie out and what indicators determine it. Development of test documentation. Prototype Job Function Email List test optional. Testing process. Processing of test results. Bug reports. Refinement base on test results. Verification test. Test formalization error reporting, reports. you nee to develop a test plan a document describing all the work and topics of the tests, strategies, and criteria for starting and ending tests. The test plan answers the following questions what nees to teste.



What is actually being teste? There is an IEEE standard that defines a set of documents to use in each step of the test. In general, familiarity with the IEEE Software Life Cycle and the set of standards will helpful for working in depth with the software. Test design. During this phase, test scripts are develope and implemente according to previously establishe criteria. Two main questions are solve WHAT to test and HOW? Determination of ranges, analysis of limit values, causal relationships all this is include in this step.