Traditional software testing problems and solutions

Traditional software testing process: small amount of unit testing in the software development process. Then end stage throughout the software development, focus on a large number of tests, including the function and performance of the integration testing and system testing. With the increasing complexity of software development, software testing process inevitably brings us the following question:

One problem: difficult to control the progress of the project, project management more difficult.

A large number of software errors often only to the system test phase of the project late been discovered to solve the problem of the time it takes to be difficult to predict, and often lead to the progress of the project can not control, a lack of understanding of the quality of projects throughout the software development process, project management and control, increase the difficulty of project management.

Second problem: weak project risk project risk control in the late project development can really reduced. After system testing before really determine whether the design truly meet the needs of the system functionality, performance and reliability.

Question three: software project development costs exceed the budget. The later errors found in the entire software development cycle, the higher the cost of the unit bug fixes, error delay to solve the entire cost of the project is bound to lead to a sharp increase.

The successful experience of the IBM Rational Software automated testing to solve the problem of the traditional test.

The core of the successful experience of the three best: early testing, continuous testing, automated testing, and on this basis to provide a complete software testing process and a set of software automation tools, so we eventually be able to do: a test team, based on a complete set of software testing process, the use of a complete set of automated software testing tools, and complete a full range of software quality verification.

Successful experience: as soon as possible to test

The so-called as soon as possible to test an idea through a variety of software engineering in the entire software development cycle as early as possible to complete a variety of software testing tasks. IBM Rational software engineering techniques early test for us in the following three aspects:

First of all, the entire testing life cycle of the software is essentially flush with the software development life cycle process. When demand analysis basic clear we should be based on a needs analysis of the results, and the entire project plan for software test plans; along with the analysis and design process should be completed test case design; When the software's first release came out, the test to immediately based on its implementation of test scripts and execute test cases based on the purpose of the test in the test plan, the assessment report of the test results. In this way, we can index real-time monitoring of various test project quality status, to improve the control and management of the entire project.

Project planning, demand management --- test plan

Test plans, analysis of the design --- test design

Test design --- test implementation

Test --- test results assessment

Secondly, through the iteration is software development to the original of the entire software development life cycle is divided into multiple iteration cycles, and in each iteration cycle test system testing time in advance, so largely, largely reduce project risk and project development costs.

Finally, IBM Rational early test of successful experience is also reflected in the expanded developer testing and system testing traditional testing phase from unit testing, integration testing, system testing, acceptance testing division of the entire software testing phases divided into two stage. Software testing duty bound to extend to the the developers work of the entire development process. Through advance testing time to improve the quality of software testing as soon as possible, to reduce the cost of software testing.

Successful experience: continuous testing

The test successful experience continuous test is derived from iterative software development model. Iterative method, we target the entire software development is divided into a series of small targets easier to implement and achieve these objectives are defined clear stage evaluation criteria. Iterations is engaged in a series of development activities in order to complete certain milestones must be based on the current state of the project and the milestones to be achieved before the start of each iteration develop iterative scheme and each iteration of the process including requirements development, design, coding, integration, testing a series of activities will be incremental integration of new system functions. Each iteration to generate a running system. System can run tests to assess the iterations have not reached the predetermined iteration goals, and as a basis to develop the next iteration. Thus, in each iteration of the iterative software development cycle, we will carry out activities of software testing, and completion of the entire software testing through each iteration cycle constantly incremental testing and regression testing.

Successful experience: automated testing

Should test as soon as possible in the whole process of software testing, continuous testing, can be said to improve the testing process is automated testing tools is to ensure that. The successful experience of the IBM Rational automated testing refers to the use of software testing tools provide complete support of the software testing process and various test automation implementation.

Addition to the test in order to make the software testing team, IBM Rational provides test successful experience, also provides us with a complete set of software testing processes and automated testing tools, software testing team can take time to complete the test task.