https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-07-22T09:02:56ZopenSUSE Project Management Toolqe-yam - action #69184: [y][timeboxed:24h] Design architecture for ruby rspec yast testshttps://progress.opensuse.org/issues/69184?journal_id=3142302020-07-22T09:02:56Zriafarov
<ul><li><strong>Subject</strong> changed from <i>[y] Design architecture for ruby rspec yast tests</i> to <i>[y][timeboxed:24h] Design architecture for ruby rspec yast tests</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/314230/diff?detail_id=311485">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> qe-yam - action #69184: [y][timeboxed:24h] Design architecture for ruby rspec yast testshttps://progress.opensuse.org/issues/69184?journal_id=3145272020-07-24T11:29:43ZJERiveraMoyajeriveramoya@suse.com
<ul></ul><p>In case it could help (as got confused myself with this), I think we are referring to Page-Object Model / Page-Object pattern instead of the MVC, so we are looking for the pattern(s) to use to create our Automation Framework. We can check: <a href="https://blog.testproject.io/2020/06/29/design-patterns-in-test-automation/" class="external">https://blog.testproject.io/2020/06/29/design-patterns-in-test-automation/</a></p>
qe-yam - action #69184: [y][timeboxed:24h] Design architecture for ruby rspec yast testshttps://progress.opensuse.org/issues/69184?journal_id=3177702020-08-10T11:04:02ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Assignee</strong> set to <i>JERiveraMoya</i></li></ul> qe-yam - action #69184: [y][timeboxed:24h] Design architecture for ruby rspec yast testshttps://progress.opensuse.org/issues/69184?journal_id=3180942020-08-11T08:32:11Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2020-08-11</i> to <i>2020-08-25</i></li></ul> qe-yam - action #69184: [y][timeboxed:24h] Design architecture for ruby rspec yast testshttps://progress.opensuse.org/issues/69184?journal_id=3182142020-08-11T13:33:03ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul> qe-yam - action #69184: [y][timeboxed:24h] Design architecture for ruby rspec yast testshttps://progress.opensuse.org/issues/69184?journal_id=3187452020-08-14T06:37:17ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><ol>
<li>Organization created (I added team members to it and the new project)</li>
<li>PoC: <a href="https://github.com/qa-sle-yast/libyui_test_framework" class="external">https://github.com/qa-sle-yast/libyui_test_framework</a></li>
</ol>
<p>For launching the YaST modules, we will run from openQA <code>su -c /bin/sh</code> and type the password once (unavoidable AFIK) and then we will run <code>bundle exec rspec</code>. The way to open the module was unified, check the <a href="https://github.com/qa-sle-yast/libyui_test_framework/blob/master/spec/expert_partitioner/expert_partitioner_spec.rb#L11-L12" class="external">spec</a> although the code perhaps makes more sense to be in the framework instead of the client. <br>
For output validation we could use <a href="https://ruby-doc.org/stdlib-2.7.0/libdoc/open3/rdoc/Open3.html" class="external">Open3</a></p>
<p>Note 1: Ensure loading of the screen is still an issue to be solved when developing the framework, for example in Expert Partitioner in SLE is not enough to wait for the tree to send a selection on the tree, because if the central pane is not loaded, the screen got frozen, not usable, I workarounded that waiting for the central screen, but it does not work fine stable with TW, so it might be require more element to be waited for.<br>
Note 2: I didn't see any issues with port after applying the env variable to reuse the port.</p>
qe-yam - action #69184: [y][timeboxed:24h] Design architecture for ruby rspec yast testshttps://progress.opensuse.org/issues/69184?journal_id=3193092020-08-18T08:48:09ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul>