Warning, /libraries/qca/unittest/TestPlan is written in an unsupported language. File is not indexed.
0001 QCA Test Plan 0002 0003 There are two types of tests that you should consider running on your 0004 QCA build - manual functionality tests, and automated "self checking" 0005 tests. 0006 0007 You should start with a couple of quick manual tests, then do the 0008 automated tests, and then conduct more sophisticated manual tests. 0009 0010 0011 0012 Initial Manual Testing 0013 0014 The fist step is to use the "qcatool" command line tool to verify 0015 basic operation. 0016 0017 0018 Test 1 - Verify startup 0019 0020 Execute the "qcatool" application with no arguments 0021 0022 Expected result: Information on usage of the application is 0023 displayed. 0024 0025 0026 0027 Test 2 - Verify application version 0028 0029 Execute the "qcatool" application with the "--version" option 0030 0031 Expected result: Information on the version of QCA and the version of 0032 qcatool is displayed. 0033 0034 0035 0036 Test 3 - Verify plugin can be loaded 0037 0038 Execute the "qcatool" application with the "plugins" option 0039 0040 Expected result: The plugin paths are displayed (which correspond with 0041 the appropriate plugin directory for Qt, and the current 0042 directory). 0043 0044 The list of providers is displayed, or "(none)" is displayed if no 0045 providers are installed. Note: "(none)" should not be displayed if any 0046 providers are installed. 0047 0048 0049 0050 Test 4 - Run "self checking" tests 0051 0052 Note: this test does not exercise any providers unless the providers 0053 are installed. 0054 0055 Note: automated unit testing with qmake is experimental. 0056 0057 Run "make test" in the build directory. 0058 0059 Expected result: All (23) tests pass. 0060 0061 0062 0063 Additional "self checking" tests 0064 0065 Depending on test requirements, consider running additional unit tests 0066 that are not in the "make test" set. For example, to run the unit 0067 tests for TLS Server Name Indication, run the "veloxunittest" test 0068 application from the "unittest/velox" directory. 0069 0070 Note that tests outside the "make test" set are potentially fragile, 0071 and should not be expected to pass in all circumstances. Nor should 0072 the tests be expected to fail if there is a problem. You should ensure 0073 that you understand what the test is supposed to be checking before 0074 running the test and attempting to interpret the results. 0075 0076 0077 0078 Additional manual tests 0079 0080 Depending on test requirements, consider using "qcatool" to check for 0081 additional functionality. 0082 0083 Depending on test requirements, consider using code in the "examples" 0084 directory to verify functionality. 0085