Test-related Topics

Testing fundamentals, testing strategies and methods (reproduced)

Today is about testing strategies and methods, first look at what the strategy and methods, this is a bit like military strategy and tactics, one is macro, one is micro.

In view of this, software testing strategy is a set of principles, ways and methods of software testing under the guidance of certain software testing standards and test specifications, according to the specific environmental constraints of the test project. This set of test principles, methods, and methods can help us to analyze the test in a global way.

When we get a software preparation test, we must first grasp from the macro. The macro is basically what we often say 5 w:when, where, who, what, how. When is to grasp the progress of the test, where is the site of the test, who is the team building, what is to measure, how is measured. Our strategy should be how to measure.

So, let's take a look at the kinds of test strategies we have.

1. White box test, grey Box test and black box test

black Box testing: also known as functional testing, data-driven testing, or testing based on specifications, focus on testing the functional requirements of the software. Testers do not care about how the program is implemented, according to the specifications of the software to enter various types of software, observe the various output of the software, found the software defects. Because such tests do not take into account the internal workings of the software, the software is like a black box to the user. For example, the calculator program, input the 4, as long as the result is the function is correct, and do not have to care about whether the internal is 2*2 or, only pay attention to its output is not our expected results.

White Box testing: also known as structural testing, logic-driven testing, or test based on program code. Based on the analysis of the internal workings of the software, the testers judge the quality of the software by reading the program code or by using one-step debugging in the development tools. This kind of test will be concerned with its internal implementation, or our calculator, calculate the 2*2, we have to see its internal implementation should be the "T-S, but not the."

Gray Box testing: A test method between black-box and white-box testing that considers black-box testing when performing white-box testing

2, manual testing and automated testing

Manual testing: As the name implies, manual execution of software to discover defects without relying on other automation tools.

Automated testing relies on automated tools to aid testing, and common automation tools such as QTP, LoadRunner, robot, etc.

3. Static test and dynamic test

Static testing is the process of not running the program itself and looking for errors or evaluating program code that may exist in the program. This is primarily a check of the code documentation. Static testing can be done either manually or using automation tools, such as jtest, C + + test, and so on. Dynamic testing is the execution of programs to check for defects.

4. Function test and performance test

Functional Testing : test the characteristics and operational behavior of a product according to product characteristics, operating description, and user scenarios to determine that they meet the design requirements.

Performance Testing : A test that evaluates whether a product or component meets the performance requirements. Includes load test, strength test, Database capacity test, benchmark test and other types.

5. Smoke Test

Smoke tests are also known as version verification tests. It is mainly to verify that the basic function of the software is normal. The first thing we need to do when we get a software is a smoke test, and if the smoke test doesn't go through then the following is no longer necessary. For example, when we test Sogou input method, it can not be installed correctly, then the next function can not be measured.

6. Regression test

regression testing is a new version of the software test, when you get a new version of the test to repeat the first version of the use case (or part of the use case).

7. Random Test

Also known as the Monkey Test, is not a specified use case, completely according to the experience of the tester to test.

OK, today's introduction of these, the focus of today to master these common test strategies. Tomorrow will continue to introduce the test method, starting tomorrow I will use some small projects to help you learn, and increase experience.

English words:

Cause and Effect diagram: Cause-effect Graph Code Coverage: The Code Coverage condition test: Condition Testing Configuration Management: Config management

Test-related Topics