Skip to main content

How can I run TQSK tests if I am building my application on a dedicated machine? - Knowledgebase / TQSK - Lauterbach Support

How can I run TQSK tests if I am building my application on a dedicated machine?

When calling the TQSK test script (python), usually the test application is compiled then output files are loaded in TRACE32.
If the build environment is however different from the test environment, the TQSK script needs to be decomposed: the first part is called to build the application on the build machine (computer "A"). TRACE32 should not be called here so the setting need to be changed to nop.
On the test machine (computer "B"), we need to change the compilation step with a copy operation from computer "A".
So, the basic idea described here is to run the test on first computer ("A") only until immediately after the build step and then replace the build step on a second computer ( "B") with a copy operation.

TQSK Build Decoupling 

Build step on computer "A"

1. Extend "environment.cfg":

[command "nop"]
command = python
args =

2. Create empty file "nop.py" in folder "tqskvvsuite< test_suite >test"

3. Disable execution steps in "environment.cfg"/"test.cfg":

practice-commands = "nop.py" @ nop
...
load-symbols = "nop.py" @ nop
...

TRACE32 should not be started on computer "A" anymore during the test execution. All tests should be failing, but afterwards the test applications should be located in "tc-XY/input". Those test applications can now be transferred to computer "B".

Test completion on computer "B"

Change tqskvvsuite< test_suite >environment/env-XY/source/makefile so that it is merely copying the transferred files from computer "A" to "tc-XY/input"

Helpful Unhelpful

Add a comment

ID-0
To prove you are a human, please tell us the text you see in the CAPTCHA image