blob: a116569f54890010ec5b90575e01f79927e5ec2d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
# Test Case Guidelines for `rnp`
The document aims to describe and capture various use cases for `rnp` in
the form of the test cases. These can be used as acceptance tests for
the maintenance of the project.
## Naming conventions
The test case name is composed of the three parts.
* First being the module under test,
* Second being the feature and third details the motivation of the test.
Naming structure looks like: `<module>_<component>_<test-motivation>`.
For example, when testing the `generatekey` feature of `rnpkeys`, the
test case name would be `rnpkeys.generatekey.<test-motivation>`.
## Test Case Specification Template
The following template **SHOULD** be used for describing a test case.
~~~~~~ md
# <test-case-name>
Component
: <component-name>
Feature
: <feature-name>
## Objective
% Objective of test case
## Description
% Describe test case briefly
## Preconditions
% List of conditions prior to testing
* condition 1
* condition 2
* condition 3
## Test steps and expected behavior
1. Test step 1
1. Test step 2
Expectation: expectation here
## Verification steps and logic
1. Verification step 1
* Rationale: verification logic
1. Verification step 2
* Rationale: verification logic
## Comments
% if any
~~~~~~
|
