Книга: Microsoft Windows Embedded CE 6.0 Exam Preparation Kit
Debugging a Custom Test
Debugging a Custom Test
Because Tux tests rely on code and logic implemented in Tux DLLs, it might be necessary to debug the test code. One issue worth mentioning is that you can set breakpoints in your test routines, but when code execution halts on those breakpoints, you lose the connection between the client-side application (Clientside.exe) and the workstation server application (CETest.exe). Consider using debug messages instead of breakpoints. If you must use breakpoints for thorough debugging, run Tux.exe directly on the target device in standalone mode, as mentioned earlier in this lesson. You can display the required command line in the workstation server application when you right-click the test and select Edit Command Line.
Оглавление статьи/книги
Похожие страницы
- Chapter Review
- Application Verifier Tool
- Creating a Custom CETK Test Solution
- Creating a Custom Tux Module
- Defining a Custom Test in the CETK Test Application
- Custom CETK Test
- Microsoft Windows Embedded CE 6.0 Exam Preparation Kit
- Chapter 12. Debugging your scripts
- Debugging, a necessity
- Bash debugging tips
- System tools used for debugging