The term debugging can have many different meanings. However, the literal meaning of debugging is the removing of bugs from your code. A debugger is programmer tool that is attached to your running program and allows you to examine the code, doing stepwise execution, looking at variables and registers. In our case, the running program is your test harness consisting of your system-under-test together with the test execution machine and the respective test case.
In complicated systems, test cases tend to become complicated too. If a test case fails, it is the task of the tester to find the root cause. Failed tests can have various causes e.g.:
- Requirements not free of interpretation,
- faulty test case derivation
- faulty test implementation
- bug in the code
For the last case, it is useful to analyze the states, signals and progressions in the code step by step in order to narrow down the cause of the misbehavior to a few areas in the code.
To support this, we have implemented a Visual Studio connection for debugging in TPT18. If you are not using Visual Studio Enterprise or Professional 2017 and 2019, we will continue to support Eclipse CDT to allow you to debug.
Beside of this Debugging on target is also possible via Lauterbach Trace32 or PLS UDE.
We hope you like it.