Fundamentals of Software Testing (i)

The definition of test: refers to the activity of detecting the object by means of manual or automatic, the aim is to discover the difference between the subject and the customer's demand, or to clarify the difference between the actual result and the expected result.

Second, the software: source code, user manual, configuration data.

Test object: The software source code, the document matching with the software source code, the configuration data supporting the running of the Software source code (System design stage: Summary design document, detailed design document, whether there is a design or logical error; Coding phase: Testing the source code (errors in the discovery of programming) System testing Stage: whether the object being measured meets the user's needs.

Iv. The purpose of software testing (the value of software testing engineers):

1. Find the difference between the measured object and the user's demand--commonly known as the bug;

2, through testing activities to find and solve defects, enhance people to the subject of the quality of confidence;

3, through testing activities to obtain the quality information of the subject, to provide data basis for decision-making;

4, through testing activities to prevent defects, reduce the risk of the project or product.

Five, the principle of software testing:

1, the test proves that the software has defects;

2, it is impossible to carry out exhaustive testing;

3, software defects exist cluster phenomenon (28 law);

4, the test should start early, early intervention;

5, pesticide paradox;

6. Different testing activities depend on different test backgrounds;

7, the software does not exist the fallacy of defects.

Vi. Software quality model (external and internal quality):

Functionality:

1. Suitability

2. Accuracy

3. Interoperability

4. Security and confidentiality

5. Functional Compliance

Reliability:

1, the maturity of

2. Fault tolerance

3. Ease of recovery

4. Reliability Compliance

Ease of Use:

1. Easy to understand

2, easy to learn the nature

3. Ease of operation

4, the attraction of

5, Ease of compliance

Efficiency:

1. Time characteristics

2. Utilization of resources

3. Efficiency Compliance

Serviceability:

1. Easy Analysis

2, easy to change the sex

3. Stability

4. Easy to test

5. Maintenance Compliance

Portability:

1. Adaptability

2, easy installation of

3, easy to replace the sex

4. Co-existence

5. Portability Compliance

Vii. Test level (test phase):

1. Unit test: The test activity for the smallest component unit of the system being tested is generally a class or function, or it may be the smallest functional unit;

2, Integration testing: for components/units and Components/unit interface between the implementation of testing activities to verify that the interface design is consistent with the design;

3, System testing: the integration of testing software, deployed in the real user environment to perform the test ;

4, Acceptance testing: User-oriented testing, acceptance of the group should be composed of members of the project team, user representatives;

Alpha test: The test activities performed by the user in the development environment, the developer around the tester, found that the problem of timely communication solution (in a controlled environment to carry out the test);

Beta test: The developer is not around the tester, found that the problem is collected by the person, and then modified by the developers (in an uncontrolled environment to carry out the test);

UAT Test: User Acceptance Test (general business user Verification System usability test);

Note: About 80% defects can be found in the unit testing phase.

Eight, System test type:

1, Functional testing: Under the specified use conditions, the use of the tested object, to verify whether it meets the user's explicit or invisible needs;

Test Focus: 1), whether there are incorrect or missing or redundant functions

2), to meet the system's explicit or invisible needs

3), whether the input and output to make the correct response, the output can be displayed correctly

2, Performance testing: Through the simulation of the measured objects operating pressure or the use of the scene, to verify whether the object tested to meet the pre-set performance indicators;

Test the Focus: 1), verify the system has the ability to claim

2), understand the typical scenario of test system, and have the definite performance target

3), the requirement in the real environment experiment

3, Safety test: Test the object of the security protection mechanism to protect the system from illegal intrusion, to accept the correct authorization of the operation;

4, Compatibility test: Verify the object under test in different operating systems, hardware information, such as the operation of the environment;

Nine, software testing methods:

1, black box test: Do not pay attention to the internal structure of the object under test, only from the user's needs, whether to meet the explicit or invisible needs of users; 2. White box test (structural test, Logic driven test): test the internal structure of the object being tested;

3, gray Box test: not only focus on the external characteristics of the object being measured, but also pay attention to its internal design;

4, Static testing: In the test object is not running when the detection activities;

5. Dynamic testing: The testing activity carried out during the running of the object under test;

6, Manual test: Through the test engineer trial, to verify that the object is tested to meet user needs;

7, automated testing: Automated testing tools or scripting language Automation to complete the test process;

Fundamentals of Software Testing (i)