Construction of a reliable software testing process

Test Staff assessment:

Testing a tester with a bug means that development and testing begin to rival

Comprehensive Assessment

Choose the right person, "will be able to June."

The most valuable testers?

A Test team, the test personnel level is very high, found a few bugs, but also is the core problem ;

Does the test really need to write test case? --The percentage of time that a case takes to be read for the total test time

the difference between high and low level testers: Case coverage and understanding of the business;

Automated test process, not automated testing

Two indicators tested--mass amplitude; improve the coverage of software test cases efficiently

What is the goal of software testing?

Amplitude of stability control software PRODUCT quality

Efficient coverage of test case (by reuse of case, data driven; effective test design method)

Two factions of software test management? --CMM and agile

How to do the project grading, on this basis for software testing cutting it?

To crop the test process

Development of Test strategies

Determine test requirements;

Determine test objectives

Determining Test types and methods

Test risk Analysis

Test Plan Development--5w

Determine test objectives, methods, environment, tools, etc. (functional requirements; non-functional requirements-performance indicators, reliability stability indicators, security indicators)

Determining the time period

Identify resources

Automated test analysis (what problems to solve; how much it costs; how much to improve efficiency)

Determine test process monitoring methods

Risk analysis

How to improve work efficiency

Reusable Products (indicator: Test resource reuse rate); Useless work (indicator: Effective test of work rate); Good coordination with development (indicators: number of collaboration points, the correct rate of collaboration points); Test Project Progress Fit (Indicator: Project change rate, duration fitting degree) ; Automated testing improves efficiency (indicator: Automated manual test case rate)

Coverage of test Cases

It's a process of finding an integral.

Effectively measure the condition of increased coverage of test cases (define baseline; Define particle size-units; a single function point is effectively structured-to determine the minimum test scope; the improvement is the combination of function points and the increase of test data; increase the amount and rate of cases per round)

My point of view:

If you do not write case, then the maximum value of the test is on the person, not the case or tool, when there are people flowing, the risk will be very high, and if the relatively inexperienced testers, even if the time is very short, let it use exploratory testing, it is likely to fall into the local optimal, The coverage of case is lower than the coverage of the write, resulting in inefficiency

Testing, itself is a comprehensive ability to require a relatively high degree of professionalism, then requires testers, whether from the business, or the ability to test the breadth, and have corresponding depth; the mean is important, go to one extreme will extremes meet

Testers can improve in some way by improving test efficiency, but to a certain extent, it is the boss's importance to the test and the role of the tester throughout the project.

People-oriented, based on project ROI

This article is from the "Sunny" blog, make sure to keep this source http://1994520.blog.51cto.com/1984520/1679020

Construction of a reliable software testing process