SQA testing process
World Business Review ICXO.com (Date: 2004-07-28 11:02)
Test Lifecycle Test Plan → Test Design → Test Development → Test Execution → Test Evaluation Test Plan is to define a process of testing projects in order to be able to measure and control test. The first part: Test plan test plan: 1. Test plan is often waiting for the development cycle to begin implementation, making no time effective implementation plan; 2. The organizers of the test plan may lack the client / server test experience; 3, test Measurement and complexity may be too large, no automation tools, difficult to plan and control. Test Strategy: Test Policy Description Test Engineering Method and Goal. Describe the current test (unit test, integrated test, system test), and test types (function test, performance test, pressure test, etc.) per stage (function test, performance test, pressure test, etc.). Test strategies include 1. Test technology and tools to use; 2. Test completion standards; 3. Special considerations affecting resource allocation, such as testing and external interfaces or simulating physical damage, security threats. One of the most critical steps of the test plan is to break software into units, write a test demand. Test demand has a lot of classification methods, the most ordinary one is based on commercial functions. There are several benefits to break down the software into unit components: 1. Test demand is the basis for testing design and development test cases. The divided into units can be better designed; 2. Detailed test requirements are important indicators for measuring test coverage 3. Test demand includes various test practical and development and resources required. How to estimate the test workload: 1, efficiency assumption: Test team work efficiency. For functional testing, this mainly depends on the complexity of the application, the number of windows, the number of action in each window. For capacity testing, mainly depends on the workload of the data required to test the test. 2, test assumption: In order to verify the number of tests required for test requirements. 3. Dimension of the application: complexity indicators of the application. For example, to join a record, the dimension of the test demand is the number of this record. 4. Stage of the test cycle of the test: Some phases are in design, some stages mainly test implementation. Test Resources: 1. The Human Resources Test Manager provides overall direction for test projects. Develop test programs, collect and supervise testers, apply for system resources, monitor and report work processes, test assessments, and test demand. Test Engineer ---- Design and Development Design: Detailed understanding of the test software, breaking the test requirements, selecting techniques for verifying test requirements in a C / S environment. Development: Familiar with SQA, VB, and scripting languages. Test Engineer ---- Execute the results responsible for test execution and recording. You need to install system, network knowledge, initialize databases, and other initial conditions. It is important to diagnose. Test System Manager Each test item must specify a person to manage SQA Suite. Includes a repository on the server, install the printer connection, perform backup, and other maintenance work. Managers must be highly familiar with SQA, network work experience. 2, System Resources Installing SQA Suite Hardware and Software Environment Database Server This server must be dedicated to testing, reset some initial values, including system date and time. Steps to write test programs: 1. Determine the following information
Documentation has created (yes / no) version / date requirements Details Function Details Project Plan Design Details Prototype User Manual Defines New Engineering, Adminà New Project. Determine the structure of the software, define the software structure with the Assetsà Software Structure option. 2. Define test strategies
Test Strategy Item Example Test Phase System Test Test Type Function Test Test Technology 75% Automatic Testing with SQA Suite, 25% Manual Test Complete Standard 95% Test Example Pass and Solve All Solve Special Considering Test Must perform 3, Decompose Software Write test requirements Analyze various information repeatedly and understand various information, communicate with users, and understand their requirements. You can follow the steps below: 1. Determine the primary business task 2 provided by the software. For each business task, determine the transaction to complete the task. 3. Determine the calculation result from the database information. 4. Determine the time and conditions of the time and conditions for transactions for time requirements. These conditions include database size, machine configuration, transaction volume, and network congestion. 5. Determine a major accidental pressure test, including: memory, hard disk space, high trading rate 6, determine the amount of data that needs to be processed. 7. Determine the required software and hardware configuration. Typically, it is impossible to test all possible configurations, so choose the most likely to produce problems to test, including: the lowest performance hardware, several software compatible with compatibility issues, the client machine passes the most Slow LAN / WANF Connection Access Server. 8. Determine other commercial transactions that have no direct relationship with the application software. Including: management functions, such as launching and launching program configuration, such as setting printer operators, such as font, color application, such as accessing email or display time and date. 9. Determine the installation process, including which installation, custom installation, upgrade installation. 10. It is determined that there is no hidden in the functional test. Most interfaces are tested when feature testing. There is also no test, such as: operation and display consistency, such as using shortcuts, etc., interface follows reasonable standards, such as button size, tag, etc. To organize demand into level Figure 4, estimate test workload σ (time for each test * * Number of tests for each requirement * Number of test requirements) (test design, development, ...) 5, determine resource Human Resources Position Name Special Responsibility / Description Test Manager Test Engineer Design / Development (Can Multi - person) Test Engineer Test Enforcement (Can Multi - person) Test System Administrator System Resources
System Name / Type Database Server Network / Subnet Server Name Database Name SQA Test Repository Network / Subnet Server Name Customer Test Machine Includes Special Configuration Requirements List Test Development PC List 6, Create Engineering Scheduling
Task-related workload (day) The entire SQA process 38 test plan 12 Determine item 1 Define test policy Decision Test requirements Estimation workload determine resource scheduling test activities Generate test plan document test design 7 Analysis test requirements Specify test procedure Specify test case View test requirements Coverage Test Development 12 Establishing Test Development Environment Recording and Playback Prototype Process Development Test Process Test and Debug Test Process Modifying Test Procedure Establishing External Data Collection Repeat and Debugging Test Process Test Entering 6 Setting Test System Execution Test Verification Test Results Survey Results (Unexpected Result Generating Defect Diary Test Evaluation 1 Reviewing Test Diary Evaluation Test Demand coverage assessment defect decision to achieve standard 7, writing test plan 1, introduce the background test range project file list 2, test demand 3, Test Strategy Test Type 1, Function Test 2, User Interface Test 3, Performance Test 4, Pressure Test 5, Capacity Test 6, Configuration Test 7, Installation Test Tool 4, Resource Human Resource System Resources 5, Scheduling 6, Document Software Components Test Features (Assets) Test Diary Defect Report Part 2: Test Design Test Design Problems 1, do not test design, the test process is also built. 2, the test design is not detailed, not based on a volumetric test strategy, such as a test plan covers a collection or test demand. 3, the test process does not use the best technology to test the selection rule 1 of the test demand test case of the Windows C / S structure, select the most relevant test cases for the substantive part of the test demand. 2. The selected test case should not be easily influenced by the changes. Below is a few specific rules for choosing test cases: 1, business function business functions are generally related to the database, to test the changes in the database, there are several ways: 1. If the change in the database is reflected in a list box, then To select the test case of the verification list box content. 2, you can also check the confirmation dialog completed after the transaction. You can check the title of the dialog. Image comparisons can also check the confirmation dialog, but the image is more likely to be affected by other factors. 3, modify the script, SQA Basic provides powerful database support. 2, the field verification Various different domains selection corresponding test cases. 3. User Interface Test Object Status Test Example 4 Use example (related to the drive) 8, the installation option and the verification target status case and the window exist, the file exists. Steps to write test design ↓ Specify test process ↓ Specify test case (optional) ↓ Review the test coverage Part III: Test development input: Software, test design output based on test requirements: testing process and test Use examples: 1. Creating a reuse testing process and test case 2, maintaining a test process, test case, and a one-to-one related test requirements. Test development issues: 1. Test development is very chaotic, no correspondence with the test requirements or test strategy 2. The test process is not repetitive or not reusable 3. The test process is executed as a programming task, causing the script to be too long, can not meet the software Transplantation requirements.
