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.

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

Schedule manual test case execution in openQA #95

Open
foursixnine opened this Issue Jan 19, 2018 · 9 comments

Comments

Projects
None yet
6 participants
@foursixnine
Collaborator

foursixnine commented Jan 19, 2018

Project Title: Schedule manual test case execution in openQA

Description:

Since a while now, openQA has been one of openSUSE's gate keeper which ensures that what we build, will work. We automate the OS builds, sync them into openQA and trigger a lot of automated tests. And it would be great to have the possibility to also add manual test cases.

openQA has a great API that can work and allow test developers to upload new tests manually but sometimes a test requires more than just setting the job status.

If you have experience executing tests cases, or writing test cases you already know that there's a lot of information that sometimes you need to introduce when creating a bug.

The whole idea is that a new test case can be added to openQA, attached to a Medium and schedule the jobs based on the user's profile (AKA the worker_class), so that when the user logs in, it is already known what to execute, and simply start the execution. With the possibility of adding evidence, and notes to the test steps.

There are multiple ways to do this, by either adding gherkin stories support to openQA, or by integrating with other tools like kiwitcms.org

Deliverable: A PoC is created, with enough pieces so that it can be further expanded, with it's tests

Mentor: @coolo, @mudler, @foursixnine

Skills: Problem resolution, Systems Integration, Perl, Javascript, HTML, Mojolicious, (Maybe Python)

Skill Level: Medium

Get started:

@atodorov

This comment has been minimized.

atodorov commented Jan 19, 2018

Hey folks,
I'm the project leader for Kiwi TCMS, already CC'ed myself on this issue. I will happily attend your meetings if you like. Let me know if you do have questions.

@coolo

This comment has been minimized.

Member

coolo commented Jan 20, 2018

Thanks for the offer.

@giovanism

This comment has been minimized.

giovanism commented Mar 15, 2018

Hi,
Can I work on this as part of gsoc? I would be happy if someone could tell me where to start.

@coolo

This comment has been minimized.

Member

coolo commented Mar 15, 2018

Hi @giovanism. If you can work on this depends not only on us, but also on the openSUSE project picking proposals and GSOC allocating slots. So it highly depends on your propsal.

And to write a good proposal, it would be good if you follow the 'Get Started' part of the issue. You can also check https://openqa.opensuse.org

@giovanism

This comment has been minimized.

giovanism commented Mar 15, 2018

Great! Thanks @coolo . I'll mail you as soon as I have my first draft.

@Ana06

This comment has been minimized.

Member

Ana06 commented Mar 15, 2018

@giovanism the proposal should be sent through Google at https://summerofcode.withgoogle.com

you should send it in a Google Doc and the mentors will be able to review it there 😉

@yusrideb

This comment has been minimized.

yusrideb commented Mar 26, 2018

Hi,
Can I apply it to other Mojolicious based apps? I need to know where to start

@Ana06

This comment has been minimized.

Member

Ana06 commented Mar 26, 2018

@yusrideb

Can I apply it to other Mojolicious based apps? I need to know where to start

what do you exactly mean?

@foursixnine

This comment has been minimized.

Collaborator

foursixnine commented Mar 26, 2018

@yusrideb This is about integration of two applications: openQA webUI, and Kiwi TCMS. So that manual tests runs are recorded with Kiwi TCMS, and results are uploaded to openQA via rest api.

There's no need to develop a new Mojolicious application. The only missing part is the integration between both applications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment