21) Outstanding items regarding LRM/CRM integration
The current manual LRM testing setup is neither comprehensive nor adequate.
A suite of regression tests that verifies all facets of LRM functionality is required before it will be enabled in the CRM. Debugging the CRM alone is complex enough without trying to debug the LRM at the same time. The tests should be able to be run by others based on what is in CVS.
Off the top of my head, below are some parts of the LRM that need to be tested for each resource class and with both good and bad data/inputs where appropriate:
metadata operations (including faking metadata, the "description" field IIRC, in the case LSB RAs)
event generation (maybe just start with a fake heartbeat RA that it rigged to fail after X seconds)
monitoring (is this different from monitoring?)
doing things at the wrong time (stop a resource when its not started for example)
doing bad things (try to add duplicate resources, perform an action that isnt supported)