Overview

The Bosch Gateway IoT Software Runtime Validator allows testing  of console command groups and their commands. You can create your own group of commands and write tests for those commands using the test scripts; Or, you can use existing commands to periodically perform tests for different scenarios.

Glossary

• TC - test case
• TS - test script
• Script - contains descriptive scenarios for execution of console command
• Group - the group provides commands related to some Service
• TC commands - a command is a word or a series of words used in TC to request an action

The core logic of the test is implemented including loading, parsing and executing of files, invoking console commands and asserting the console commands output, logic for handling of variable outputs is implemented.

TC support

• one-line commands
• multi-line commands
• variables

Structure Description

All Test Scripts (TS) and configurations files are included in the tee/sa/configs/com.prosyst.mbs.test.templates.commands directory, with the following folder structure:

    tee

        sa

            configs

                com.prosyst.mbs.test.templates.commands 

                    group_name (atm, fim, scr, etc.) - folder for each group of console commands

                        tc - folder that holds all scripts

                        resources -  folder that holds helper artifacts

                    com.prosyst.mbs.<module_name>-commands.cfg.xml (atm, da, fim, etc.) - configuration which references the root folders. For example, log and scr for OSGI

            projects

                com.prosyst.mbs.test.templates.commands

                    com.prosyst.mbs.<module_name>-commands.prj.xml (da, fim, etc.) - project for every module