Introduction to Software Testing--basic knowledge of software testing (iv)

About the testing process

General company Testing Process

• Review requirements
• Decomposition requirements
• Develop a test plan
• Design Test Cases
• Perform tests
• Submit a bug report
• Regression testing, verifying bugs
• Writing test reports
• Experience Summary

Test process Model

• Waterfall Process Model

Document driven, low degree of freedom. In the actual development process, there is a degree of overlap between the parts, and the reason for this overlap is that no one phase can end before the start of the next phase.

• Rapid Prototyping Process Model

First to make a functional and simple prototype system, to the customer trial to see whether to meet customer expectations, and according to customer feedback to modify the update.

Pros: Focus on user needs and reduce the risk of project errors due to unclear requirements. In large-scale project needs analysis is difficult to complete once, the effect is particularly significant.

• Agile Process Model

A large project is divided into several interconnected, but also can be run independently of small projects, and completed, in the process of the software has been in a state of use. The results of each sub-project are tested, with integrated and operational features.

Suitable for small pieces of work, can fully adapt to the user environment, and continuous iteration of the product.

• Spiral Process Model

Need to undergo multiple requirements analysis, design, implementation, testing process, based on the results of the previous version of the construction of a new version.

This requires a lot of time and effort, primarily to avoid risk, to get user feedback when building a local version of the software early, and to avoid integrating large amounts of code at once.

• Incremental process Model

As the iteration speeds up, each iteration simply adds a small amount of functionality on the previous basis.

Applicable to the post-project, maintenance phase.

What is a bug?

From the internal point of view, the bug is the software development or maintenance process in the existence of errors, defects;

From an external point of view, a bug is a function that the system needs to implement the failure, violation.

Smoke test

Smoke test is the basic function of the software testing, testing the object is each new compiled need to formally test the software version, the purpose is to confirm the basic function of the software is normal, to ensure that the software system can run, and can carry out the formal testing work.

Bug Handling Process

Bug Management

1. Ask questions (why is there a problem?) Is there a problem with the test environment, etc.? ）
2. Confirm is not a bug
3. Positioning problems
4. Submit a bug report
5. Tracking bugs
6. Validation bug (after development process, validation is turned off by the bug)
7. Experience

Bug reports included?

Bug number

Bug status (has development been determined?) ）

Project

Problem Parts

Version

Systems, platforms (EG:PC-side windows systems)

Important levels

Test steps

Expected results

Actual results

Tester, test date

Introduction to Software Testing--basic knowledge of software testing (iv)