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.
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.
https://hackweek.suse.com/18/projects/controlling-and-testing-the-yast-ui-remotely-for-integration-tests-openqa Ladi did some more things for the framework, now package is split into 3 separating qt and ncurses parts, so can be used in minimal setup without dragging qt dependencies.
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?
#16 Updated by JERiveraMoya 11 months ago
- 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