Experience of soft testing experience 1--web Project test (basic process, regression test, test plan)

As a junior te with insufficient testing experience, in the last six months, we have been involved in functional side testing of 2 larger Web projects, including the test lead time and the optimized maintenance period, and of course the iterative release test continues ... ), which mainly summarizes their own experience in the process of participating in the project and a variety of pits ... Pure mark, you are also welcome to test practitioners watching brick ~) 1. Test flow:

(for reference only, personal workflow:) Web test
To participate in a new project testing, the first collection of test-related materials, including prototype drawings, various requirements documents, business-related instructions, such as to develop: Brand table, the agreed indicator calculation method, such as code table, business description and other requirements related materials, the first step to collect the requirements of the relevant information, self-familiar with the system, At the same time, the list does not understand the point, the product has a preliminary understanding of the error point, the focus of the test point list of issues; To find PM or Product manager familiar with the system, ask for a systematic introduction of the product, including the relevant implied demand points, at the same time over the previous step list of issues listed, while checking the requirements and development Test order, form test requirement, write test plan, plan and confirm with PM according to prototype diagram and requirement document, test requirement. After confirming, we begin to design the concrete use cases according to the System Summary column test case, fill in the Use Case table, and through the Equivalence class division, boundary value analysis, error speculation, scene, judgment table and so on. "Note browser compatibility, different systems (mac,windows), and whether the account is related to permissions, if any, more than a few account login to try, encountered problems in the place to reproduce bugs, to confirm the existence of the problem;" Configure the test environment, prepare the data (on-line export collation or self-designed data). The test environment includes browser-compatible, mainstream browsers, product main use environment, formal test execution, test execution according to test case, record bugs document. For bugs point, Word description, screenshots, etc.: List the problem and the corresponding recurrence condition, mark the priority, modify the time, named XX system defect record MMDD; invite PM to Bugs document notes, which are bugs points, which is the test understanding error, Which is the temporary development or the demand changes, in time to know, at the same time for bugs points, timely allocation of repair, write a brief test results, defect quantity, status, distribution and so on; after the first round of testing, the system has been more in-depth understanding, and began to follow the development iteration cycle for continuous testing, Modify the first test result, delete the fixed mark, and then add or update the bugs; Follow up the iteration test, pay attention to the regression test, the PM is required to publish the key points before each release; 2. About regression testing during project iterations-note:

1, to ensure that each release is controlled, that is, the main points of each release must be clear, to avoid untested points with the release on-line, practice: request PM or Product Manager when the column release points, go through the demand;

2, to release points to do smoke test before, to fully understand the business, to modify the point of familiarity, testing before there is a basic test method, and for the new modification point may be involved in the module, divergent thinking, to ensure complete measurement of the relevant modules involved;

3, the new module in addition to do basic smoke test, must do the correlation module and function check, especially involved in the interactive part, do adequate testing, but also include plug-in calls;

4, smoke test is completed, must do the corresponding regression test, all functional points to test in place, in the early stages of the iterative release test process, summary of the streamlined effective test set, for the subsequent optimization process will not change the basic functions, such as: login, change the password ... You can write some automated test scripts through the plugin selenium of Firefox, and also improve the efficiency of regression testing.

5, the test process, with the product manager or PM communication needs often keep, understand the product can be measured, and intermediate demand changes or system-related intermediate output can be timely access;
(Pit: Login-exit, you need to check the interception problems, such as not logged in, directly populate the URL to jump, the background there is no validation;) 3. Approximate content of the test plan

Test scenario: A document that identifies how the test will be carried out, including test plans, test environments, test data, tools, test methods, and risk dependencies.

Overview of the test Scenario reference directory (which can be appropriately truncated depending on the project or product)
Writing target Audience object Project background Test objective Reference test plan
Test content contains which modules of the system (function, performance, data) test scope test environment
Hardware environment Software Environment Test tool
Some test browser compatibility tools, automated test tools ... Test method for testing data of performance test tools
Black box (the related method to be used) white box (speaking method) smoke test acceptance test test HR scheduling Test schedule Test output
Which documents and reports are included: test plan, test scheme, System evaluation report, defect report and other risk analysis
Problems that may occur after the system is on-line, some bugs that are not yet resolved, problems that may arise in each use environment, etc. integration test cases
Interface Test System test Cases
function Test Module 1 Module 2 Module 3 ... Performance testing
Performance Test Cases