action #45410
Updated by riafarov over 5 years ago
## Motivation As a job reviewer or developer taking a look on openQA job I would like to have general understanding of the test module steps without reading code. As it's done for the unit tests frameworks, one can write expectation, and message what is checked. Similarly in openQA, it's not always clear what we check and what was expected. With such functionality test developers could provide information (e.g. `assert_screen 'generic-desctop', msg => "Verify that window is closed`). closed`.