[MGNLCE-67] Add an UI test checking that there are no Definitions app problems Created: 19/Dec/16 Updated: 02/Jan/17 Resolved: 28/Dec/16 |
|
| Status: | Closed |
| Project: | Community Edition |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.5.1 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Maxime Michel |
| 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: | Definitions app problems |
| Sprint: | Basel 75 |
| Story Points: | 2 |
| Description |
|
While we clear up current problems with BL-381, it would make sense to also to make sure we don't end up in a similar situation years down the line. Once the epic is done, any new addition to the codebase, or any deprecation of class or function, should result in a clear Problems subapp state. An UI test should therefore be written, assessing that there are no problems, so that builds fail otherwise. |