The preliminary test and discussion on the campus seal the gods list

1. Our test plan

Test Purpose:

We inevitably have some loopholes in the beginner programmer's mistakes. Testing is essential to us. In order to make the app more smooth and convenient to run, in order to improve the user's sense of experience, adhere to the test to improve.

Test tasks:

Our tests are simple: functional testing, performance testing, user interface (UI) testing, security and access control testing, compatibility testing, regression testing.

Test resources:

Role: Our "Classic users and their scenario descriptions" have been described (see Personal blogs).

Test environment:

Software Environment:

Operating system: Win7 Win8 win10

Android Development: eclipse-adt,jdk1.7

Database: mysql5.7.10

Server: myeclipse2014a jdk1.6

Hardware environment:

See "Test Matrix"

Test tools:

LoadRunner Performance testing tools, TestDirector

Test design Arrangement:

Test activity	Test tasks	Technology	Complete the standard
First Stage Functional Testing	Verify the correctness of data accuracy, data type, business functions and other related aspects.	Using black box test, boundary value test, equivalence class partition, data driven test method	95% use cases pass and top-level defects all resolved
Phase II Performance testing	High-traffic data and performance testing for multiuser operations	Automated testing	The app meets the performance requirements of the user's needs
Phase III UI Test	1. Navigation, connection, Cookie, page structure including menu, background, color, font, button name, title, consistency of information, etc. 2. Friendliness, operability (ease of use).	Common methods for web testing	The UI conforms to acceptable standards, ensures user interface friendliness, ease of operation, and conforms to user operating habits.
Stage Four Security and Q Control Test	1. Password, login, administrator, ordinary user, etc. 2. Permissions. 3. Illegal attacks. 4. Login timeout limit and so on.	Code package or illegal attack tool	Perform a variety of illegal operations without security vulnerabilities and the app is working properly.
Fifth stage Compatibility test	1. Use different versions of different browsers and resolutions to test separately; 2. Combination test of various conditions such as browser and resolution.	Black box test	It can realize its function normally under various conditions.
Sixth stage Regression test	The above test returns to re-test	Manual testing and automated testing	95% of test case executions pass the test

Number of test case estimates:

function point or test type	Maximum number of Use cases	Moderate number of Use cases	Minimum number of Use cases	Total
Module 1 (Security test)	5	3	2	3
Module 2 (Functional test)	60	50	40	50
Module 3 (Functional test)	60	50	40	50
Module 4 (Performance test)	5	3	2	3
UI Test	6	6	6	6
Regression test	136	112	90	112

Workload estimate:

Stage	Maximum workload (Person hour)	Moderate workload (Person hour)	Minimum workload (Person hour)	Total (Person hour)
Test planning	6	5	4	5
Test design	12	10	8	10
Test implementation	60	50	40	50
Test execution	45	38	33	38.3
Test summary	6	5	4	5

Staff Arrangement:

Role	Name	Task Schedule
Test Manager	Song Hailing	Test planning
Test Design Staff	Song Hailing	Test plan and user test design, test summary
Testing staff	Song Hailing, Jia Zhao, Yuhuihui, Zhangjiangpeng	Test execution

Do we need to test until our software is perfect?

Software testing is the process of building confidence in the product that causes the end user to lose risk 100

What is "good enough" for testing?

Software testing, which describes a process used to promote the correctness, completeness, security, and quality of the certified software. In other words, software testing is an audit or comparison process between the actual output and the expected output. The classic definition of software testing is the process of operating the program under prescribed conditions to detect program errors, measure software quality, and assess whether it meets design requirements.

So a good enough test should ensure the correctness, completeness, security and quality of the software.

What is the "standard for Exit"?

Test Exit Criteria
The final release date of the product is 2016 * * Month * * day. Test exit criteria to complete all the functions listed in the test requirements and regression tests for defects found during testing.

Unit Test Exit Criteria

1) Unit test case design has passed the review
2) core code 100% via code Review
3) unit test function coverage up to 100%
4) Unit test code line coverage not less than 80%
5) At least 60% of all identified defects are included in the defect tracking system and all levels of defect repair rates are up to standard
6) There is no type A, b defects
7) C, D, e-type defects allowed to exist
8) Complete the test of all the required units according to the unit test case
9) Software Unit function and design consistent
Integration Test Exit Criteria
1) Integration test Case design has passed the review
2) All source code and executable code have established a controlled baseline, included in the configuration management controlled library, without approval can not be arbitrarily changed
3) Complete the integration test of the whole system according to the integrated component plan and incremental integration strategy
4) Meet the requirements of the test plan for the coverage required for integration testing
5) Integrated work version to meet the design definition of the functions, performance requirements
6) The errors found in the integration test have been modified to meet the standard of defect repair rate at all levels
7) A, B bug cannot exist
8) C, Class D bugs are allowed, but not more than 50% of the total unit test bug.
9) Class E bug allows existence
System Test Exit Criteria
1) system test Case design has passed the review
2) system test completed according to the system test plan
3) system test function coverage up to 100%
4) The function and performance of the system to meet the requirements of product requirements Specification
5) errors found in system testing have been modified and the level of defect repair rates are up to standard
6) There is no Class A, B, C defects after the system test
7) Class D defects allowed to exist, no more than 5% of total defects
8) Class E defects allowed to exist, not exceeding 10% of total defects

Each project team defines what is your beta version "good enough"?

1. Code Error Rate 0%

2. Function Realization 98%

3. The interface is more beautiful;

4. Safety meets general requirements;

5. Stable performance, more smooth user use.

What is your test matrix?

Our test matrix:

	User type	Screen resolution	Operating system	Operating system (Default language)	Network speed	Browser	Total number of combinations
	Administrator	QVGA (240x320 pixels )	Win7	Chinese Simplified	Dial	UC Browser
	General users	HVGA (480x320 pixels )	win8.1	Chinese Traditional	Adsl	Baidu Browser
	Tourists	VGA (640x480 pixels )	Win10	English	Lan
		WVGA (800x480 pixels )
Number of variables	3	4	3	3	3	2	648

The preliminary test and discussion on the campus seal the gods list