1. What is the test
1. Finding bugs is the process of finding software testing errors
2. Deepen the understanding of the software and make the software more suitable for users
3. Test work - execute the test
a. Participate in requirement review, plan test process, write test plan, edit test case
b. Participate in requirements meeting, design review meeting, regular test meeting, and test summary meeting
c. Learn test tools, understand project business,
d. Ability to edit test cases, familiar with the methods when planning test cases
4. Communicate with product managers
Communicate with the development the problem sheet output during the testing process
The purpose of the test
1. Verify that the software can achieve the normal functions required by users and find bugs
2. Prevent the occurrence of problems, find problems in the early stage to avoid problems; summarize and analyze problems, and cooperate with development to avoid problems
The software life cycle
User puts forward requirements - planning software development and testing, etc. - requirements analysis - design model - programming - testing - maintenance
When a software is no longer officially maintained, the software is considered dead. But some users can still use
Four, three models of software development
1. Waterfall Model
Steps: Planning - Requirements Analysis - Design - Programming - Testing - Maintenance
Applicable objects: software with determined requirements and simple functions
Pros: Clear and complete
Disadvantages: software with a long cycle is not suitable, such as the research and development of operating systems, the content is copied and huge, and all problems cannot be predicted in the early stage; the resolution time of technical problems is uncontrollable
Software with rapidly changing requirements is not suitable. If it is completed at one time, it will cause excessive maintenance due to changes in requirements later.
2. Spiral model
Adding iteration or looping to the waterfall model
Applicable objects: The huge software is divided into several small requirements, and the important requirements are completed first.
Fast-changing software: The previous iterations have been completed and stabilized, and after other requirements are stabilized, it will be implemented in subsequent iterations
3. Agile
Applicable object: multiple iterations, with the time period as the termination point, the iteration has a fixed time
Features: Fixed cycle, not based on the completion of requirements as the termination point; short cycle, usually about 15 days as a cycle; agile testing, daily construction; tool support required
5. R&D team
1. Development team: requirements analysis, design, coding
2. Test team: functional testing, automated testing, performance testing
3. Quality management personnel: project management personnel, CMO configuration personnel, QA
6. What is the defect
1. Defects can be understood as errors, parts that do not meet the requirements
2. For example, the internal deficiencies of the software code, human-induced errors, and inconsistencies with the user's habits
3. Defects are generally divided into three categories: failure (failure of software operation), failure (absence or unavailability of a major function), general
7. Test engineer
Generally divided into three categories: functional test engineers, automation test engineers, performance test engineers
In general, the growth of test engineers is also from function to automation to performance
Self-improvement aspects of test engineers: experience (test process, project, business), technology (new development technology, code, test tools, new test model), test process, communication skills