UAO Software test plan (Day time)

OS configuration and FLAO software installation

The following step will be done in advance (i.e.: before the allocated telescope daytime), on both test servers at Mt.Graham.

Requires servers on line with final configuration (OS, network, etc.). No interaction with telescope.

  1. Installation of required additional O.S. packages
  2. Installation of FLAO Supervisor code and system set-up
  3. FLAO configuration
  4. Software startup test and configuration verification.
    For each process of each subsystem (AdSec and WFS):
    • Verify access to configuration and calibration files
    • Verify proper communication between subsystems.
    • Verify interaction with RTDB and related RTDB variables.
    • Verify location and content of resulting log files

FLAO System testing (at the telescope, daytime)

Requires: hand over of FLAO servers (one side) to make the test one operational, full access to WFS and secondary on the same single side.

  1. Hardware startup tests. Proper startup of all the components will be checked by means of specific commands (details depends on the specific component)
    1. Adaptive Secondary.
    2. WFS
  2. AdSec new features tests. New features of AdSec functionality will be checked by means of low-level engineering interfaces
    1. New procedure for failure recovering
    2. Test of new Skip Frame algorithm
    3. Test of Failed actuator removal procedure (Seeing limited) a Test of Failed actuator removal procedure (Closed Loop)
  3. Test of engineering interfaces. Low-level engineering interfaces are to be tested by exercising all the commands and verifying the result. the resulting log file records are to be inspected too.
    1. Adaptive Secondary (portions not tested in step B.2)
    2. WFS
  4. Low-level Integration tests
    The main functions will be exercised by means of the engineering interfaces to verify the proper functionality when both AdSec and WFS are working together.
    1. Close loop simulation with no light
    2. Close loop simulation with light source (argos)
      1. Check diagnostic data communication
      2. Check FastDiagnostic functionality
  5. Individual arbitrators test
    1. AdSec Arbitrator.
      All the AdSec Arbitrator functions are to be exercised by means of the related GUI and/or a dummy test client. To be verified:
      • command effect
      • status after command
      • what GUI shows
      • related RTDB variables
      • log records
    2. WFS Arbitrator
      All the WFS Arbitrator functions are to be exercised by means of the related GUI and/or a dummy test client. To be verified:
      • command effect
      • status after command
      • what GUI shows
      • related RTDB variables
      • log records
  6. High-level integration test (AO Arbitrator test)
    1. Base functionality test
    2. AdSec start/stop/set/rest
    3. WFS start/stop. To be verified for all the commands above:
      • command effect
      • status after command
      • what GUI shows
      • related RTDB variables
      • log records
    4. Arbitrator commands test Mode: AUTO
      Performed by means of dummy client generating arbitrator commands. A full command sequence as issued by TCS (PresetAO, AcquireRef, startAO, pause, resume, stop) will be performed. To be verified:
      • Proper execution of commands
      • Sequence of state changes
      • Effect of Stop/Abort commands
    5. Arbitrator commands test. Mode: INTERVENTION
      This part of the test uses also the new FLAO GUI. A full command sequence as issued by TCS will be performed. Interactive functionality of the FLAO GUI will be tested. To be verified:
      • Proper execution of commands
      • Expected functionality of manual commands
      • Functionality of FLAO GUI
      • Sequence of state changes
      • Effect of Stop/Cancel commands
  7. Error condition tests.
    Some error conditions will be caused by means of low-level engineering interfaces to verify proper trapping/displaying of error messages.
  8. AOS/AOSGUI Test
    The AOS/AOSGUI test include:
    • Verify proper communication
    • Verify correct update of status variables
    • Verify correct display of status variables on AOSGUI
    • Check of log messages
Topic revision: r4 - 03 May 2016, LucaFini
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback