jenkins is a great CI system (continuous integration) with a plethora of plugins available. SUSE QA uses openQA extensively as it excels in distribution and product testing - not only image comparison (common misconception ;-) ). How about combining both in using jenkins with plugins to act as a UI for openQA?
jenkins can be used by test developers and maintainers to get simpler feedback on
what is the current "big picture" of jobs, e.g.
- how many are failing
- since when
- how did the situation change
which failing tests are not claimed, where can I help
who is working on what
people who can fix failing tests, introduced a regression or the ones who want to keep tests running can be informed
- by email
- in IRC
- other means as preferred by the user …
an alternative interface to control an openQA instance
Using the jenkins CI web interface to schedule jobs, control trigger, review maintenance of the openQA server itself
My personal plan is to follow the following steps in this order and priority
- refine goals and technical feasibilities into user stores and/or acceptance criteria and/or acceptance tests
- prepare jenkins and openQA test instances on my computer
- review and install all maybe useful plugins into jenkins
- interface openQA-->jenkins, i.e. one-way first from openQA to jenkins should be enough for first two goals, e.g. by polling in jenkins builds the status of openQA over its REST interface or maybe just the "client" script
- complete one user story using the above prerequisities
- document results and experiences
- implement more user stories
Looking for mad skills in:
Nothing? Add some keywords!
This project is part of:
Hack Week 13 Hack Week 14
This project is one of its kind!