Project

General

Profile

Actions

action #16188

closed

Easier way to clone jobs for test development

Added by pgeorgiadis almost 8 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2017-01-23
Due date:
% Done:

0%

Estimated time:

Description

In order to contribute to openQA, most of the people I know of, they are cloning a job from [openqa.suse.de] and then they add their test into that. So, while they are writing their new test, they have to run the whole build which might be consisted of 20-30 tests more or less. So, instead of waiting for a number of unreleated tests to finish (waste of time), I would like to propose a functionality where you can run only one = the test you are developing and you are interested into (e.g. java, or unzip).

So far, I managed to do that (credits to @Romanos) by creating a new medium, a new testsuite, a new jobgroup and modifying the main.pm accordingly. As a side effect, I have to play with git stash save and git stash pop and be careful to not submit unwanted changes (this hack) in main.pm. The whole workflow is documented [here] and [here], but instead of working around it, I would prefer an official solution to that problem. Probably you guys have already something in mind ;)


Related issues 2 (1 open1 closed)

Related to openQA Project - coordination #10316: [epic] Better command line options extending "client"New2018-03-27

Actions
Related to openQA Tests - action #44420: [functional][y][timeboxed:6h] proof-of-concept of declarative test schedule definition, e.g. in YAML file(s)Resolvedriafarov2018-11-28

Actions
Actions

Also available in: Atom PDF