In order to more clearly know the system testing process to write some of the concepts of testing:
1, software testing into four phases: unit testing, integration testing, system testing and acceptance testing.
(1) unit test: test function, based LLD, is generally completed by the developer, is white box.
(2) Integration Testing: modules and interfaces, according HLD, developers and testers completed, belonging gray box testing.
(3) system testing: test the entire software, based on SRS, testers completed, is black box testing.
(4) acceptance testing: test the entire software is divided into α test software under [completed internal testing environment, but must require customers to participate, ask the customer to the company to participate in closed beta testing in a controlled environment under [test] and β customer environments test , the test environment is not controllable].
2, each stage of the four activities: test plan, test plan, test cases, test execution.
3, regression testing
(1) The purpose is to verify whether the defect repaired, whether the introduction of new defects.
(2) strategy: selective regression and complete return.
4 common types of system testing: functional testing, performance testing, GUI testing, usability testing, reliability testing, compatibility testing, installation testing and so on.
Complete system testing process and how the process of:
First outline: Requirements Review Requirements Document [measure], familiar demand - "demand [needs assessment, testers and developers together] -" test plan [Test] team leader or manager to complete the test - "Design test program [complete] senior test engineer - "extraction tests according to item [SRS] -" - "[selective] carried out according to project progress use Case review -" design test case execution of test cases - "writing test test report [ leader Finish
Note: The testing process outlined above each company is different, but generally are so.
First, demand review
Get SRS to our personnel needs, be familiar, familiar with the process is the process of testing the SRS. Because you can not guarantee that the needs of our customers who give real thoughts.
How familiar with the demand?
1. Structure: Composition of the software under test everything
2, Function: provides all the features of the software under test
3, the data: the data (type, size, number, content) can handle the tested software, data which the tested software initialization, configuration data related to what
4, platform: what is the tested software environment: hardware, operating systems, test tools
5, operation: user how to operate, clear what kind of user to use, proper operation, abnormal operation
6, time: time on the tested software functions: time difference, winter time, daylight saving time, special time
Second, the needs assessment
Objective: To develop and test SRS do not understand, understand the wrong place to put forward to improve the quality of the software. To do so throughout the latter part of lower software maintenance costs, projects carried out more smoothly.
Third, the test plan
Core: division of labor, the progress of the control, risk estimates
Fourth, specify the test program
Core: 1, use cases guide the work: the method used to guide the design of test cases
2, guide implementation: guidance how to build environment, defect management guidance how to guide how regression testing
Fifth, extract test items
The main test is the system analysis, system testing purposes analysis is: a clear test points, to extract test items, test requirements analysis. There are three methods: Quality model analysis, functional interaction analysis, user analysis scenarios.
1, the quality model analysis
(1) Functional:
Suitability: whether the corresponding function
Accuracy: function correctly
Interoperability: Inter product 's ability to interact with each other data
Confidentiality Security: whether to allow authorized users to access, whether to allow normal access to data and information systems
Compliance: software functionality for compliance with laws, regulations, standards, norms and protocols
(2) Ease of use:
Easy to understand: the content (icons, text, images, etc.) on the screen are correct and easy to understand
Easy to learn: the ability of users to learn the software. Such as user documentation, tips
Ease: Can users the ability to operate. (Keyboard, shortcut keys, can choose not to enter operation wizard-style operation [more complex business processes can only remember the first step], the menu series <generally not more than 3>, towed operation)
Attractiveness: [interface is beautiful] content on the screen, color; interface elements of typography, layout, size, text font, color [GUI test]
Compliance: software functionality for compliance with laws, regulations, standards, norms and protocols
(3) Efficiency:
Time characteristics: to provide adequate response time and throughput capacity. [Focus on performance indicators]
The use of resources: the service request processing system software resources consumed, CPU usage, memory usage, disk I / O [concern utilization of hardware resources]
(4) Reliability:
Maturity: the ability of the software error does not crash occurs
Resilience: various error conditions
Recoverability: if the software can be restored in case of a crash, the degree of recovery, recovery time-consuming
Compliance: software functionality for compliance with laws, regulations, standards, norms and protocols
(3) Portability:
Adaptability: ability to adapt to different environments [Compatibility test]
Easy Installation: Installation test
Coexistence: software in public environments co-exist with other independent software capabilities. Software resource conflict between attention, read and write the same file, occupy the same port, with a control device
Easy alternative: upgrade testing
Compliance: software functionality for compliance with laws, regulations, standards, norms and protocols
2, functional interaction analysis
(1) consider the interaction between internal software features
(2) common interactive functions: function simultaneously, using the order function
(3) reasons:
a resource conflict: read and write to the same file, occupy the same port, with a control device
b. the results of a function of an impact on the implementation of another function
3. The user scenario analysis
(1) User: person, a piece of software, one device
(2) Scenario: For the purpose of the user, the plurality of functions used to string together.
(3) user scenarios: determined by the flow of events.
(4) flow of events: different trigger events in the same order and form an event processing result stream.
(5) Event Flow Type: elementary stream, stream alternatively
(6) the base stream: begin program from the shortest path to the end of a successful elapsed.
(7) Alternative Flow: various error situations.
(8) Step:
a. Alternatively the flow stream and substantially clear
b. Determine the basic scene and alternate flow stream
c. merging overlapping scenes
During the test points extracted, but also consider the detailed input boxes, drop-down box, links, text boxes, cookie, session and so on, these test points I have order, you can see more. Implicit test point should be taken into account, if your company needs matrix, the extracted test point accuracy to look after fully ensure the test point.
Sixth, test case design
1, the test case is a set of test input for a specific purpose and design, execution conditions and expected results, a program to test and verify the roadbed meet a specific demand!
2, the eight elements of test cases: the number, test items, title, preset condition, input conditions, steps, expected results, importance.
According to these eight factors to write test cases, ideas will be clearer.
3, the test methods used:
Equivalence partitioning method, boundary value method, orthogonal arrangement method, process flow chart, the state transition method, scenario analysis, error guessing method.
4, summarizes the main test case design and precautions:
Test case design is a process of constantly thinking, we must first find out the needs and capabilities of its own software system tested, as well as all the factors that can change the function of these points fitted to a design framework, were tested in various functional point of refinement method and results desired, the refinement process by equivalence partitioning method, an orthogonal matrix or the like in detail each test point, to ensure full covering, while the user's perspective, consider the time users common operation path, in order to choose test points. Test case design is a process of continuous optimization, bug usually found, sum up experience, more experience, will be more comprehensive test cases, software quality can be better protected!
Seven, the implementation of test cases
1, set up a test environment, mainly for the server b / s, c / s
2, the first pre-test (smoke test): select a high level or a basic function test
3, turn the system test assessment: determine there is no need to continue down to test
4, the formal implementation of test cases
5, defect management
6, regression testing
Eight, preparation of test reports
Summative evaluation is generally done by the test leader, to draw final conclusions: Can you publish? Whether to notify the user acceptance? By statistical analysis (amount of work, with the number of cases, number of defects, etc.) various types of data