L3 - Default Context:
In the integration test code of the back-end we have a lot of code duplication, which is helper functions that allow us to interact with the Optimize rest-api. We should create dedicated client classes that help us to interact with the rest api, e.g. like how it's done with the AuthorizationTestHelper or the CollectionTestHelper.
AT:
- there is a utility client class for each Optimize endpoint
- the client classes are used in all integration tests
- the client classes are initialized in the AbstractIT, so we don't have to intialize them in every test class
- abstract classes that are just for the porpose of sharing those utility methods are being removed (e.g. possibly the AbstractAlertIT)
This is the controller panel for Smart Panels app
1.
|
Refactor Alert, Analysis and Collection Authorization ITs to use client classes |
|
Done | Unassigned |
2.
|
Refactor Export ITs to use client classes |
|
Done | Unassigned |
3.
|
Refactor collection related ITs to use client classes |
|
Done | Unassigned |
4.
|
Refactor Definitions ITs to use client classes |
|
Done | Unassigned |
5.
|
Refactor Report ITs to use client classes |
|
Done | Unassigned |
6.
|
Refactor Dashboard ITs to use client classes |
|
Done | Unassigned |
7.
|
Refactor Variable ITs to use client classes |
|
Done | Unassigned |
8.
|
Refactor Identity ITs to use client classes |
|
Done | Unassigned |
9.
|
Refactor Entities, FlowNodeNames, Localization, Sharing and Status ITs to use client classes |
|
Done | Unassigned |