No matter how much testing is performed, if the test coverage is not adequate the system may contain unrevealed defects or insufficiencies. 

Thus the buyers of a system must have input into the acceptance test design and content. This should happen at two points:

1. The initial requirements and specifications.
2. The review of the test plan.

The acceptance test must demonstrate that the system will perform adequately in the way that the system is intended to be used . Final tests must be done with the system configured for live use, using real-world data and realistic test scenarios.

There are many types of tests such as stress and load tests, performance tests, failure tests, and functional tests. 

There are several categories of testing such as unit testing (test of various components individually), integration testing (test that components work together properly) and systems testing (testing how the system functions as a whole).

When and where do you do how much of each?

How much testing is too much? Or too little?

The buyers and users of the system will want to focus on how they plan to use the system on a daily basis. This is good, but it's usually not enough.

Someone expert in the types of tests required must see that the test plan contains:

- a valid test approach
- appropriate test cases
- reliable test procedures
- correct test system configuration
- proper test environment
- clear description of expected test outcomes
- valid test pass/fail criteria
- tests appropriate for the technologies employed
- proper testing of packaged software components

The small investment of time that will be involved in reviewing (and if necessary, revising) the test plan will make a big contribution towards a successful system turnover.

To find out more about how RBCS can help you with security systems acceptance testing, call us today at 949-831-6788!