OpenQA testing for desktop search
OpenQA testing for desktop search
Mentors
TBC - I am not sure i can commit to mentoring this year.
Project length
Short ~175 hours, extensible to Long (~350 hours) if preferred.
Description
OpenQA is a testing tool, we are trialling OpenQA to do end-to-end testing of GNOME OS.
Currently there are no tests for desktop search, this is blocked on having some well-defined example content to search through.
There are three steps to make this happen, you could propose to do the first only, or the first two, or all three.
- Collect realistic examples of user content, and set up a CI process to build a disk image with a realistic home directory.
Requirements for this task can be found here: GNOME/openqa-tests#8 (comment 1664309)
As a guide, this may be around 80 hours of work.
- Update OpenQA tests to mount the disk image from (1) at
/home/testuser
This requires basic knowledge of QEMU. There is probably a test in the https://github.com/os-autoinst/os-autoinst-distri-opensuse/ repo that shows how to do this.
This may be 20-40 hours work, depending on experience with QEMU and OpenQA
- Create initial set of tests for desktop search
The idea of OpenQA testing is to have a small set of tests which cover a lot of functionality. The goal would be to find 2 or 3 search queries, which are able to exercise many difficult codepaths within the search infrastructure. We might produce many tests and select the most useful 3 from those.
This might be completed to a minimal within 20 hours but ideally more time would be spent to ensure code coverage is as high as possible. (Note that actually measuring coverage may be too difficult, we might have to estimate based on reading code).
Requirements
Knowledge of scripting languages, e.g. Python (for step 1) and Perl (for step 3).
Basic knowledge of managing virtual machines and disk images with QEMU (for step 1 and 2).
Communication
TBD