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

Develop scripts and dashboards to support MCCS testing in sITF

    XporterXMLWordPrintable

Details

    • LOW ART
    • Hide

      A minimal set of scripts and dashboards are needed for the upcoming MCCS milestones: AAVS3 and sITF. These would be used both by MCCS developers and engineers when they are debugging it, as well as AIV engineers when testing the MCCS. This enabler is focused on the ITF needs.

      Show
      A minimal set of scripts and dashboards are needed for the upcoming MCCS milestones: AAVS3 and sITF. These would be used both by MCCS developers and engineers when they are debugging it, as well as AIV engineers when testing the MCCS. This enabler is focused on the ITF needs.
    • Hide

      Scripts and Dashboards developed for integration and testing of MCCS to be developed as guided by the sITF teams and the TAIV tickets. (Note: The actual testing of the MCCS in the ITF is out of scope of this ticket, however the scripts / dashboards should be exercised by the MCCS team in the spirit of an FAT before handing them over to the sITF integration team. Thus it should be shown minimally that the scripts trigger actions as expected, and the dashboards show the expected parameters. .

      Show
      Scripts and Dashboards developed for integration and testing of MCCS to be developed as guided by the sITF teams and the TAIV tickets. (Note: The actual testing of the MCCS in the ITF is out of scope of this ticket, however the scripts / dashboards should be exercised by the MCCS team in the spirit of an FAT before handing them over to the sITF integration team. Thus it should be shown minimally that the scripts trigger actions as expected, and the dashboards show the expected parameters. .
    • 2
    • 2
    • 0
    • 20.5

    • PI22 - UNCOVERED

    • Team_MCCS mccs_software mccs_ui solution-goal-1

    Description

      Dashboards and tests should be developed that support:

      • Testing and debugging integration of the MCCS components already developed, as well as those that would be developed in PI20.
      • ITF test scenarios especially supporting the integration and verification events as in TAIV-89 and TAIV-782
      • NOT including the TMC interface for these tests is acceptable for PI20 as discussed with AIV teams. However connections directly to the MCCS Tango devices that allow exercising a significant part of the test requirements is expected.
         The actual testing of the MCCS in the integrated AAVS3 is out of scope of this ticket, however the scripts / dashboards should be exercised by the MCCS team in the spirit of an FAT before handing them over to the AAVS3 integration team. Thus it should be shown minimally that the scripts trigger actions as expected, and the dashboards show the expected parameters.

      Attachments

        Issue Links

          clones

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-3696 Develop notebooks and dashboards to support MCCS tests in AAVS3

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                v.mohile Mohile, Vivek
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel