Test notes (effective ways for software test)
Part 1 software testing capabilities and qualification evaluation
Chapter 1 evaluates software testing capabilities and personnel qualifications
What is a defect?
1. Defect in product specifications
2. Do not match the expectations of customers / users
Divided into the following three categories: errors, omissions, excess
Test personnel ability factor
1. Test analysis report
2. Test improvement skills
3. Test execution skills
4. Test plan, skill
5. Management support
6. Test skills, method
The second part finds a software test environment
Chapter 2 Develops Software Test Strategies
Establish a test principle
1. Test definition. Define a clear, concrete, and clear test
2. Test system. Test and mandatory tests through this method
3. Evaluation. How to measure the evaluation test of information service management
4. Standard. Measurement of test standards
Test factor
Positiveness
2. Document integrity
3. Audit tracking
4. Continuity of processing
5. Service level
6. Access control
7. Compliance
8. Reliability
9. Obtainability
10. Maintainability
11. Portability
12. Coupled
13. Performance
14. Easy to operability
Formulate test strategy
1. Select and distribute test factors
2. Clarify the system development phase
3. Clarify the business risk at the time of development
4. Place the risk in the matrix
Chapter 3 Establishing Software Test Methodology
What need to test?
1. It does not match the specification. This type of defect is due to the lack of vision of the product manufacturing
2. It does not match the expectation. This type of defect is due to the lack of vision.
Why is the shortcomings difficult to find
Did not see
2. I saw it, but I didn't find it.
The defects that are often found in the software are caused by the following conditions:
1. Information technology is incorrect for demand
2. Users put forward the wrong needs
3. Do not correctly record the needs of users
4. Program specifications are incorrect
5. There is an error in programcodes
6. Data input error
7. Data input error
8. Test error
9. Mail error when error correction
10. Error correction conditions lead to additional defects
Four test tactics
Verify, confirm, function test, and structural testing.
Divided into two groups
Verify and confirm
Test staff uses verification methods to ensure that the system (software, hardware, documentation, and personnel) follow organizational standards and procedures, verifying primarily on reviews or some non-executable methods.
Confirmation is actually performed through a series of tests that can be seen and evaluated to ensure that the system operation is implemented in accordance with the plan.
Verify answering such a question: "Do we have a correct system?" And confirmed that the question is: "Whether the system we established is correct"
2. Function and structural testing
Functional testing is often also referred to as a black box test because there is no internal logic knowledge of the system in the test case.
Structural testing is often referred to as a white box test because the internal logic knowledge of the system is often used for imaginary test cases. Structure test mainly uses verification technology.
pros and cons
The advantages of function test:
1. Simulate the use of actual systems
2. Entrance to the system structure
Functional test:
1. Potential logic errors in missing software
2. It may cause redundancy testing
Advantages of structural testing:
1. Can test the structure logic of the software
2. Don't consider whether the function test is completed when testing
Structural test
1. Do not guarantee whether to meet the needs of users
2. Structural testing can not simulate the real world
Testing using verification and confirmation technology includes:
Feasibility review
2. Review
3. Unit test
4. Integrated test
5. System Test
6. User acceptance
