Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-26177

Write the Test Framework of SAL LabVIEW API in Phase 1

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: ts_main_telescope
    • Labels:
    • Story Points:
      3
    • Epic Link:
    • Sprint:
      TSSW Sprint - Aug 3 - Aug 17, TSSW Sprint - Aug 17 - Aug 31, TSSW Sprint - Aug 31 - Sep 14
    • Team:
      Telescope and Site
    • Urgent?:
      No

      Description

      Write the test framework of SAL LabVIEW API. This task begins to construct a framework to test the LabVIEW API for each new SAL update. In the past, we used the component CSC in LabVIEW to test this. Now, we need a framework to test this automatically. The SAL LabVIEW APIs rely on the shared memory, which is not needed for the C++ and JAVA APIs. Therefore, this kind of automatic test framework should be helpful for the maintenance of CSC in LabVIEW. This task is in the phase 1.

        Attachments

        1. getFuncReturn.png
          getFuncReturn.png
          56 kB
        2. iniCtrlSummaryState.png
          iniCtrlSummaryState.png
          66 kB
        3. privateAttributeInControl.png
          privateAttributeInControl.png
          59 kB
        4. segmentFaultInfo
          2 kB
        5. stuckWhenIssueSalEvent.png
          stuckWhenIssueSalEvent.png
          281 kB
        6. summaryStateInIDL.png
          summaryStateInIDL.png
          108 kB
        7. summaryStateInShmem.png
          summaryStateInShmem.png
          106 kB

          Issue Links

          is triggering

          Bug - A problem which impairs or prevents the functions of the product. DM-26379 Missing Control in SAL LabVIEW VI and IDL Information

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-26666 Write the Test Framework of SAL LabVIEW API in Phase 2

          • Done
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-26493 Support the Shared Enum in LabVIEW

          • Done

            Activity

            Ascending order - Click to sort in descending order
            4 older comments
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment -

            Sometimes, the LabVIEW just stuck when issuing the salEvent:

            Show
            ttsai Te-Wei Tsai added a comment - Sometimes, the LabVIEW just stuck when issuing the salEvent :
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment -

            Got the segment fault when just connect and release the SAL: segmentFaultInfo.

            Show
            ttsai Te-Wei Tsai added a comment - Got the segment fault when just connect and release the SAL:  segmentFaultInfo .
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment - - edited

            I used the command line to issue the event by c++ and tested the LabVIEW could get the event or not. It can't. I just got the function return: -100.

            Show
            ttsai Te-Wei Tsai added a comment - - edited I used the command line to issue the event by c++ and tested the LabVIEW could get the event or not. It can't. I just got the function return: -100.
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment - - edited

            Created a new repo for the SAL LabVIEW test:
            https://github.com/lsst-ts/ts_SALLabVIEW_test

            Show
            ttsai Te-Wei Tsai added a comment - - edited Created a new repo for the SAL LabVIEW test: https://github.com/lsst-ts/ts_SALLabVIEW_test
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment - - edited

            Please help to review the PRs:
            1. https://github.com/lsst-ts/ts_SALLabVIEW/pull/6
            2. https://github.com/lsst-ts/ts_SALLabVIEW_test/pull/1

            For the ts_SALLabVIEW, I used the test data from ts_sal commit: 13a69b9 and removed the check of private attributes.

            For the ts_SALLabVIEW_test, I implemented the class to get the data type and vi path by reading the SALLV lvlib. I also implemented the class to run and kill the SAL monitor. For the pipeline test of SAL, I will wait until the SAL v5.0 is ready and do the further implementation.

            Thanks!

            Show
            ttsai Te-Wei Tsai added a comment - - edited Please help to review the PRs: 1. https://github.com/lsst-ts/ts_SALLabVIEW/pull/6 2. https://github.com/lsst-ts/ts_SALLabVIEW_test/pull/1 For the ts_SALLabVIEW , I used the test data from ts_sal commit: 13a69b9 and removed the check of private attributes. For the ts_SALLabVIEW_test , I implemented the class to get the data type and vi path by reading the SALLV lvlib. I also implemented the class to run and kill the SAL monitor. For the pipeline test of SAL, I will wait until the SAL v5.0 is ready and do the further implementation. Thanks!

              People

              Assignee:
              ttsai Te-Wei Tsai
              Reporter:
              ttsai Te-Wei Tsai
              Reviewers:
              Dave Mills
              Watchers:
              Dave Mills, Te-Wei Tsai
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Start date:
                End date:

                  Jenkins

                  No builds found.