Software Testing-Considerations

Software course testing is coming to an end, in addition to what the teacher taught in class, I searched for some information about software testing considerations.

1, carefully check whether the software test environment to build the success and stability, because the test case execution is built on this test environment, if the test environment inconsistencies, will affect the execution of test cases, and the proof of testing purposes.

2. Note the prerequisites and special instructions in the test case. Because some test software is sequential, its test cases have some implementation prerequisites or special instructions. For example, to test the landing function of a software, you must create a user before testing, and assign certain permissions to the user, and so on. If the prerequisites and special instructions are not noticed, the test case cannot be executed.

3, the test case to perform all execution, each use case at least once. Because when writing a test case, it takes into account the problem of test coverage, each test case corresponds to a function point, and if one is executed less, there is a function point that is not tested. Before we perform the test, we think that each function point of the software to be tested is not implemented, we must test each function point to ensure that the software to be tested can correctly meet the needs of users.

4, when executing the test case, to detail the actual input and output of the software system, carefully compare the actual input and the test case of the expected input is consistent. If not consistent, to test several times from multiple angles, as far as possible to pinpoint the location of the software error and cause, and test because this error will lead to more serious errors, and finally the detailed input and actual output, as well as the description of the problem to write to the test report. In a project team, the development time of the project is limited, if we can test the problem described in detail, then developers will easily reproduce the problem, will be able to solve the problem faster, save project time.

5, do not miss any accidental imagination. When we test, we sometimes find that when a use case executes, the software goes wrong, but the error is no longer reproduced when it is executed again. In this case, it is common to think that it is a coincidence that we ignore the past. In fact, this kind of error is the deepest, most difficult to find error. We want to encounter this situation, to carefully analyze this situation, do not let go of any small details, more testing several times, to accurately identify the cause of the problem.

Software Testing-Considerations