View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000213||HTML||[All Projects] General||public||2019-02-03 16:09||2019-02-03 16:54|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0000213: Using the action hierarchy abstraction for automated UI testing|
The abstraction of representing system-human interface as a hierarchy of actions may be used not only for generating a Web user interface but also for testing is in the UI-independent way.
Tests may be parameterized by device types, orientation, screen resolution - each permutation returning an action hierarchy backed by a driver with specified configuration.
Action drivers may pull metadata information from the system being tested and thus require little-to-no manual coding.
The action driver may capture screenshots and generate slideshows and videos. In this case tests may be used not only to test a piece of the UI functionality, but also to automatically produce educational
Tests may be written in different ways, e.g. JUnit or BDD scripts, e.g. in Gherkin. One option is creation of application-specific DSL using Xtext and the action hierarchy specification. The base syntax of such DSL may be based on Gherkin and roles and steps will be application-specific
In the above example:
The language/UI/action driver may hide the details on how to get to the initial state (e.g. log-in) and randomly use different options on getting to the initial state. Those options would correspond to already defined scenarios. A scenario in this case may be thought as a transition from a state A (action A) to state B (action B). Such transitions may be composed to. E.g. A -> B and B -> C may be composed to A -> C.
Recorded scenarios screenshots may be organized in a number of different ways:
The documentation for recorded scenarios may be generated as a static web site or as a dynamic web application, perhaps with access control.
|Tags||No tags attached.|
|2019-02-03 16:09||pvlasov||New Issue|
|2019-02-03 16:17||pvlasov||Summary||Using an action hierarchy abstraction for automated UI testing => Using the action hierarchy abstraction for automated UI testing|
|2019-02-03 16:17||pvlasov||Description Updated||View Revisions|
|2019-02-03 16:54||pvlasov||Description Updated||View Revisions|