Repman

The page covers the acceptance tests for the repman utility. See the [Downloads] page for the utility itself.

Use Case	User adds a process to the replication manager to launch and manage
Functionality	Baseline
Test Distribution	None
Known Problems	None
Test Sequence	Have repman in the local directory or in your path Start a managed process by passing in the process and label on the command line Run repman with no flags Should print out the process label and machine that you created
Configuration/Deployment Issues	User must have read/write access to the /tmp directory In order for the replication manager to tracks its managed processes, it stores all of its managed processes in /tmp/polaris.proclist. If this file is modified outside of repman, or moved, repman will no longer know its managed processes.

Use Case	User kills a process that has been managed by repman
Functionality	Baseline
Test Distribution	None
Known Problems	None
Test Sequence	Follow the steps in test 1 Run repman with the k flag and the label of the process just created Should print out its managed process list without the process just killed
Configuration/Deployment Issues	User must have read/write access to the /tmp directory In order for the replication manager to tracks its managed processes, it stores all of its managed processes in /tmp/polaris.proclist. If this file is modified outside of repman, or moved, repman will no longer know its managed processes.

Use Case	The replication manager displays a list of the processes that it is managing.
Functionality	Baseline
Test Distribution	None
Known Problems	None
Test Sequence	Run the test sequence in test number 1 several times, modifying the label each time. Run repman with no flags Should print out a list of all managed processes
Configuration/Deployment Issues	User must have read/write access to the /tmp directory In order for the replication manager to tracks its managed processes, it stores all of its managed processes in /tmp/polaris.proclist. If this file is modified outside of repman, or moved, repman will no longer know its managed processes.

Use Case	The replication manager should detect when a process it is managing goes down external to repman.
Functionality	Baseline
Test Distribution	None
Known Problems	None
Test Sequence	Run the test sequence in test number 1 several times Run repman with no flags Should print out a list of all managed processes Externally kill on of its managed processes Run repman with no flags The list printed out should not show the killed process
Configuration/Deployment Issues	User must have read/write access to the /tmp directory In order for the replication manager to tracks its managed processes, it stores all of its managed processes in /tmp/polaris.proclist. If this file is modified outside of repman, or moved, repman will no longer know its managed processes.

Use Case	The replication manager should not manage a process that is never started.
Functionality	Baseline
Test Distribution	None
Known Problems	None
Test Sequence	Run repman with the process and label flags. However, for the process flag, use a command which does not exist. Repman should print out an error.
Configuration/Deployment Issues	User must have read/write access to the /tmp directory In order for the replication manager to tracks its managed processes, it stores all of its managed processes in /tmp/polaris.proclist. If this file is modified outside of repman, or moved, repman will no longer know its managed processes.

Use Case	The replication manager does not allow creation of duplicate labels.
Functionality	Baseline
Test Distribution	None
Known Problems	None
Test Sequence	Run the test script in test number 1 Run it again, with the identical flags An error message should appear stating that the label has already been used.
Configuration/Deployment Issues	User must have read/write access to the /tmp directory In order for the replication manager to tracks its managed processes, it stores all of its managed processes in /tmp/polaris.proclist. If this file is modified outside of repman, or moved, repman will no longer know its managed processes.

Use Case	The replication manager should detect invalid flags.
Functionality	Baseline
Test Distribution	None
Known Problems	None
Test Sequence	Have repman in the local directory or in your path Run repman with invalid or incompatible flags Should print out a usage message
Configuration/Deployment Issues	User must have read/write access to the /tmp directory In order for the replication manager to tracks its managed processes, it stores all of its managed processes in /tmp/polaris.proclist. If this file is modified outside of repman, or moved, repman will no longer know its managed processes.