[MGNLCE-126] Consolidate integration test settings in a Java class Created: 12/Jan/18 Updated: 23/Feb/18 Resolved: 23/Feb/18 |
|
| Status: | Closed |
| Project: | Community Edition |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.5.10, 5.6.2 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Epic Link: | Improve QA setup |
| Story Points: | 5 |
| Description |
|
Most of the integration test properties we use are scattered across the abstract classes, maven configs, property files and etc. By opting for the more complex integration test env, we are also adding additional config options. In order to not make situation worse, but rather improve it - looks like we need a class that would book-keep the configurable settings and make them available in a unified form in all our test utilities. |