QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

coordination #62726

Updated by oorlov almost 5 years ago

## Motivation 

 The reason to create the separate Gem for Client API is to separate logic layers, that will allow us to use MVC-like pattern in tests architecture. Also, it will allow to reuse the Gem during CI of YaST modules without being forced to duplicate the logic for the Client API. 

 ## Acceptance Criteria 

 1. Ruby Gem is created; 
 2. The API contains only generic API methods to access to libyiu (e.g. click(), get_text(), send_keys() etc.); 

     2a. Consider UI elements representing as separate objects (e.g. Button, Table, TextField) with the actions that could be performed on them (e.g. send_keys() exists for TextField but does not exist for Button); 
 4. 3. Each method well documented.

Back