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

Simulation Mode: Implement Telescope Startup E2E scenario

    XporterXMLWordPrintable

Details

    • Feature
    • Must have
    • PI13
    • None
    • Services
    • Hide

      Startup Telescope tests as developed in the continuous integration plan can be executed as part of the SKAMPI low pipelines running in STFC.

      Show
      Startup Telescope tests as developed in the continuous integration plan can be executed as part of the SKAMPI low pipelines running in STFC.
    • 2.5
    • 2.5
    • 0

    • Flow USE-29 Startup Telescope - Basic Flow

    • Team_VULCAN
    • Hide
      • The 'at-111' branch was used to integrate the component helm charts in SKAMPI, to decouple it from the gitlab ci changes which had removed the low enevironment
      • BDD tests for the Basic and alternate flows of the Use case - Telescope Start up, are written, implemented and integrated in GitLab CI pipeline for automated test runs. X-Ray BDD test: https://jira.skatelescope.org/browse/XTP-4445
      • The same are integrated to X-ray so the test execution results are visible in JIRA Test Execution: https://jira.skatelescope.org/browse/XTP-4522
      • Use case to Tests and then to test execution traceability can be seen from the Use case https://jira.skatelescope.org/browse/USE-1. It shows the Test Coverage and gives the Status as OK/NOK depending on the linked Test execution Results.
      • Test logs include the test configuration such as Product version info (chart), Env variables set and any debug log for failed tests.
      Show
      The 'at-111' branch was used to integrate the component helm charts in SKAMPI, to decouple it from the gitlab ci changes which had removed the low enevironment BDD tests for the Basic and alternate flows of the Use case - Telescope Start up, are written, implemented and integrated in GitLab CI pipeline for automated test runs. X-Ray BDD test: https://jira.skatelescope.org/browse/XTP-4445 The same are integrated to X-ray so the test execution results are visible in JIRA Test Execution: https://jira.skatelescope.org/browse/XTP-4522 Use case to Tests and then to test execution traceability can be seen from the Use case https://jira.skatelescope.org/browse/USE-1 . It shows the Test Coverage and gives the Status as OK/NOK depending on the linked Test execution Results. Test logs include the test configuration such as Product version info (chart), Env variables set and any debug log for failed tests.
    • 13.6
    • Stories Completed, Integrated

    • PI22 - UNCOVERED

    • Team_VIOLA

    Description

      Steps:

      1. Add BDD test implementation to SKAMPI

                   1.0 TMC On() cmd (TBC)

                   1.1 LOW.CSP_LMC On() cmd

                   1.2 LOW.CBF On() cmd

                   1.3 MCCS On() cmd

                   

      2. Define the helm charts needed to pull in the test components 

      3. Run the test in Simulation mode only

      Note: Not all the sub-systems helm charts are in SKAMPI yet (except Central Node). 

       

      Task breakdown:

      • *LOW umbrella chart need to be integrated to SKAMPI (Central Node is the only component available at this stage) - can include Alex (ST activity) - SP1 - 1SP (Dep ST) and 3SP for Alex (Indirect)
      • Add BDD tests to X-Ray (including labels, test set, tests etc) - SP1 - Vani - 1SP
      • "SP-2215" branch of SKAMPI to be established - this consists of 'finalised' central node and other components in developmental stage - take the current helm charts of MCCS, Low-CSP and Low-CBF -> this is to prove that the integration works - SP1 - Alex/Malte - 3SP + 3SP(Indirect)
      • Implement the BDD tests using the components from above and run the test - SP1/SP2 - Vani/Malte/Drew (Dep Gerhard) - 5SP + 3SP(Indirect)
      • Show the test execution results in the X-Ray and the link to GitLab CI pipeline - SP2/SP3 - Vani - 1SP
      • Show the Use case to Test Execution traceability in Jira - SP3 - Vani - 1SP
      • *Show the Use case to Test Execution traceability in Jama (Dep on SE team) - SP3 - Vani - 1SP
      • Add the bare minimum instances of MCCS (ex. MCCSTile, MCCSSubrack etc) and re-run the test - Mid SP3 - Drew/Alex - 1SP + 1SP(Indirect)
      • *Add the Low-CSP instance to the SKAMPI branch "SP-2215" and re-run the test (Dep on CREAM) - SP4/SP5 - Drew/Alex - 2SP + 2SP(Indirect)
      • *Add the Low-CBF instance to the SKAMPI branch "SP-2215" and re-run the test (Dep on Perentie) - SP4/SP5 - Drew/Alex - 2SP + 2SP(Indirect)
      • Demo on STFC - SP5 - Vani - 2SP

      Attachments

        Issue Links

          mentioned in

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                g.leroux Le Roux, Gerhard [X] (Inactive)
                m.deegan Deegan, Miles
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.5

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1439.0
                  Total1439.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel