Handling situations when TestBase fails to generate test data (e.g. constraint is UNSAT)
Detected in build:
Published in build:
The situation when TestBase fails to provide data for a test situation should be handled in the following way:
- A warning message explaining the reason must be printed.
- Some default data (e.g zero) must be provided. Leaving a resource (register) uninitialized is incorrect.
Now MicroTESK prints an abrupt message and leaves the resources uninitialized.