The exam is in the afternoon ~ ~ Attach oneself to do the examination scope

The first chapter tests whether it is necessary

Yes. Low cost after all

What is the quality of the software? (Testing is the quality of the software, then what is the quality of the software)

External quality: User-aware,[ Functional, reliable, easy-to-use, efficient ]

Internal quality: Code style, cohesion, coupling "maintainable, portable"

Software Quality attributes:

Static mass properties: Structured, maintainable, testable code, and the right documentation for availability

Dynamic mass properties: Software reliability, correctness, completeness, consistency, availability, and performance

Testing is only used to detect defects.

Debugging is the ultimate solution to the problem, people can not be weight to lose weight.

A possible point to be explored:

The development trend of software testing:

1, functional verification-oriented: testing is to prove that the software is correct. (Positive Thinking)

2, destructive-oriented: testing in order to find errors in the software (reverse thinking)

3, quality assessment-oriented: testing is to provide product evaluation and quality measurement

4, to defect prevention-oriented: testing in order to demonstrate that the software meets the design requirements, detect defects, prevent defects

1 Software Testing the correct definition:

1, Software testing is the "verification (verification)" and "validation (Validation)" Activities constitute the whole .

2, Verification "is to verify that the software has been correctly implemented in the product specifications defined by the system functions and characteristics.

3, "validity confirmation" is to confirm that the software developed to meet the real needs of users activities.

b Other points of view for software testing:

1. Software testing is considered to be an activity to evaluate potential risks in a software system. risk-based software testing can be seen as a dynamic monitoring process, the whole process of software development to detect, at any time to identify problems, report problems

2, the economic view of the test is to obtain the highest quality of software products at the lowest cost. The economic point of view also requires software testing to work as early as possible, and the sooner the defect is discovered, the smaller the amount of rework, and the smaller the damage.

Chapter II Software Testing coverage:

Figure Overlay

Code overrides

Logical Overrides

The definition of the test coverage, as well as the level if you want to, will.

The test path is the complete path that refers to the single-entry single-out. The points or paths passed are accessed. A subset of its "paths" is traveling.

Figure A

123568

1234

123567

43568

768

343

434

767

676

43567

Find the simple path (greater than or equal to the node less than or equal to the primary path), the primary path, and the maximum simple path.

Main path source?

NCC ECC EPCC CPCC SPCC PPCC

Draw according to the code. Find the corresponding side pair, and the main path, and find the corresponding test path

Data Flow Overlay:

Full definition covering the ADC with a defined

Full use covers all of the AUC bands used

Full definition use path overrides ADUPC definition used by combination

Conditional overwrite CC, results overwrite DC condition result overwrite MCDC

Figure II

Chapter III Functional Testing

pairwise orthogonal test of causality diagram of equivalence class boundary value judgment table

How to test?

1, play the customer to do the test

2. Business-based testing

3, demand-based testing

4, play the customer to do the test

5. Test method based on use case "scenario-based testing"

Equivalence class

1.make a table, divide the equivalence class

2, for each equivalence class label

3.design a test case to cover as many valid equivalence classes as possible

4.repeat 3until all valid equivalence classes are overwritten

5.design a test case to cover only an invalid equivalence class

6.Repeat 5until all invalid equivalence classes are overwritten

Boundary value

Design method:

Determining boundary conditions (the bounds of an input or output equivalence class)

Select exactly equal to, just greater than, or just below the boundary value as the test data

Decision table

Based on the combination of the results can be known to the problem, the use of the decision table method / Policy Table method (decisiontable)

Causality diagram

1, can not be based on the combination of input conditions, directly determine the resulting results, the need for causal analysis

2.causality analysis is done by causality diagram

3, causality diagram is a graphical method of logical analysis

Pairwise

Factors when multiple values are taken:

To be seen.

Might

Orthogonal test:

Neat comparable

Balanced dispersion

Fourth. Variation Test

P11

At the end of the second step, it is determined that K1 is the mutant that was killed. (k1<k)

K-k1 is the surviving variant.

Situation One:

K-k1=0: T is sufficient in terms of mutants.

Situation Two:

K-k1>0: Then we'll calculate the mutation fraction MS:

ms=k1/(K-E)

E is the number of equivalent variants,e<=k-k1.

Analysis:

k-k1>0 T is not sufficient.

If T is insufficient , some mutants are not identified, resulting in fewer kills than the real

This diagram says: ms= detected mutants / true non-equivalent variants

Figure Four

If Ms=1, then T is full. e=k-k1"This is there,case1 is all detected, this Ms=1 refers to the living is equal to the" Increased technology

