Before addressing the bug identified in spike SWATCH-3887 (use status to terminate contract from IT partner gateway UMB contract message), we need a test for the UMB message terminating the contract.

Currently our only coverage around this is ‘test_verify_add_remove_contract’ which adds a contract via internal api, verifies capacity increase, removes contract using internal api, verifies capacity decrease. This does not validate the db change directly. 

Acceptance Criteria:

• Documented test plan with scenarios, expected results, and edge cases.
• What test coverage is in iqe component test currently and see any gaps for time being. 
• If we need to write a test to cover SWATCH-3887 then we should write it in iqe component test for the moment.
• Automated test cases covering functional, negative, and regression scenarios.