This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag


About Us

Contact Us

Legal Info

How To Contribute

Security Issues

This web page is no longer maintained. Information presented here exists only to avoid breaking historical links.
The Project stays maintained, and lives on: see the Linux-HA Reference Documentation.
To get rid of this notice, you may want to browse the old wiki instead.

1 February 2010 Hearbeat 3.0.2 released see the Release Notes

18 January 2009 Pacemaker 1.0.7 released see the Release Notes

16 November 2009 LINBIT new Heartbeat Steward see the Announcement

Last site update:
2019-12-14 16:07:05


  1. Test Plan for Linux-HA
    1. Document Control
      1. Document Change Control
      2. Reviewers/Approvers
      3. Change Summary
    2. I. Introduction (Phase 1 Item)
      1. A. References/Related Documents
      2. B. LDP Items
      3. C. Hardware
      4. D. Limitations
      5. E. General
      6. F. Past History
    3. II. Test Plan Overview (Phase 1 Item)
      1. A. Test Approach and Methodology
      2. B. Automatability (and Requirements)
    4. III. Approval Criteria (Phase 1 Item)
    5. IV. Detail Information (Phase 2 Item - FVT Exit)
      1. A. Build/Install/Enablement
      2. B. Parameters (Design/Implementation Details – New Section)
      3. C. Bugs/Defects
      4. D. Firmware
    6. V. Testcase Descriptions (Phase 2 Item – FVT Exit)
      1. A. Naming Conventions
      2. B. Testcase Location
      3. C. Testcases description
    7. Appendix A: Distribution Information
    8. End of Document

Test Plan for Linux-HA

Version 1.0 - 11/09/2005

Owner: Alan Robertson <>

It is the responsibility of the user of this document to ensure that they are using the current version of this document. To validate that your copy of this document is at the latest level, view the latest version of this document:

Document Control

Document Change Control

Initial Release


Review Frequency

At each major revision

Final Page Indicator

End of Document section header


Valid until superseded by a new version/level


Alan Robertson - <>

Change Summary

Review Date

Version Reviewed

New Version (if needed)






Alan Robertson

Alan Robertson

I. Introduction (Phase 1 Item)

A. References/Related Documents




CTS overview


Basic Sanity Check overview


B. LDP Items

LDP Number (LDP)


Included in Product/Package

Targeted Integration Date

Actual Product/Package Release


Linux-HA Release 2




C. Hardware

All Linux-compatible IBM server platforms.

D. Limitations


E. General

Needs a working kernel.

F. Past History


II. Test Plan Overview (Phase 1 Item)

All testing is 100% automated.

A. Test Approach and Methodology

We have two tests we run:

  • BasicSanityCheck (BSC) (takes about 2-3 minutes)

  • CTS (Cluster Test System) – takes about a week

Note that SUSE actively contributes to these tests, and runs them themselves long before we release anything. We also run these tests on “legacy” and CRM configurations.

B. Automatability (and Requirements)

All tests are fully automated.

III. Approval Criteria (Phase 1 Item)

100.0% success of the test run – at least 3000 iterations of CTS, and BSC passing on all relevant architectures. There are rare occasions where the random tests cause some single unique behavior because of something in the test environment. Special exceptions are occasionally made for these occurrences

There is also a class of error called “bad news”. Under normal circumstances, these should never occur.

IV. Detail Information (Phase 2 Item - FVT Exit)


A. Build/Install/Enablement

Basic Sanity Check can simply be installed as an RPM on any single machine. CTS is a complex installation involving a cluster of at least 4 nodes. The more nodes, the slower the tests run. The setup of CTS is described in the cts/README file in the source tree. Fortunately, SUSE already knows how to install and run these tests ;-).

B. Parameters (Design/Implementation Details – New Section)



Valid Values/Sample Input


Expected Output

C. Bugs/Defects

All bugs will be tracked by the [HeartbeatBugzilla Linux-HA bugzilla] which you can find here:

D. Firmware


V. Testcase Descriptions (Phase 2 Item – FVT Exit)

A. Naming Conventions


B. Testcase Location

Installed as part of the package. SUSE tests the software before every one of our releases.

C. Testcases description

Name of testcase

What it tests

Expected result


Basic sanity. Portability check.



Many things. See URL above for details


Appendix A: Distribution Information


End of Document