function test that thing _ test

Contact function test has been three years, the functional testing has its own feelings and experience, the following is said function test that thing.

First, start from the beginning of testing work

When you receive a new project, the first thing you need to do is understand the test content of the project, the scope of the test, the project cycle, and the current progress of the project. According to the understanding of the project, comprehensive test resources, work out the project test plan and test strategy. When the project development has been relatively complete, you can directly carry out system testing, basically take conventional testing, system testing and regression testing to alternate. Some projects are suitable for integration testing when they have only completed the development of part of the module. If the project time is tense and the resource conditions are allowed, the agile test can also be carried out. According to the characteristics of the project, take the best test strategy.

Ii. on module partitioning and use-case writing

As we all know about Web testing, some features are based on pages. When the function and the page are merged, the partition of the module is not so easy. If divided by the page, it is easier to assign tasks, the operation is easier to control. However, duplicate or similar features appear on each page, and problems can easily result in redundant and repetitive bugs. If you divide by function, you may need to repeat on each page, and for Web page testing, the function is not very distinguished, is not obvious, and more scattered, may be an operation on multiple pages have an impact. My experience is that, in general, page partitioning takes precedence over functional module partitioning. Of course, the specific situation should also be specific analysis.

on how to write a use case, I think most of the test engineers will be more understanding of what the Equivalence class division, boundary value analysis, causality diagram, and so on, and so on the Internet, we have a lot of introductions. As long as the title of the use case, operation steps, expected results, are basically available.

Third, the testing process

When the use case is written, the project team can enter the test execution phase directly after the use case review. (for how to conduct a use-case review, two approaches have been tried, one for each evaluation and one for evaluating the use-case framework only.) The former is too time-consuming, and the latter is not detailed enough to always find the best way. I do not know whether you have any experience in this area reader. At this stage, there has been an experiment on cross testing. In the project, there is a use case written by test engineer A, assigned to B to perform, or, at the close of the project, a complementary cross test for team members. found that the latter result is better than the former. Because the former is to put the cross test in the project compared to the previous stage, under normal circumstances, engineers will be strictly in accordance with test cases to test, it is difficult to have time to dig deeper defects. The latter is to arrange the cross test to the project after the stage, most of the defects have been dug out, may be in the test, to help the divergent thinking.

Iv. Test Risk Assessment

After the test has been completed, the test lead is required to summarize the project and write the test report, in which the lessons that must be done are risk assessments. There are still a number of differences between the test environment and the formal online environment, and some modules may not be well tested in a test environment, such as data migration issues, such as the instability of third-party interfaces. For tests that are not covered, try to list them here, alerting the relevant personnel to the risk of potential problems at the lowest level.

For the functional testing process and how each stage of development, online information has a lot of many, do not elaborate, the above points are in the work, I think it is worth noting several points, I hope we can explore together.

This article is reproduced from the 51Testing Software test network, see more: http://www.51testing.com/html/news.html