When new functionality of the system is developed, the analyst writes the requirements, and the tester checks them. Before starting implementation. Because at this stage it is cheapest to make corrections.
Just what to look for when testing? There are a number of basic characteristics that good documentation should have:
Of course, there may be more of them. Someone uses the mnemonic CIRCUS MATTA , someone expands the list for themselves and the team. But these six characteristics are basic. They write about them in books on testing and in various articles.
In this article I will tell you more about each of them, with pictures and examples from life.
1. Completeness
Is everything described? Have you forgotten anything? What if we still have an undescribed functionality or an API method parameter?
To check this point, just write a checklist of functional checks. This is how they started to read the TK, immediately write down the tests. It is important to write , and not just think in mind. Otherwise, you will definitely forget something.
- . , , . , -... , «», .
«». , , . :
— , ... ?
, ! , , .
, . . ... , , 5-10 . , , .
, « ». 10 . « », - .
? , , . : ?
, . , , . , , .
, — , . , - , !
2.
.
« » → «»?
, , ;
, 5 , .
. . :
.
5 .
, :
, 0. , !
, ! - ...
, , :
— .
, — , . , , ...
, , . , , .
, — .
, — , « , ...?». , . , - . , .
3.
. , . , . .
, , , 3 . , . , . !
, . , ?)
4.
: «, »? .
, . , 10 4. , , , , .
, ? ? , ?
, :
— , , .
— , . .
5.
, ? ?
. « 0,1 » - . , , - .
, , . « , «», « , ». , .
— . « », :
1. : .
2. : .
?
? , ? .
Lucene. -:
o ;
o ;
o ( , );
o ...
! , . ( ), — .
, . , . — .
? . . , . , 1000 10 , .
6.
?
. , , , . , , .
, . , , . , . — . .
, , « , » . , . , .
, . , JMS-. JMS-.
— « » ! , :
— ? jms — , ?
— , , , . , .
, , !
, , . , .
( ) , , . — , . .
! . .
: CIRCUS MATTA
CIRCUS MATTA — . ! :
Completeness —
Independent —
Realisable —
Consistency —
Unambiguity —
Specific —
Measurable —
Acceptable —
Testable —
Traceable — ( )
Achievable —
Look how many points it turned out! I am particularly impressed by the items "customer specific" and "traceability". This is really important. If you have a boxed product that is customized for the customer, be sure to look at the item "Specific". And traceability is a very nice bonus, making it easier to keep the documentation up to date!
See also:
Testing documentation for software products - there are as many as 18 criteria for good documentation!
Requirements testing. Features - An article from the Quality Lab.
PS - for more useful articles, look at my blog under the tag "useful" . And useful videos are on my youtube channel