Shulou(Shulou.com)06/02 Report--

Assessment of testers:

Testing testers with Bug means that development and testing begin to antagonize each other.

Comprehensive assessment

If you choose the right person, "you will be invincible."

The most valuable tester?

A test team with a high level of testers, found few bug, and all core issues

Does the test really need to write Test Case? -- you need to see the percentage of time spent writing Case to the total test time.

The difference between high-level and low-level testers: Case coverage and business understanding

Automate the testing process, not automated testing

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

What is the goal of software testing?

Stabilize and control the amplitude of software product quality

Efficiently improve the Coverage of Test Case (through Case reuse; data-driven; effective test design methods)

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

How to grade the project and tailor the software test on this basis?

Tailor the testing process

The formulation of testing strategy

Determine test requirements

Determine the test target

Determine test types and methods

Test risk analysis

Test plan development-5W

Determine the goals, methods, environment, tools, etc. (functional requirements; non-functional requirements-performance indicators, reliability and stability indicators, security indicators)

Determine the time period

Identify resources

Automatic test and analysis (what problems are solved, how much cost is spent, and how much efficiency is improved)

Determine the monitoring method of the test process

Risk analysis.

How to improve work efficiency

More reusable products (indicators: test resource reuse rate); less useless work (indicators: effective test hours rate); good cooperation with development (indicators: number of collaboration points, correct rate of collaboration points); good fit of test project schedule (indicators: project change rate, duration fit); automated testing improves efficiency (indicators: automated manual test case rate)

Coverage of test cases

It's a process of finding integral.

Effectively measure the conditions for increasing test case coverage (define baseline; to define granularity-units; effectively normalize a single function point-determine the minimum test range; improve by the combination of function points and the increase of test data; increase the quantity and rate of case each round)

My opinion:

If you do not write case, then the greatest value of testing lies in people, not on case or tools, and if there is a flow of people, the risk will be very high; and for relatively inexperienced testers, even if they are allowed to use exploratory testing for a short time, they are likely to fall into local optimization, and the coverage of case is lower than that of Coverage writing case, resulting in inefficiency.

Testing itself is a major that requires relatively high comprehensive ability, so testers are required to have breadth and corresponding depth both in terms of business and testing ability; the golden mean is very important. If you go to a certain extreme, things will go back to the extreme.

As to how to improve the testing efficiency, testers can improve the testing in some ways, but to some extent, it is the importance that Boss attaches to testing and the position of testers in the whole project.

People-oriented; project ROI-oriented

Attachment: http://down.51cto.com/data/2365959

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.