Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add a story for exporting tests into nitrate #83

Merged
merged 1 commit into from
Jan 22, 2020
Merged

Add a story for exporting tests into nitrate #83

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 45 additions & 3 deletions stories/cli/test.fmf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,9 +47,51 @@ story: 'As a user I want to comfortably work with tests'
documented: /docs/examples#convert-tests

/export:
story: 'I want to export test metadata into desired format.'
example: tmt test export --format yaml
implemented: /tmt/base
story: 'I want to export test metadata.'

/format:
story: 'I want to export test metadata into given format.'
example: tmt test export --format yaml
implemented: /tmt/base

/nitrate:
story: 'I want to export test metadata into nitrate.'
example: tmt test export --nitrate
description: |
In order to keep metadata in sync with the old test
case management system we need to export selected set
of attributes back to nitrate. The full fmf object
identifier should be added to the structured field
under the key ``fmf``. A warning should be added to
the structured field informing users that the test
metadata are now maintained in git.

Below is the list of supported ``fmf`` attributes and
corresponding nitrate fields:

* component — components tab
* contact — default tester
* description — purpose-file in the structured field
* duration — estimated time
* enabled — status
* environment — arguments
* path — not synced
* relevancy — relevancy in the structured field
* result — not synced
* summary — description in the structured field
* tag — tags tab
* test — not synced
* tier — tags (e.g. ``1`` synced to the ``Tier1`` tag)

The following attributes, if present, should be
exported as well:

* extra-hardware — hardware in the structured field
* extra-pepa — pepa in the structured field

They have the ``extra`` prefix as they are not part of
the L1 Metadata Specification and are supposed to be
synced temporarily to keep backward compatibility.

/coverage:
story: 'Test coverage overview'
Expand Down