# Test handleChange / handleAdd / etc code

Although there is no way to enforce testing of any coding in any of the methods

    			HandleRegisteredChange
    			     (BusinessEntity changedBusinessEntity,
    			      RegisteredChangeDetail changeDetail)

    			handleAdd(BusinessEntity newBusinessEntity)

    			handleChange(BusinessEntity changedEntity, DataTransferObject oldDTO)

It is still imperative that this code should also be exercised AND verified when testing the change handler. Please ensure that every path through these methods is exercised and the results verified.

In general, there is a specific set of classes or functionality that is required to have explicitly defined tests.

- Every entity (and entity extension) class must have each of its validation rules explicitly tested. That is, each rule should fail once, with an explicit acknowledgement of the failed rule expected.
- Every service must have a test.
  - Searches must test each search type once.
    - "Page" services must test their complete cycle that are available.
    - Queries must test read
    - Maintenance classes must test add/change/read/delete
- Every maintenance extension must have a test class
- Every algorithm implementation must have a test

Note: Currently, the above must have tests may still not completely cover all the cases. For example, one search type may have several inputs, which trigger different code or queries to be executed. The testing FW as is cannot know this, so only requires a single test case for that search type. However, to achieve complete code coverage, it is strongly recommended that each possible specialized case be modeled with a test case.
Note: In addition, there is a desire to assure that each business component or business entity method has been tested. Currently these tests are not required. However, after a complete build server run, any business component methods or business entity methods that have not been explicitly tested will be reported.
Parent topic: Standard test cases