What is software testing?

The purpose of software testing is to discover some development risks that can be avoided by testing, to implement tests to reduce the risks identified, and to determine when the test can end. Consider testing as a standard project during the development of a project. The purpose of the test is to verify whether it satisfies the required requirements or to ascertain the difference between the expected and actual results. You need to write a test plan before testing, the most important of which is the test method used in this test, the test tool used, and the test environment. Staffing and scheduling of personnel, output artifacts after each test phase, and risk assessment are required. Make these preparations in place before testing so that they are more organized during testing.

The test flow is as follows:
Requirements: Read the needs, understand the needs, and customer, development, architecture, multi-party communication, in-depth understanding of requirements. --testing Team
Test Plan: Estimate the required resources (manpower, equipment, etc.), the time required, the function points, and how to allocate resources rationally according to the requirements. ---Testing leader or testing manager
Use case design: According to test plan, task assignment, Function point division, design reasonable test case. ---testing leader, senior tester
Execute the test: Execute the test case based on the detailed steps of the test case. --every Tester (mainly junior testers)
Execution of result records and bug records: The results of each case recording test, bugs in the test management tool to write Bug records. --every Tester (mainly junior testers)
Defect tracking: Track the bug that leader assigned to you to track. Until the bug is fixed. --every Tester
Test report: There is no major bug in testing and tracking until the tested software meets the test requirements.
User experience, software release, etc...

What is software testing?