Lines Matching refs:test
28 The purpose of the parsing tool is to parse comments from the functional test xml files.
31 the functional test xml files, and how to build and run the parsing tool.
35 Each directory will be assumed to contain the tests within a test group.
36 Each test group needs to have the following tags.......
40 #@TestSubgroupName [only necessary for some test groups, like Security]
43 as long as the xml file is in the proper directory for the test group. For convenience,
44 the tags for the test group should be near the top of the xml file which is used
45 for setting up for the test group test cases.
47 The following is an example for the test group, functional-tests/testcases/security/pwd_storage,
51 Place group-specific test information here.
53 #@TestGroupPurpose To test the security functionality.
57 Some test groups will not have the tag, #@TestSubgroupName.
59 For instance, the test group tags for the Backend group are
62 Place group-specific test information here.
64 #@TestGroupPurpose To test the backend functionality.
69 Each xml file will be treated as a test suite. Each file should contain the following tags......
78 The following example is from the test suite, MD5 Tests, which is located in
82 Place suite-specific test information here.
91 Each functional test xml file will have multiple test cases.
92 Each test case should have the following tags........
103 The tags should be located near the beginning of each test case.
106 correlation to match each test case with the proper test suite.
109 which this test case is testing. Do not add the hyperlink to the issue web page.
112 As many #@TestStep tags may used to define the steps that are involved in each test case.
113 There should be one #@TestStep tag for each step. There is no limit to the number of test
114 steps which may be defined. Each test step may have multiple lines.
122 Place test-specific test information here.
137 Note that this example contains three test steps.
140 Place test-specific test information here.
174 for functional test files to parse. The parsing tool will only search one or two levels below
180 java files are parsed for test specifications rather than xml files. The file format must be