action #46670

openQA Tests - action #15132: [saga][epic] Better structure of test plans in main.pm

action #44360: [epic] Parameterize test suites within job groups

Create import for format defined in #46667

Added by mkittler about 1 year ago. Updated 9 months ago.

Status:ResolvedStart date:25/01/2019
Priority:NormalDue date:
Assignee:cdywan% Done:

20%

Category:Feature requests
Target version:-
Difficulty:
Duration:

Description

  • Create import for format defined in #46667
  • Allow posting the document via openQA's REST API.
  • This would be a uni-directional sync from that document into the openQA database.
    • So rows not present in the document are removed in the openQA database.
    • New rows are inserted and existing ones might be updated.
  • Be sure to validate the document.

History

#1 Updated by cdywan about 1 year ago

  • Assignee set to cdywan
  • % Done changed from 0 to 20

#3 Updated by cdywan 12 months ago

As discussed in the openQA meeting the editor will use a "preview" mode to demonstrate the changes to expect while reverting behind the scenes, which makes it safe for people to play with and find out how it works.

#4 Updated by mkittler 11 months ago

Additional PR: https://github.com/os-autoinst/openQA/pull/2056

Note that the current implementation creates/updates/deletes job templates and creates new/empty test suites if a test suite is missing. It requires products and machines to be already present. We should discuss whether this is ok or should be changed.

Show far the UI showing the YAML relies on the export. Likely this is not good enough because it wouldn't preserve comments or references. If that's right the import should maybe store the raw YAML as well to be able to present it in the editor UI. The export could of course still be used if no raw YAML is present yet or if an export is explicitly wanted.

#5 Updated by cdywan 11 months ago

mkittler wrote:

Show far the UI showing the YAML relies on the export. Likely this is not good enough because it wouldn't preserve comments or references. If that's right the import should maybe store the raw YAML as well to be able to present it in the editor UI. The export could of course still be used if no raw YAML is present yet or if an export is explicitly wanted.

Right. To start with we're only supporting the "preview" mode. People can play with it, and see how it works but no changes to the database will be retained.
Storing the edited YAML and leaving it in the hands of users is the next step.

#6 Updated by cdywan 11 months ago

CodeMirror support gh#2063

#7 Updated by mkittler 11 months ago

  • Status changed from New to In Progress

I think this is in progress by now :-)

#8 Updated by okurz 10 months ago

  • Category set to Feature requests

#9 Updated by okurz 10 months ago

  • Description updated (diff)
  • Category deleted (Feature requests)

#10 Updated by okurz 10 months ago

  • Category set to Feature requests

oops, sorry. re-set the category

#11 Updated by cdywan 9 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF