![\"progress\"](\"https:\/\/sysprogs.com\/w\/wp-content\/uploads\/2017\/08\/progress.png\")
<\/a><\/p>\n<\/p>\n
Overview<\/h2>\n
Embedded Integration Tests\u00a0let you modify the\u00a0flow of the program using the debugger functionality (via commands like ‘Set Next Statement’ and ‘Set variable value’), record the program response and allow adding\u00a0extra checks (e.g. verifying that a variable value falls within a certain range). You can create Embedded Integration Tests inside any embedded project by simply selecting Test->Record Embedded Integration Test: VisualGDB will automatically start a new debug session\u00a0and will stop in the main()<\/strong> function. Now you can use the normal debugging functionality to make your program follow a certain path and check its consistency along the way.\u00a0For example, you can:<\/p>\n VisualGDB will record (and replay when testing) the following actions:<\/p>\n Each time you create a breakpoint or use “Set next statement”, VisualGDB will suggest tagging the corresponding source line by adding a specially formatted comment: This comment will help VisualGDB locate this line when running tests even if the code in the line changes: VisualGDB will show the recorded actions in the “Integration Tests” window and will let you edit them: If you have just checked a variable value by hovering your mouse over it, you can tell VisualGDB to always check for the same value by adding a check. VisualGDB will automatically suggest recently evaluated expressions:<\/p>\n Embedded Integration Tests are stored in test set files (.vgdbtest) that are added to the project via Solution Explorer. You can view and edit the tests by simply opening the test set file in Visual Studio:<\/p>\n Tests from all sets included in a project will automatically appear in the Test Explorer letting you run them as if they were the regular unit tests: VisualGDB will conveniently display the progress of the currently running test\u00a0and give the control back to you if it stumbles upon any inconsistency: You can download VisualGDB 5.3 Preview 7 here<\/a>. As always, we appreciate your feedback, suggestions for more recordable\u00a0actions and\u00a0general ideas, so don’t hesitate to drop us a line via our support form<\/a> or the VisualGDB forum<\/a>.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" VisualGDB\u00a0started supporting unit tests in version 5.2.\u00a0Having\u00a0out-of-the-box support for CppUTest, GoogleTest and TinyEmbeddedTest,\u00a0VisualGDB made it easy to check\u00a0whether every separable component of your system works. However\u00a0the size overhead and the necessity to create a separate test project makes it hard to use them for testing the\u00a0behavior of the entire\u00a0embedded system. So in VisualGDB 5.3 Preview … Continue reading Introducing Embedded Integration Tests<\/span> <\/a><\/p>\n\n
Recorded Actions<\/h2>\n
\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a>You can also\u00a0check the\u00a0consistency of your program by running complex gdb commands and letting VisualGDB validate their output via regular expressions:
\n<\/a><\/p>\nEditing and Running Tests<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nGive It a Try<\/h3>\n