Test start and end notification mail templates

Test start Notification Mail template

Hi all

According to the situation of the XXX project, the XX round of XX testing will be entered from 11:30 to 18:00 on April 24, 2009. Developers are asked not to modify the test environment and keep the environment stable before the test is over.

The test plan is as follows:

Test version

Tags/xxxx

Test environment

Login address:

Visit after login:

Hosts settings:

Test range

1 return to the defects of the last wheel

2 for this round of testing, all functions except feed and notification content:

Testing strategy

Immediately after the completion of this stage of testing, enter the defect review to determine the follow-up work plan.

Tester

Defect management

1. Welcome to participate in the test.

In order to avoid repetition or invalidation, except for the test and product engineer to fill in the proposal in JIRA, please send a letter directly to xxx if you find any problems.

two。 Defect allocation

-the defect with no objection to the requirement is directly assigned to the xxx and arranged by him to solve it.

-defects that need to be identified by the product are assigned to xxx, which is confirmed to be the proposal of bug and assigned to xxx

3. Defect report

-defect library: "xxx-APP-defect library" in JIRA

-version selection: xxx's first integration test

-component selection: xxx

End of Test Notification Mail template

Hi all

The XXX round X system test (smoke test X) ends.

Test version

Xxx

Test time

XX XXX XX:XX-XX XXXX XX:XX

Test range

Tester

Test engineer + product engineer + customer service staff

Test conclusion

Analysis of the defects newly reported in this round

1. Defects are classified according to priority:

X new proposals have been found in this round, including X at B, X at C, X at D, and X at E

2. Defects are divided by module:

XX module: XX defects, of which X are C level defects

3. Defects are classified by status:

Open: XX

Resolved: XX

4. Analysis of high weight problem:

Impact statement (XXXX) (list relevant proposals)

Regression defect analysis:

A total of X proposals have been validated in this round: among them, X have been verified and X have been reopened (including proposals that have been amended after failing the verification).

Test conclusion and risk

[test failed]

1. The current system has not yet reached the online standard.

two。 Fix all newly discovered defects and reopen defects and build a new version to enter the fourth round of system testing.

3.

[test passed]

1. The current system can meet the online standard. It is recommended that all unvalidated and unfixed proposals be delayed and the code frozen.

two。 Release version: for example: xxxx

3. The test report will be given after launch.

Attachment: defect list