Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Initial tests for Yomi #8163

Merged
merged 8 commits into from Aug 16, 2019
Merged

Initial tests for Yomi #8163

merged 8 commits into from Aug 16, 2019

Conversation

aplanas
Copy link
Contributor

@aplanas aplanas commented Aug 9, 2019 •
edited

Minimum set of tests to validate Yomi images in openQA.

foursixnine
foursixnine requested changes Aug 9, 2019
View reviewed changes
Copy link
Member

@foursixnine foursixnine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I have concerns with the download of isos, I think this looks fine in general, except for the big ammount of tying that might be prone to mistyping issues, therefore scripting that part should be good enough

tests/yomi/start_qemu.pm Outdated Show resolved Hide resolved
tests/yomi/yomi_scenario.pm Outdated Show resolved Hide resolved
@aplanas aplanas force-pushed the yomi branch 12 times, most recently from caefdeb to af917b5 Compare August 12, 2019 07:28
@aplanas
Copy link
Contributor Author

aplanas commented Aug 12, 2019

@foursixnine ready for re-review. The CI complains about unused module. So far I am not sure where to load them, as I plan to use via the SCHEDULE parameter from openqa-clone-job.

Any suggestion here?

@Vogtinator
Copy link
Member

Currently this test as-is can't be used for Tumbleweed as it always tests the hardcoded systemsmanagement:yomi repo and iso. What about using the .iso built in oS:F (like the vagrant tests do it) and the packages from the plain repos?

@aplanas
Copy link
Contributor Author

aplanas commented Aug 12, 2019

@Vogtinator yes, I was thinking to pass the repo as variable in the env, so I can use the same set of tests for testing the devel project and Factory.

The current state makes more relevant testing s:y before it goes to Factory.

@aplanas aplanas force-pushed the yomi branch 3 times, most recently from 3c366b2 to d40237e Compare August 13, 2019 08:12
@aplanas
Copy link
Contributor Author

aplanas commented Aug 13, 2019

Run example here: https://openqa.opensuse.org/tests/1005632#

@aplanas aplanas force-pushed the yomi branch 2 times, most recently from d07a80e to 8ec88c1 Compare August 13, 2019 11:42
foursixnine
foursixnine previously approved these changes Aug 13, 2019
View reviewed changes
@foursixnine
Copy link
Member

@aplanas please tidy the code, to merge :) (make prepare && make tidy should do the trick)

@aplanas
.gitignore: ingore emacs backup file extension
1407fd9
@aplanas
yomi_formula: install and configure yomi-formula
e87cc9e
@aplanas
fetch_iso: fetch JeOS image for Yomi
34872b5
@aplanas
start_qemu: launch QEMU and the inner minion
288232b
@aplanas
yomi_scenario: prepare and execute a single test
573ef14 
You can use the variable $TEST to specify the scenario to run. For
example:

TEST=simple

will run the `simple` test (single node, msdos partition, openSUSE)

For a list of valid scenarios, check the source code of the test.
@aplanas
Copy link
Contributor Author

aplanas commented Aug 16, 2019

@foursixnine Thanks, done. Now is green.

@foursixnine foursixnine merged commit bf9d905 into os-autoinst:master Aug 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@foursixnine foursixnine foursixnine approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@aplanas @Vogtinator @foursixnine