4.3 Lab Testing and Validation

One of the key parts of the design phase is the testing and validation that is done in the organization’s lab environment prior to any deployment being completed. This is your opportunity to do the following:

The organization should use the lab to develop acceptance tests that are run by the project team and tracked for completion and success. The best way to do this is to document individual acceptance tests (a simple spreadsheet can be used if you want), and complete the tests according to the steps you need to take. After the individual tests have been run successfully and validated (proven successful), you can document this and move on until all tests have been completed.

If individual tests are unsuccessful, you need to make changes (this could also include your design), and run the test until it is successfully completed.

The idea is not to create more work for you, but to prove the overall design quality and increase the probability of a successful ZENworks Configuration Management deployment.

Your lab environment must reflect your existing infrastructure as closely as possible, and the ZENworks Configuration Management infrastructure in the lab must accurately reflect the design you are creating.

The lab should contain real-world layout (design) to ensure that the ZENworks Configuration Management design fits well within the existing environment. Things to include are:

When building your lab, you do not need to build the entire lab with physical hardware. You are not testing the breaking point here. You are testing functionality and whether or not there are any major issues found with the overall design. You should use actual production hardware to test functionality at the device level, but the server infrastructure could be virtualized to save hardware costs. The idea is to reflect the design so you can prove that it is solid.