[MGNLCE-134] Fix and enable the crawler in the UI tests pipeline Created: 09/Mar/18 Updated: 08/May/18 Resolved: 08/May/18 |
|
| Status: | Closed |
| Project: | Community Edition |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Epic Link: | Pipelines continued |
| Description |
|
A crawler is used in an integration test to retrieve a few URLs from the site. The crawler looks into Tomcat logs for any errors that may have occurred during accessing the website. Problem is that in pipeline context it's not easy to point the crawler to a valid URL. The crawler wasn't included in the pipeline MVP because there was simply no time to get it back to work. Some leads are available in the UI tests pipeline template, though. |
| Comments |
| Comment by Antti Hietala [ 08/May/18 ] |
|
Decided not to try to fix the existing crawler. Rewriting the crawler from scratch can be considered in the future. Closing as Won't Do. |