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

extend the test harness for the TMC

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

Details

    • True
    • Obs Mgt & Controls
    • Hide

      Improve the test harness for the TMC so that it can support 

      • writing more succint and clear tests
      • getting more informative test execution reports
      • provide living documentation about the behaviour of the SUTs
      Show
      Improve the test harness for the TMC so that it can support  writing more succint and clear tests getting more informative test execution reports provide living documentation about the behaviour of the SUTs
    • Hide

      see the points in the description

      Show
      see the points in the description
    • 5
    • 5
    • 0
    • Team_OMCPT
    • Sprint 5
    • PI23 - UNCOVERED

    • testing

    Description

      We need to continue the work done in SP-4030 along these lines (in this order).

      1. in SP-4030 we were not able to tackle the issue of refactoring the code of the test harness that handles emulators of tango devices. This needs to be done to increase modularity, modifiability and understandability of the test harness and tests.
      2. Refactor other TMC+X integration tests (TBD); liase with Himalaya, Sahyadri and possibly the new "software integration team" to do so and spread the knowledge
      3. create a library for the tmc-test-harness so that it can be reused across TMC MID and LOW
      4. setup a mechanism so that X-ray pages describing scenarios and test plans can be used as living documentation. This should enable casual users (like managers) to understand what tests have been run, and what is the actual behaviour of the tested system. (This needs to add more details to xray pages: composition of the SUT, all scenarios in a single screen, some way to provide the meaning of the gherkin steps)
      5. put in place a mechanism that can print out (on the stdout in gitlab pipelines) the actual versions of all the components involved in a test (there should be something like this that was implemented by VIOLA/VULCAN)
      6.  a mechanism so that html pages of the test report produced as gitlab artefacts (one thing achieved by SP-4030) can be accessed as links from Xray test plans/test executions
      7. setup a mechanism to declaratively represent the obststate state machine inside the source of the testware and refer to its parts in individual tests that involve subarrays; this should then be used to automatically produce text-only or graphical reports of the level of transition-coverage by a testset/testplan.
      8. explore ways in which gherkin steps can be reused (at least within the TMC testware). This should involve inventing clever ways to parameterize steps and define their meaning (like pre- and post-conditions).

       

      NOTE: all this is way beyond the capacity that will be allocated (no more than 1 person x 5 sprint=5FP). We will do what we can.
      This is expected to be carried out by g.brajnik E.Lena and v.allan .

       

      Attachments

        Issue Links

          Structure

            Activity

              People

                g.brajnik Brajnik, Giorgio
                g.brajnik Brajnik, Giorgio
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 5.0

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

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel