Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,792
    • Issues 43,792
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,417
    • Merge requests 1,417
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #215514
Closed
Open
Created Apr 23, 2020 by Jan Provaznik@jprovaznik🌴Maintainer

Allow passing status for each requirement in CI job report

In the first iteration we assume that job report (JSON file) contains confirmation only for all jobs - something like {"*":"passed"} saying that all requirements passed.

It would be nice to accept state per each requirement, so user could pass in the JSON file state for specific requirements, e.g.:

{
  "requirement_iid1": "passed";
  "requirement_iid2": "failed";
  "requirement_iid3": "failed";
}

Allow the parser to parse and create TestReports for multiple requirements, rather than all at once using *. Add support for parsing status for individual requirements. See !33031 (diffs, comment 353097705).

Related to #215513 (closed) and &2859 (comment 310970936)

Edited Jun 05, 2020 by charlie ablett
Assignee
Assign to
Time tracking