Actions
action #13590
closedpersistent description field for test suites
Start date:
2016-06-19
Due date:
% Done:
0%
Estimated time:
Description
user story¶
As a new user I want to know more details about test suites to better understand what they are about, e.g. responsible persons, intentions, related fate entries, etc.
acceptance criteria¶
- AC1: everyone can see the description for a test suites over UI (e.g. displayed in each corresponding job)
- AC2: As AC1 but over API
- AC3: operators can write/edit/delete descriptions for each test suite
tasks¶
- Add description field to database (testsuites table)
- CRUD via API
- Add web UI either in each job or in admin view
Updated by mkittler over 7 years ago
- Copied from action #12400: persistent description field for job groups added
Updated by okurz over 7 years ago
- Related to action #13904: test suite names on test overview should support links to description pages added
Updated by okurz over 7 years ago
- Status changed from New to In Progress
Updated by okurz over 7 years ago
- Status changed from In Progress to Feedback
PR merged, waiting for deployment, then write announcement and suggestions for osd/o3, e.g. mailing list post to openqa@suse.de
Updated by okurz over 7 years ago
https://github.com/os-autoinst/openQA/pull/1168 adds documentation to openQA, waiting for that, then announcing with link to official documentation.
Updated by okurz over 7 years ago
- Status changed from Feedback to Resolved
doc available http://open.qa/docs/#_description_of_test_suites . Also posted on os-fctry and openqa@suse.de mailing lists
Actions