If ms<1, then T is not sufficient. Increase use cases

Fifth Chapter Regression Test

Refers to the introduction of a new error after the old code has been modified, or an error in other existing code.

Concept:

1.perform all or part of the same test as before

2, the new module, may have negative effects on other modules, it is to carry out a certain degree of regression.

3, the center of gravity of the regression test, with the key module as the core.

Maintenance of test Case libraries:

1. Delete obsolete Use cases

2. Improve the uncontrolled use case

3. Delete Redundant test cases

4. Add new test Cases

Regression Test Package Selection:

1, in testing all use cases

2, based on the risk selection test "test from main characteristics to secondary characteristics." The most important, critical and questionable tests "

3, based on the Operation section selection test "the most important or most frequent use of the function of the test case, a given budget for the most effective system to improve the reliability, but the implementation of a certain degree of difficulty." 】

4, in the test modification of the section "To do as far as possible full coverage"

Test process:

1. Identify the parts of the software that have been modified

2. From the original baseline test Case Library T , exclude test cases that are no longer in use, identify test cases that are still valid for the new version, and create a new limit test case Library T0.

3, according to a certain strategy, Select test Cases from T0 test the modified software.

4. If it is necessary to generate a new set of test cases T1 used to test T0 is nothing more than a fully tested piece of software.

5 . Execute the modified software with T1.

"Maybe that's the point I'm going to find, and maybe that's what the" bastard programmer "has learned in the self-study code. As long as you can solve the problem, it is unnecessary to be too wedded to the ready-made style. For example, a few days of regression testing, if the step-by-step reading ppt may take a long time, since all are regression testing, Baidu should also have introduced, then may wish to read a quick version, in order to achieve the knowledge of this part of the rapid thinking to clear. In order to solve certain problems in practice. "

The sixth chapter test requirements Analysis Concept

What are test requirements?

1, testing requirements, to solve the problem of testing, indicating what to test the object to be tested.

2, usually based on the requirements of software development, the development needs of the refinement and decomposition to form the content can be tested.

3. Test requirements should cover all defined business processes, functional requirements, and non-functional requirements.

What does the test requirements analysis do?

1, clear the scope of requirements, sorting out the test demand point

2, clear the business process of each demand point

3.organize the business combination between different demand points

4. Mining implicit demand according to explicit demand

【

1, clear test requirements range, sorting out the test point

2. Define the business logic of the test point

3, according to business logic, sorting out the business portfolio

4, according to display demand to find implicit demand "

"Test the demand outcome to test what, that is, the test team phase that the content to be tested

2, according to the requirements of software development, to split and refine the requirements, the content of the itinerary to be tested

3. To test all defined business logic, functional requirements, and non-functional requirements

Seventh Test requirements Analysis process

1. Acquisition Scope: Requirements specification, project related documents, business background information, training materials, communication with customers or people involved, competitor products, Test experience library, other "

2, demand Analysis "

Demand Essentials Analysis: Source of demand analysis, inheritance analysis, requirements of the collation ( thinning, merging redundancy )

Quality Model Analysis: Analysis of quality characteristics and test type

User Scenario Analysis: Interaction analysis, Business scenario analysis

】

3. Requirements Review

Content of the review: completeness review, accuracy review

The form of review: review meetings, mail or instant messaging tools to communicate with relevant people.

Test demand Tracking Matrix

Test demand tracking matrix requires constant maintenance

On the one hand to synchronize changes

On the other hand, expanding

Exploratory testing

Product Functional Characteristics Layering:

Single characteristic test:

1. Lenovo Input Model

2. Internet Test model

1. On-line Bug model
2. Off-line fault model

3. Roaming test Model

1. Basic test methods
   1. Selling Point test method
   2. test method of bad neighbor
2. Advanced test methods
   1. Limit test method
   2. Overnight test method
   3. Test one to send a testing method

Interactive feature testing:

Scene Exploration model

1. Scene Operation model

1. Full operation based on each user's visible operating point

2. Roaming Exploration model

1. Landmark test method with the scene click on each of the locations
2. Express test method first operation after verification

System Interaction Test:

1. Formal Process Model

1. Identify products and functions
2. Identify potential areas of uncertainty
3. Testing the functionality and stability of the product

2. Roaming map Model

1. Introduction to the roaming map model
2. Roaming map Thinking Framework

3. soap opera Test model

1. Soap opera Test Cases
2. Soap opera Test features

Test model for functional testing based on force testing

Figure Five

The exam is in the afternoon ~ ~ Attach oneself to do the examination scope