Major Description
Currently we have two IMRU functional tests. Both are done through IMRUClient. As IMRU Client uses IMRUDriver in the configure, it is inconvenient to test failed scenarios.
A way to do it is to write IMRU tests that gets driver configuration in test instead of in IMRUClient. This would give us a flexibility to set different handlers in driver configuration so that we can simulate some scenarios in testing.
Other configurations for IMRU can be shared in those tests so that we won't miss any configurations for the driver and group communications.
This would allow to write test for IMRU task close event.