| Summary: | Uncaught JS Console errors | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Martin Renvoize (ashimema) <martin.renvoize> |
| Component: | Test Suite | Assignee: | Chris Cormack <chris> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | dcook, jonathan.druart |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21813 | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Attachments: | Bug 22077: Make sure there were not JS errors on running selenium tests | ||
|
Description
Martin Renvoize (ashimema)
2019-01-07 17:58:42 UTC
(In reply to Martin Renvoize from comment #0) > I'd love to see some sort of regression test to catch such errors in the > future.. but I'm not sure how to proceed and didn't want to prevent that bug > from progressing.. hence the new report here. Do you mean an automated test? I'd be intrigued by that. Created attachment 86700 [details] [review] Bug 22077: Make sure there were not JS errors on running selenium tests We could move that code to t::lib::Selenium and add the subtest to all our selenium/*.t files |