Opened 10 years ago

Last modified 9 years ago

#1252 new defect

IZ311: Missing TS test for sdmadm uninstall_host command

Reported by: torsten Owned by:
Priority: high Milestone:
Component: testsuite Version: current
Severity: Keywords: hedeby
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=311]

        Issue #:      311             Platform:     All           Reporter: torsten (torsten)
       Component:     testsuite          OS:        All
     Subcomponent:    hedeby          Version:      current          CC:    None defined
        Status:       NEW             Priority:     P2
      Resolution:                    Issue type:    DEFECT
                                  Target milestone: milestone 1
      Assigned to:    crei (crei)
      QA Contact:     crei
          URL:
       * Summary:     Missing TS test for sdmadm uninstall_host command
   Status whiteboard:
      Attachments:

     Issue 311 blocks:
   Votes for issue 311:     Vote for this issue


   Opened: Tue Nov 10 06:42:00 -0700 2009 
------------------------


Description:
The Hedeby testsuite currently has no dedicated test for the sdmadm
uninstall_host command.

There exists a helper function hedeby_uninstall_managed_host (defined in the
install test) that is used in tests for issue 633 and 640. This function only
covers the uninstallation of a managed host, not of the master host (CLI switch
-master).

The normal hedeby_install test uses the remove_bootstrap_config command and not
the uninstall_host command.

A dedicated test that tests the uninstallation of all managed hosts and the
master host (in order to cover both cases and all architectures/OSes present in
the TS) would greatly increase the test coverage. Furthermore, this test needs
to ensure that the uninstallation executed properly (spooling files and
bootstrap information needs to be removed).

Evaluation:
High priority, as currently this needs to be tested manually for different
combinations of OS/architecture for every release.


Suggested Fix:
Write the described TS test.


Work Around:
None, manual tests are not really an good option.

Analysis:
no further analysis needed.

How to test:
Write the described TS test.

ETC: 1.5 PD

Change History (0)

Note: See TracTickets for help on using tickets.