Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-826

system tests for newer "MVP"

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Services, Obs Mgt & Controls
    • Hide

      We keep developing system level tests that are used to make sure that the MVP in the staging environment works properly.

      This work should cover more and more of the existing requirements (at least those that apply to the MVP).

      Show
      We keep developing system level tests that are used to make sure that the MVP in the staging environment works properly. This work should cover more and more of the existing requirements (at least those that apply to the MVP).
    • Hide
      1. one or more test sets in gherkin are created
      2. they can be run either interactively or from within the CICD pipeline of the skampi repo
      3. their test artefacts are automatically uploaded to Jira
      4. in Jira there are links between tests, test sets and requirements.
      5. Jira requirement coverage reports can be generated which show (requirement) coverage levels.
      Show
      one or more test sets in gherkin are created they can be run either interactively or from within the CICD pipeline of the skampi repo their test artefacts are automatically uploaded to Jira in Jira there are links between tests, test sets and requirements. Jira requirement coverage reports can be generated which show (requirement) coverage levels.
    • 3
    • 3
    • 1.333
    • Team_NCRA
    • Sprint 5
    • Hide

      Linked user-stories

      Show
      Linked user-stories
    • 9.4
    • Stories Completed

    • PI24 - UNCOVERED

    Description

      As the functionality of the MVP increases, new sets of system tests need to be developed. For example, acceptance tests for the Abort command (SP-754).

      If completion of the current BDD PoC https://jira.skatelescope.org/browse/SP-587 will be successful then a much larger test set in gherkin should be developed to cover the new capabilities of the MVP. Possibly by adopting the same approach (involving an informal group of testers) and linking those tests to higher level requirements.

      This is also related to the first solution goals for PI6 described in https://confluence.skatelescope.org/x/PwF8BQ: "Provide a Scheduling-Block-driven MVP that can be easily and effectively deployed understood and operated through enough tooling in the development environment, logging, and error handling, with full trace of states for all TANGO devices." that implies testing the behavior of the MVP, not just its results.

      Attachments

        Issue Links

          relates to

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-302 Control the MVP using the first Scheduling Block Instances

          • Not Assigned - Priority is not assigned yet.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-754 Implement Abort and Restart commands in TMC

          • Not Assigned - Priority is not assigned yet.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-755 SDP MVP can Abort a workflow

          • Not Assigned - Priority is not assigned yet.
          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                g.leroux Le Roux, Gerhard [X] (Inactive)
                g.brajnik Brajnik, Giorgio
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1142.0
                  Total1142.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel