NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Software > MaintenancePlans > MnCMaintenanceProcess > PerformIntegrationTests

Changes | Index | Contents | Search | Statistics | Go

Performing Integration Tests

• Administration Details
• Prepare for Integration Tests
• Perform Integration Tests
• Recover from Integration Tests

Administration Details

1. Copy the scheduled dates for testing onto the SddCalendar as soon as they are available for the cycle.
2. Remind MR Leads whose MRs have not completed sponsor testing (i.e., no ) to schedule their Sponsors for test time during Integration Testing.
3. Make sure that a discussion of the upcoming testing activities is covered in a SDD group meeting. The biweekly meeting is a good forum.
4. Write a draft of the release notes and forward them to the group for review.

Prepare for Integration Tests

1. Until most the bugs have been found and fixed, run the integraton tests out of the integration directory (/home/gbtversions/integration and /home/sparrow/integration).
2. For the final integration test run create a new version following CreatingNewMCVersion and BuildingSparrow procedures. Most the problems encountered when first switching to this version should have to do with failed builds or installs.
3. Review the configuration files (/home/gbt/etc/config/*.conf including /home/gbt/etc/config/resetbox.list to see if the new release requires any changes. For each change, each file will need two copies: one with the old versions as a suffix and one with the new version, e.g., system.conf.6.3 and system.conf.6.4.
4. Remind MR Leads whose MRs have not completed sponsor testing (i.e., no ) to schedule their Sponsors for test time during Integration Testing.
5. Run the command gbtversion -p to get a list of all patches in the current release.

Perform Integration Tests

1. Switch version following SwitchingMCVersions and perform checks listed in PostMaintenanceProcedure for this version. Note that if a new version of resetbox.list is needed the switch for that file will have to be done manually.
2. If CLEO contains version-dependent changes then use the test version of CLEO, either by export CLEODIR=~rmaddale/Tcl; cleo or cleo -cleodir ~rmaddale/Tcl
3. Allow sponsor testing for all incomplete MRs from the Plan of Record.
4. Run tests or have Leads run tests for all refactored code from the Plan of Record.
5. Test all PATCHES from previous release.
6. Run integration scripts (integration1 and integration2 from project TINT). NOTE: integration1 and integration2 specify a source from the strong HI catalog HI_strong.cat. Use the Cleo Scheduler & SkyView tool to select a source that is up and change 'mySource' to this.
   • During tests observe all Astrid tabs (ObservationManagment, DataDisplay, and GbtStatus) for correctness.
   • gfm should be examined for performance and correct results, and after the initial peaks and focuses in the scripts be sure that the LPCs and LFCs are reasonable (LPCs should be a few thousands arcmins and the LFC should be several mm).
   • If the tests run successfully, i.e., gfm displays valid spectral line data, test the data analysis system.
     • If a version change is not necessary, simply type 'gbtidl' at the command line.
     • If integration tests need to test a new version of GBTIDL, we can't simply switch the symbolic link to the new version, as this would affect all current users. Instead, just use the full path to the new version, /home/gbtidl/VERSION_NUMBER/gbtidl/gbtidl.
     • Now test it out:
       • GBTIDL> online # connects to the online sdfits filler
       • GBTIDL> summary # should show you all the spectral line scans you've done so far
       • GBTIDL> getrec, 0 # will display the very first spectra from the first scan - make sure this has the same shape as the corresponding spectra in GFM
       • GBTIDL> exit # to quit
7. Perform SpigotIntegrationTest to ensure that spigot files are in correct locations and functional. Re-cable to remove the artificial pulsar.

Recover from Integration Tests

1. Switch back to the previous M&C version, following SwitchingMCVersions.
2. Follow the procedures listed in PostMaintenanceProcedure before declaring the system ready for other users.
3. Make sure all sampler2logs are writing their FITS files.
4. Run integration1 from TREG just to check for a pulse.

-- MarkClark - 26 Jun 2006