This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
Exceptions within the setup/teardown files are not displayed when running a test suite. #573
Labels
Milestone
Comments
rhdunn
pushed a commit
to rhdunn/roxy
that referenced
this issue
Jul 14, 2016
rhdunn
pushed a commit
to rhdunn/roxy
that referenced
this issue
Jul 21, 2016
… they exist. There should only be a t:test element for suite-setup.xqy and suite-teardown.xqy when those files exist. This is applying feedback from @dmcassel.
dmcassel
added a commit
that referenced
this issue
Jul 21, 2016
Fix #573 Report exceptions in the setup/teardown logic to the test framework.
|
fixed in dev |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Overview
If a test suite setup/teardown file contains syntax errors, logical errors (e.g. cast errors), or other errors running that test suite displays a "NO TESTS RUN" message.
Use Case
As a developer, I want to see any exceptions in setup/teardown code within the test runner UI so I can easily identify and fix problems in the setup/teardown code (e.g. like exceptions that occur when the test files contain syntax or logical errors).
System
Roxy Version: 1.6
Operating System: Windows
Web Browser: Firefox
The text was updated successfully, but these errors were encountered: