Following a rigorous methodology is key to delivering customer satisfaction and expanding analytics use cases across the business.
In many cases, distinct roles are used with different ActiveVOS processes. In order to ensure that testing is comprehensive, it is important that code is tested using all possible variations of the roles required. Because a user may be given different roles for specific situations, testing can miss code flaws and cause gaps in tested use cases if these role variations are not accounted for.
This document discusses best practices for testing code with roles in ActiveVOS.
Every role assigned on an ActiveVOS business process management project (BPM) project has some functionality associated with it. That functionality needs to be tested for a user operating in a number of given roles. To ensure that testing is comprehensive, tests must also be carried out when the user does not have those roles assigned, to ensure that they cannot operate beyond their authority.
Before testing can begin, gather the following information:
For each possible combination of roles create a user.
Roles:
Functionality:
|
Process1 |
Process2 |
Process3 |
Process4 |
Process5 |
RoleA |
√ |
|
|
|
|
RoleB |
|
√ |
√ |
|
|
RoleC |
|
|
|
√ |
√ |
Multiple Roles:
Set up Users:
Test each process with each user.
|
Process1 |
Process2 |
Process3 |
Process4 |
Process5 |
UserA |
Must work |
Must fail |
Must fail |
Must fail |
Must fail |
UserB |
Must fail |
Must work |
Must work |
Must fail |
Must fail |
UserC |
Must fail |
Must fail |
Must fail |
Must work |
Must work |
UserBC |
Must fail |
Must work |
Must work |
Must work |
Must work |
It is also important to consider that a workflow may contain multiple tasks and multiple submission options for each task. Permissions for these options are typically managed by role permissions in MDM/P360 It is important to test each option for each user.
Roles:
Functionality:
|
ReviewTask |
ApprovalTask |
||||
|
Assign Task |
Approve Task |
Reject Task |
Assign Task |
Approve Task |
Reject Task |
UserRole |
|
√
|
√
|
|
|
|
ManagerRole |
√
|
√ |
√ |
√
|
√
|
√
|
Specify roles when there are restrictions or authorization requirements for particular functionality. If roles and role combinations are not tested separately, issues with the code are more likely to be missed. To ensure the robustness of the code, specify each variation to be tested, document what is expected, and then test.
Success
Link Copied to Clipboard