Simulating failures during testing

Hello,

New registered user of TA here!

Weve just finished integrating TA into our desktop APP and now looking at handling failures. I have a couple of questions:

Is it possible to prematurely expire a trial (to test trial expiry)? Can you completely remove all traces of TA on a test computer so we can easily test clean builds? (Appreciate this kind of defeats the purpose but is there a debug setting) How can we simulate users having to re-authorise their product codes?

Obviously I can hard-code these values during debug testing but thats not a real test and would give us zero confidence in real-world scenarios.

Thanks

>> "Is it possible to prematurely expire a trial (to test trial expiry)? "

No.

>> "Can you completely remove all traces of TA on a test computer so we can easily test clean builds? (Appreciate this kind of defeats the purpose but is there a debug setting)"

You can remove some information. (TA_Deactivate() with erasePKey set to true)

The best way to test "clean slate" is to use VMs and snapshots of the VM.

>> "How can we simulate users having to re-authorise their product codes?"

Set the nDaysBetweenChecks to 1, and then it will verify every day. Only enable that for your debug builds. Better to use our default values.

Reply
Discard post