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

Refactor Test Cases for TMC code refactoring

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

Details

    • Obs Mgt & Controls
    • Hide

      The feature enhances code modularity. The improved Tango interface layer is more mature and provides additional features for TMC code. It also ensures that the alarm handling is not affected and thus ensures the robustness of the Tango interface layer.

      The improved documentation will provide a better understanding of the Tango interface layer to the SKA developers.

      Show
      The feature enhances code modularity. The improved Tango interface layer is more mature and provides additional features for TMC code. It also ensures that the alarm handling is not affected and thus ensures the robustness of the Tango interface layer. The improved documentation will provide a better understanding of the Tango interface layer to the SKA developers.
    • Hide

      Refactored test cases used to successfully test the refactored TMC in SKAMPI

      Show
      Refactored test cases used to successfully test the refactored TMC in SKAMPI
    • 2
    • 15.6

    • PI24 - UNCOVERED

    Description

      • This feature clones SP-1527 TMC Code Refactoring. It is proposed to refactor the test cases

       

      • Current test cases are written around Tango commands. Refactored test cases enables to write test cases to test the command classes and helper methods, making the test cases modular and simpler. Scope of this feature is restricted to refactor the test case of CentralNode Mid, SubarrayNode Mid and CSPSubarrayLeafNode Mid.

      ---------------------------------------------------------------

      Earlier details in SP-1527 for reference only

      • The feature extends the work done in PI#9 to refactor TMC nodes and achieve better separation between application logic and Tango implementation. The work includes the implementation of additional APIs in the Tango interface layer. This facilitates to get/set the device attributes values in an easier way and also provide more options while subscribing to the events of other devices.
      • TMC should make use of the new version of the Tango interface layer. 
      • Develop a sample code that consumes the APIs provided by Tango interface layer.
      • Documentation:
      • The documentation of the Tango interface layer should also be improved. Providing a sample code that specifies how the APIs of the Tango interface layer can be utilized to develop SKA applications will be useful. Also, consider providing a sample that focuses on utilizing the APIs in non-tango applications.
      • Verify that the alarms are raised by tmalarmhandler based on changes in the attributes of tmc devices. This is to ensure that the implementation of the Tango interface layer has not impacted the alarm handling.
      • MCCS and OET code has some implementation for abstracting Tango APIs. Some discussions and exploration can be done to check if the work of these teams can be consolidated in a single codebase/library so that code is not duplicated.

      Attachments

        Issue Links

          Child Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SS-8 Technical Debt - Feature Set

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done
          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-2404 Observational Scan (including configure) for TMC in Mid

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded

          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-2402 Basic Subarray Resource Allocation for TMC Mid

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

          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-1527 Extension work of TMC code refactoring

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

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                a.dange Aditya Dange
                Votes:
                0 Vote for this issue
                Watchers:
                3 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