Test-Case Check-List

The Test Case Check List is a separate PDF document you can use as a general guide to creating your own licensing functionality test procedure.

Please view and print the Test Case Check List.

The Test Case Check-List is in PDF format. You must have Adobe Acrobat Reader Installed to view this file. If you do not have Adobe Acrobat Reader 4.0 or later installed, please go to the Adobe site now, download and install this free program:

It contains a list of test case scenarios to help you quickly develop your own list of regular testing processes to ensure your licensing is implemented correctly. Some of the test cases will not apply to your particular license or software design. Simply adopt or adapt test cases as applicable and appropriate.

Note the list is also available separately in the help folder as a PDF document.

Important notes about performing licensing tests

All of your test cases must be performed on a “clean” machine with a fresh license – otherwise you will think you have discovered a bug when in fact there is none. The best way to do this is to use disk-imaging software to rebuild a test environment, however you can use other methods. (See the help section: “Testing and Debugging” for more information).
Each of the test cases should be repeated for each and every operating system you support.
Each of the test cases should be repeated for each and every user permission level you intend on supporting (for NT, 2000 and XP).

Coverage Tests

While you are testing your application we highly recommend that you test for every possible control path through your licensing features. Besides simply testing the licensing features as a normal user would, try and defeat the license in the ways you predict your typical user might. This will require you to repeatedly clean your machine and recompile your license, so get familiar early with how to clean and recompile quickly.

Debugging

The Testing And Debugging section contains valuable information about how to debug any errors that arise. As outlined in that section, if can not immediately find the source of a problem, consider installing the debug ClientProtector server and configuring it to output detailed information. The debug messages, when used in conjunction with the ClientProtector Control Flow-Charts should quickly help you locate the source of the problem.

Tamper Resistance

While you are developing applications keep in mind that there are special safeguards inside the ClientProtector component that will shut down your application if it detects that someone is trying to debug the application. You will almost certainly need to turn off these features while you are debugging your application or else the program will unexpectedly terminate. Turn these features on only after you have completely finished development and are ready to deploy. Please see Tamper Resistance for more information.