action #50726
closed
coordination #36712: [saga] Use YaST specific framework for GUI testing
coordination #50672: [funtional][y][epic] Use libyui-rest-api for YaST modules testing
[functional][y][timeboxed:16h] Explore different ideas which technologies to use with libyui-rest-api
Added by riafarov about 5 years ago.
Updated over 3 years ago.
Description
Motivation¶
We have a chance to run same tests for multiple stages of the development which will significantly simplify bisection during the failures investigation.
I as a YaST developer want to execute same integration tests as we run for build locally.
I as a QA engineer want to run same tests on multiple development phases to simplify bisection during the investigation.
Further details¶
We need to communicate with YaST team to come with the stack of technologies to be used, so both parties can contribute and easily understand setup.
For QA it's given, that results have to be wrapped in openQA.
- Subject changed from [f to [functional][y][timeboxed:16h] Explore different ideas which technologies to use with libyui-rest-api
- Description updated (diff)
- Due date set to 2019-05-07
- Category set to Spike/Research
- Due date changed from 2019-05-07 to 2019-05-21
- Due date changed from 2019-05-21 to 2019-06-04
- Blocks action #50723: [functional][y] Automate yast2 hostname using libyui-rest-api for tumbleweed added
- Status changed from New to Workable
- Due date changed from 2019-06-04 to 2019-06-18
- Due date changed from 2019-06-18 to 2019-07-02
- Priority changed from Normal to High
- Due date changed from 2019-07-02 to 2019-07-16
- Assignee deleted (
cwh)
We need to progress here not to lose momentum. Christopher, could you please, update ticket with your findings so far?
- Assignee set to JERiveraMoya
- Status changed from Workable to In Progress
For YaST development rspec is used for unit testing. Not sure if it can be used or anyhow makes sense to be used for integration tests.
At least this would mean to use a containerized test environment for being able to run those tests manually.
I still like the idea of using cucumber. What were the reasons for not using it?
- Status changed from In Progress to Feedback
@cwh I like cucumber too but for the moment we are thinking on term of complexity and cucumber is a complex framework.
According to discussion with the team, I created a mock-up transforming the initial simple ruby script in some rudimentary rspec which allows BDD: https://github.com/jknphy/sandbox-libyui-rest-api
I could only found allure as a suitable reporting testing framework (for ruby or python). Other frameworks like Extent Report or TestNG are attached to Java or very attached to Selenium or they are testing framework and not reporting framework.
- Copied to action #54305: [functional][y][timeboxed:16h] Explore different ideas which technologies to use with libyui-rest-api added
- Copied to deleted (action #54305: [functional][y][timeboxed:16h] Explore different ideas which technologies to use with libyui-rest-api )
- Status changed from Feedback to Resolved
Also available in: Atom
PDF