Last Modified October 2, 2026
  1. Home
  2. Guides
  3. Must Read Topics
  4. Testing your Implementation

Testing your Implementation of software_DNA

  1. Overview
  2. Testing Tips

 

The DNA Control Panel will allow you to fully test your implementation of software_DNA before releasing your Software. When a new product is created in the Control Panel the status is set to TESTING MODE.

During TESTING MODE you can generate/upload Activation Codes, test all the software_DNA processes (activations, re-activations, revokes, Anti-Fraud, etc..) to ensure that your application and software_DNA are working properly before release. During TESTING MODE none of the activations will be billed to your account.

Please note, that while in TESTING MODE, there are limits placed on code generations (maximum 10 per request), uploads (maximum 1KByte file size) and a maximum of 50 Activation Codes and 50 Evaluation Codes. These limits and test codes are removed when the TESTING MODE is terminated

When your testing is complete, you can terminate TESTING MODE via the Product Configuration page. When you terminate TESTING MODE, all the Activation codes and Evaluation codes for that product will be deleted and all the counters will be reset to zero. From this point on, all activations will be billed to your account.

You can continue to test the software_DNA process free-of-charge after launch by using "Test Codes" that you create from the DNA Control Panel.

See License Codes  

Testing TIPS - Pre-Launch
Activation

Attempt to mirror the same process your customer will use to download, extract, and install your Software.

Then proceed with the activation process using a new test Activation Code. You can verify the state of an Activation Code before and after in the Code Info screen. Use the Codes -> Search menu in the DNA Control Panel.
Re-Activation

You can trigger a re-activation process by using the same Activation Code to activate the Software on another computer.

You can also trigger the re-activation process by deleting the "CDM" License file and restarting the Application on the same computer.

Validation

Exit the Software and re-start the Software. This will trigger the Validation process based on the Validation Level you have selected. The Software should run normally. For Level 2 and Level 3, this may also generate a DNA Server Validation (assuming there is Internet connectivity) which you can monitor from the DNA Control Panel in the Code Info screen. Use the Codes -> Search menu in the DNA Control Panel.
Multiple computer testing and softWORKZ testing support

Highly recommended that the above be done on multiple computers with different hardware, with multiple software and OS configurations.

We will be happy to help you in the testing of your implementation of software_DNA by performing the above on our own multiple computers and provide you feedback on your implementation of software_DNA at no additional charge.
Evaluation Codes

When testing with Evaluation Codes, the DNA Server will allow you one Evaluation Code per <email> address or per <machineID> with which to test the process for Evaluation Codes. You can reset the History of an Evaluation Code to allow you to do more testing from the Codes menu.
WARNING

While you are testing, and if you have generated multiple transactions that violate your licensing settings or "in error", you may trigger the IP Lockout mechanism. Your IP address would be banned for a period of time and none of the transactions with the DNA Server will be processed. If you believe you are in IP Lockout mode, go to the Event Log for the product, and click on Show Warnings. Any IP addresses in IP lockout will be shown and can be reset
 
WARNING

Server Validations are constrained to one(1) per day. While testing server-based features such as License Disable/ Ban, remember that the next server validation will not occur until the next day, ex: the License Disable /Ban would only take effect on the next day.