Agile Testing (10) Acceptance test execution

Acceptance test Execution-signature test

The acceptance test design mentioned above solves the problem of long test design document, poor readability, no clarity, no structure and so on. So, how to improve rd quality awareness, let them follow the acceptance criteria self-test, so as to understand the Test Rd range, effective use of its self-test results? How to change the status quo (QA test is a total coverage with no focus, no risk analysis), improve the test efficiency?

The answer is the 3rd mentioned above: Each case can be marked for execution . Detailed explanation of the specific marking method below.

For case labeling, plus the name of the journalist (or the automation level), I call it "signature". Rd takes a self-test of the structured acceptance test design provided by QA and marks it (who I am, what I measured, and which level of automated testing is covered). The identity of the tester in the system of the seal mark, so the name of the signature test, take solemn , responsible for the meaning.

1. Role Signature

2. Automated signature

3. Signature process

A. Testing process