Software Testing Process Reference one

1. Preparation phase

The Test manager needs to evaluate the test effort and evaluate the test time. Based on the test workload and estimated time analysis, it may be necessary to report to the customer in a timely manner and ask the customer to confirm the test scope and other relevant information. For the final project progress, the test supervisor, the Test manager and the project manager are required to agree on the communication.
The test plan is the primary test document, which can be referenced by the test glossary creation, the author of the test plan cannot self-review the test plan, must be reviewed by the test lead or Test manager, and the customer is finally confirmed.
Before you create a test case, you need to list all the functional areas of the test. The test risk analysis and prioritization of tests are then conducted separately and submitted to the customer or Test manager for approval.
Creating a test case is another major part of the preparation phase that can be created either manually or by using test management tools. The test case that you create must first be reviewed and approved by at least one Test lead, and then the customer is finally approved.

Prepare and set up test environment including software, hardware, network.

Testing human resources is another important test resource, and you need to create a human resources requirements curve document that lists the testers needed for each phase of the test. To maintain the stability of testers.

2. Implementation phase

Transfer and submit the software build and test cases used by the test from the project, project manager or customer to the test department, depending on the project.

After the test department gets the new test build, it first executes the version acceptable test (BAT). If the requirements of the test are met, then go to the regular testing stage and if the build has a big problem, such as a failure to install or a major function invalidation, it needs to be reported to the customer in a timely manner, requiring the new build to be recompiled.

The test execution is performed according to the test plan and test case, and a defect report is written to report the software defect to the customer-specified software defect tracking management system.

The Test team makes internal quality assurance QA of the software test content and reported defects weekly, and reports to the quality Manager or Test Manager for quality assurance findings, and takes corrective action in a timely manner.

At the same time, the customer side of the quality engineer also carry out external tracking and inspection. For any test problems that the customer finds, the team needs to analyze it carefully and take corrective action in a timely manner. All corrective actions have to be discussed by all parties to form corrective action reports, signed and confirmed by the Test Manager.

During the test, keep track of the latest estimated test time and actual test time taken, and take the necessary steps to meet the progress of the test project initially set. Analyze test software defects to measure test coverage and test effectiveness.

Some problems identified during the testing process need to be reported and confirmed to the customer in a timely manner. Such as

First here today, I hope you can help the management of software quality. Other articles you might be interested in:

Design ideas of Internet database architecture
Enterprise Application Architecture mode N-tier multi-tier architecture
An enterprise social application network topology architecture diagram
IT Infrastructure planning scenario one (network system planning)
Food chain Company It informatization solution One
Rest Service Introduction
Enterprise Service Bus Introduction

If you want to know more software development, system it integration, Enterprise informatization, project management and other information, please follow my subscription number:

Petter Liu
Source: http://www.cnblogs.com/wintersun/
This article is copyright to the author and the blog Park, Welcome to reprint, but without the consent of the author must retain this paragraph, and in the article page obvious location to the original link, otherwise reserves the right to pursue legal responsibility.
The article was also published in my Independent blog-petter Liu blog.

Software Testing Process Reference one