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
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
2788N/A * trunk/opends/resource/legal-notices/OpenDS.LICENSE. If applicable,
2788N/AThe following is an example for the test group, functional-tests/testcases/security/pwd_storage,
2788N/AEach xml file will be treated as a test suite. Each file should contain the following tags......
2788N/AThe #@TestIssue should be the number in IssueTracker that corresponds to the feature or defect
2788N/AThree parameters are required to run the parsing tool from the command line, directory-to-testcase-files,
2788N/Ajava -cp [path-to-class-files] GenerateOpenDSTestSpecs [directory-to-testcase-files] [directory-for-output-files] [file format]
2788N/AThe directory-to-testcase-files is the directory from where the parsing tool will begin searching
2788N/Afor functional test files to parse. The parsing tool will only search one or two levels below
2788N/AThe file format is necessary because the same code is used for the unit-integration tests where