Shulou(Shulou.com)06/03 Report--

Click the link to join QQ Group 522720170 (free open courses and videos): https://jq.qq.com/?_wv=1027&k=5C08ATe

Brief introduction of acceptance Test

1.1 introduction

The acceptance test is carried out by the product developer according to all the contents of the requirements document provided by Sina (or the requirements promised by the other party according to the contract and other valid agreements), the internal test is completed, and the submitted version meets the acceptance test standards. a test conducted by Sina's quality assurance department. Through the acceptance test to determine whether the product quality meets the product requirements, whether the function is correct and can be finally put online.

1.2 role definition

Acceptance submitter: product developer

Acceptance recipient: Sina quality Assurance Department

two。 Purpose of acceptance test

Through the acceptance test to determine whether the product quality meets the product requirements, whether the functional implementation is correct, whether the performance and safety meet the release standards, and the product can finally go online.

3. Acceptance test version

3.1 Test version naming

The product version submitted for acceptance test is uniformly named in the following format: product name _ version _ ATx is defined as follows:

Product name: the name of the product submitted for testing, such as "easy favorites" (EasyShareFolder)

Version: the version number of the product that submitted the test, for example, "1.0.1"

ATx: where "AT" means Acceptance testing; "x" indicates the number of acceptance tests submitted, such as 1, 2, 3, etc.

Example: EasyShareFolder_1.0.1_AT1 (indicates the first version of the acceptance test submitted by "easy favorites")

3.2 Test version save

The version submitted for each acceptance test is saved to the version library of Sina's main product, and the online version is subject to the approved version of the acceptance test.

4. Acceptance test range

4.1 Interface testing

All page browsing, correct connection, correct display of all function buttons and interface

4.2 functional testing

All the functions described in the requirements documents are implemented correctly.

4.3 performance test

Key business functions and performance can meet the needs of online operation.

4.4 Security testing

Interfaces and data calls comply with security specifications; there are no security vulnerabilities

5. Acceptance testing process

The basic workflow of acceptance testing is as follows:

5.1. Admission condition detection

5.1.1 documentation

The documentation for entering the acceptance test is complete:

A) requirements document for the acceptance version (provided by the submitter): the requirement document is required to match exactly with the program that finally submitted the acceptance test

B) acceptance version of the test case (provided by the submitter): requires the test case to cover the requirements document of the final version

C) acceptance version of the test notice (provided by the submitter): state the overall test situation, defect list and fixes in the test report

5.1.2 defects

The developer is required to conduct a comprehensive test of all the functions mentioned in the document in a WindowsXP IE6 / IE7/Firefox3.x compatible environment (the compatibility requirements will change according to the circumstances of the project, whichever is required by Sina), and all defects found by the developer have been resolved when the acceptance test is submitted.

5.1.3 Test environment

The acceptance test environment is ready to complete, which is consistent with the online real environment

Our project leader is responsible for the control of the test environment to ensure the consistency and stability of the environment during the test.

5.1.4 Communication and contact

1. The contact information of the person in charge of the developer who submitted the acceptance test and the contact information of the test engineer are complete.

two。 The communication channel for submitting acceptance test defects has been established, which requires fast, accurate and timely feedback.

5.2 acceptance testing

5.2.1 document acceptance

Entry criteria: document preparation must be complete and meet the standards, and you can enter the document acceptance process.

Interruption criteria:

1. The requirements document is not the final version, and the functional program described in the requirements document has not been implemented

two。 The test case does not match the requirements document, the modules tested in the test case do not exist in the requirements document, or the functional modules in the requirements document are not reflected in the test case

3. The test report is incomplete and the number of legacy defects does not meet the allowable limit of legacy defects

Exit criteria:

The document meets the standard and passes the acceptance, and enters the process of program acceptance.

5.2.2 functional acceptance of the program

Entry criteria: end of document acceptance process

Interruption criteria:

1. There is a grade B defect in AMagol.

2. There are 10 C-level defects (depending on the size of the project)

3. Submit a new version during acceptance testing

Exit criteria:

The acceptance test is qualified, and the defect is repaired according to the standard.

Adopt the standard:

After the completion of the acceptance test, the acceptance can only be passed when the unresolved defects meet the following requirements:

A) Class A defects: 0

B) Class B defects: 0

C) Class C defects: less than or equal to 3% of the total number of defects

D) Class D defects: 5% or less of the total number of defects

E) Class E defects: 15% less than or equal to the total number of defects.

Note: for the proposal to give up treatment, it must be agreed by us in advance.

5.2.3 acceptance completed

1. The documents submitted by the quality Assurance Department after the completion of acceptance:

A) final requirements document

B) the final test case provided by the submitter

C) the final test report provided by the submitter

D) final acceptance test report provided by the quality Assurance Department

2. Submit the procedure after the completion of acceptance:

The final version of the locked program is completed after acceptance and is required to be saved to our version library.

Appendix: defect level definition

Defects are divided into 5 levels: a, B, C, D and E.

Level

Description

Class A

Operating system crash

Serious lack of function

The program cannot be run

Class B

The main functions cannot be realized.

Program crash

Main page text error

Debug information was not cleared

Class C

The function implementation is not in accordance with the requirement specification.

The function cannot be realized, but it does not affect the use.

Program logic error

Serious inconvenience for users

Class D

The function is realized, but it is inconvenient to use.

Prompt information is not uniform

The layout of the interface is not in line with user habits.

Class E

Prompt message text error

Negotiable page layout

Overall program hue

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.