Teamwork 5 - Test and Release

Please write the software test process and test results according to the software requirements document, function description, system design and test plan in the team project, and answer the following questions.

How many bugs were found in total during testing? How many bugs are there in each category?

a. Bug fixes;

b. Bugs that cannot be reproduced

c. This product is designed like this, not a bug;

d. It has no ability to repair, and does not plan to repair it in the future;

e. This bug should indeed be fixed, but there is no time to fix it in this version, and it will be delayed until the next version.

Scenario testing, including the following:

How do you expect different users to use your software?

What are their needs and goals?

How does the functionality provided by your software fit together to meet their needs?

What platforms, hardware configurations, browser types, etc. do you test your software on? - test matrix

Performance indicators (response time and throughput, need to give screenshots and test instances and results)

System resource monitoring (CPU, memory usage, screenshots and test instances and results need to be given)

Stress test (different number of concurrent users, screenshots, test instances and results need to be given)

Fatigue test (to test the ability of the server to run continuously, screenshots and test examples and results need to be given)

Security testing (from three perspectives, namely confidentiality, availability, integrity. Screenshots and test examples and results need to be given)

serial number	completed tests	Expected performance metrics of the system	actual test results	Difference analysis	Performance issues and suggestions for improvement
001
002
003
004
005

Additional questions: The following additional questions are based on the requirements of the 4 standards and further refine the requirements

Test items	basic requirements	Refinement requirements	Score
Performance	Response time and throughput	In addition to the test of the total response time, it is also necessary to analyze the performance bottleneck. It is necessary to point out which module of the software has a serious impact on the response time. It can be considered from the calculation of the response time and the I/O response time. The smaller the granularity of the module, the better The better the concentration, the need to give screenshots and test examples and analysis
System resource monitoring	CPU and memory usage	Similar to the response time, it is necessary to give which module occupies the most CPU time and memory. The smaller the granularity of the module, the better the concentration. Screenshots, test examples, and analysis need to be given. 5
pressure test	Different concurrent users	The corresponding test script needs to be given
fatigue test	Test the server's ability to run continuously	To calculate the longest running time started from the service, you need to give the corresponding screenshot, which can be viewed from the system log
Safety test	From three perspectives, namely confidentiality, availability, integrity	Confidentiality needs to be viewed from the perspective of data confidentiality and the confidentiality of the user's use process. Ensure that the software has certain defense capabilities and can resist confidentiality attacks. Availability refers to a certain resistance to malicious attacks to ensure that the service is available and robust. Integrity requires that user data is not tampered with, operations do not interfere with each other, and data consistency can be guaranteed to a certain extent.

Under what conditions do you think your team's software is considered good enough to release an alpha version? -Exit criteria

List the features of this version (list new features developed on the basis of the original project)

Requirements for the operating environment

installation method

Describe known issues and limitations of the system

Explain how and where the software is released