Summary of software Testing (i.)

Summary of software Testing (i.) This article indexStandard software for product quality testing classification static and dynamic testing active and passive testing white box test and black box test software Test level the organization and management of test work implementation test workflow standard of product quality

functionality : A set of properties related to a set of features and their specified properties, where the functionality is those that satisfy explicit or implicit requirements.

Usability : Easy to install, easy to use, user friendly

Reliability : A set of properties related to the ability of the software to maintain its performance level for a specified period of time and conditions.

Performance : Specifies how efficiently the software responds to the operation and how much of the computer resources (including memory size, CPU time) are required to implement a function.

capacity : The capacity of the system to accept, accommodate, or absorb, such as how many concurrent users the web system can afford to concurrently access, the number of attendees the network conferencing system can afford.

Measurable: Some of the characteristics of the system can be described by some quantitative data indicators of their current state or set state

maintainability : The extent to which the effort has been made after the software has been put into operation, changes in requirements, changes in the environment, or errors in the software.

compatibility : How easy it is to migrate software from one environment to another, or to work with external conditions.

Scalability: How easy it is to add new features and expand system capabilities in the future. Software test classification

categories by Test : Unit test, Interface test, System test, data test, interface test, document test

Classification by Test purpose : Functional test, stress test, performance test, reliability test, disaster recovery test, safety test, compatibility test, regression test, installation test

depending on whether the tested software is executed during the test: static test, dynamic test

depending on whether the tester is involved in the operation of the tested object: active testing, passive testing

based on whether the internal structure of the system and the specific implementation algorithm to complete the test: white box test, black box test

depending on whether the test is done by a software tool: manual testing, automated test static testing and dynamic testing

static test execution methods are the requirements of software products and design specifications of the review, review of the Code and static analysis, etc. (round, walk, Audit, review meetings).

Dynamic Testing is the actual running of the program to find errors, by observing the code to run the process, to obtain system information, the system behavior verification. active testing and passive testing

Active test Method : The tester proactively sends requests to the object being tested, or uses data, events to drive the behavior of the object being tested, thus verifying the reaction or output of the object being tested

Passive testing methods : Testers do not interfere with the operation of the product, but passively monitor the product in the actual environment, through a certain passive mechanism to obtain the system Operation data, including input and output data. white box test and black box test

1) White box test : (structure, logic Drive)

The internal working process of the known products, clearly the final generation of software products of the computer program structure and its statements, according to the internal structure of the program inside the test program variables, logical structure, running path, and so on, each path in the test procedure can be correctly worked according to the requirements, Check whether the internal action or operation of the program conforms to the design specifications, and all internal components are operated according to the requirements.

Basic Principles

When performing a test, consider each branch to be overwritten first;

Then consider all the logic conditions to be true and false values respectively;

If there is a higher quality requirement, all independent paths are run at least once during the test object process

Examine internal data structures, and pay attention to contextual impacts to ensure test effectiveness

2) Black box test : (function, Data driven)

Test, the program as a black box can not be opened, regardless of the internal structure of the program and internal characteristics of the case, the tester for the software directly tested.

The following defects can be found

Having the wrong function or missing a function;

Unable to receive and input data correctly, output incorrect result;

Functional operation logic unreasonable, not convenient

Interface error, not beautiful

The installation procedure is not clear, not flexible

system initialization issues, etc. Software Test level

Unit Test

The minimum unit---class, function, module or component of the program system is tested, and is usually synchronized with the coding. The paper mainly uses the White box test method, from the internal structure of the program to design the test case, check whether the implemented function of the program module or component is consistent with the defined function, and whether there are errors in the encoding.

Integration Testing

Also known as assembly testing, joint testing, on the basis of unit testing, the module according to the design requirements of the assembly and testing, the main goal is to find the interface between the module problems.

Two kinds of integration methods: one-time integration and the incremental integration method.

non-functional testing of the system

Put software in the entire computer environment, including hardware and software platforms, certain supporting software, data and personnel, perform a series of tests in a real-world or simulated environment, including: load testing, performance testing, disaster recovery testing, strength testing

Alpha Test

Refers to the software development company internal personnel began to try new products, in the actual operating environment and real application process found in the testing phase has not found defects.

Beta test

Refers to a typical user test outside the company, and requires users to report anomalies, make critical comments, and then revise and refine the beta version, and eventually get the release officially released.

organization and management of software testing work

Develop test strategy, test plan, confirm the test method and specification, control test progress and manage test resources.

implementation of test work

prepare test documents in conformance with standards, build test environment, develop test scripts, collaborate with development organizations to implement testing activities at each stage Test Workflow