[test development] file compression project practice

Blog home page ： Bryant typing the code
Welcome to thumb up Collection Leaving a message. Welcome to discuss ！
This paper is written by 【 Bryant typing the code 】 original , First appeared in CSDN
Because the blogger is learning Xiaobai one , There are bound to be mistakes , If you have any questions, please leave a message in the comment area to point out , Be deeply grateful ！
Boutique column （ Update from time to time ）【JavaSE】 【Java data structure 】【LeetCode】

Review the software testing process again ：
Demand analysis ——> test plan ——> Use case design ——> Execute test case ——> Test evaluation report

Project start , Step in and understand the needs

Project background ： Not enough disk space , Need a compression 、 Unzip the file
The goal is ： Complete the compression of all file types 、 decompression .

Time ： 2018-6-1 To 2018-6-7

Members of the project ：

• project manager ： Tang's monk
• The product manager ： The Monkey King
• Development ： Pig eight quit
• test ： The sand monk

Demand analysis

functional requirement ： file type ： Support all files
Number of compressed files ： Maximum compression 100 File Compression size ： No more than 5G
Performance requirements ： Compress 、 Unzip the file no more than 30 minute
Security requirements ： Files infected with viruses cannot be compressed
Ease of use needs ： It's easy to operate 、 convenient
Interface requirements ： Layout 、 Beautiful layout
Compatibility requirements ： windows7,windows8,windows10 You can use .

Develop test plan （ plan + Strategy ）

Test scope and test points ： Compress 、 Unzip the file , A single file , Multiple files

The test method ： manual

The type of test involved ：

• function ： According to the functional test cases, all the tests shall be carried out
• performance ： Execute all according to the performance test cases
• Security ： Execute all according to the safety test cases
• compatible ： Execute all according to the compatibility test cases
• Interface ： Execute all according to the interface test cases
• Ease of use ： Execute all according to the usability test cases

Test management tools ： ZenTao

Test resources ：
plan ：

Serial number	project	Time	Those responsible
1	Demand analysis	2018-6-1	The sand monk
2	draw up a plan	2018-6-1	The sand monk
3	Write use cases	2018-6-3	The sand monk
4	Data preparation 、 Execute use cases	2018-6-4-2018-6-5	The sand monk
5	Write a report	2018-6-6	The sand monk
6	Version release and project summary	2018-6-6	The sand monk

risk : Resignation ： Personnel backup 、 Feelings stay 、 code annotation

Number of test rounds ：
First round test ： Smoke testing , Full test
The second round of testing ： Smoke testing ,BUG verification , regression testing
The third round of testing ： Smoke testing ,BUG verification , A full regression test
The fourth round of testing ： Seal test

Configuration Management ：
Upload the source code to each release ： https://github.com/broncho, And do a good job in version management
All documents produced in the project are uploaded to :svn://118.24.113.xx/

Change management ： Follow the company's change management process

Review management ： Follow the company's review management process

Entry and exit criteria
Admission test ： Smoke test passed
Out of standard ： serious 、 important BUG No legacy , commonly 、 secondary BUG Not more than in total 2 individual

Test execution process

1. Requirements testing
   The requirement based testing method is the basic testing method , The quality of requirements directly affects the subsequent development and testing work .
   Requirements review
   Requirements testing
   Requirements testing in test design
   Requirements test elements ： correctness , The need for , integrity , Uniformity
   Requirements testing should start as early as possible
2. Test the proposed version
   Smoke testing
   Information transmission in version testing ： Modify the content , Configuration Management
3. The system test
   Execute tests based on test cases
   Defect management
4. regression testing
   Confirm the return content
   Confirm that the regression method is manual
   Regression of use cases
   bug The return of the
5. Write test report
   Defect analysis
   Test conclusion

Write test cases

Such as ：

The test execution

preparation ： Compressed file data preparation
Received the first beta version ： Smoke testing , Full test
Received the second test version ： Smoke testing ,BUG verification , regression testing
Received the third test version ： Smoke testing ,BUG verification , A full regression test
Received the fourth test version ： Seal test

Defect management ： Find a flaw - Record defects - Communication deficiencies - Track defects - Close defects

Output test report

Defect analysis

Test conclusion

Version release

Published online

track 、 Collect feedback from letters

Project summary

A good project , It is worth learning from other projects ：

The project needs to be improved ：