Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improve SoarUnit failure output #103

Open
garfieldnate opened this issue Apr 17, 2015 · 1 comment
Open

improve SoarUnit failure output #103

garfieldnate opened this issue Apr 17, 2015 · 1 comment

Comments

@garfieldnate
Copy link

SoarUnit outputs something like this for a failed test:

FAILED: test xyz returns nil with total 0, never called (pass) function. Ran 101 decisions. (0.378 s)

The main thing missing is the line number that the test occurs on. I'm trying to write a text editor plugin for running SoarUnit, and having the line number would allow the user to click and go straight to the problem test.

Also, I don't understand what "returns nil with total 0" means in this context. This output is not documented as far as I can see.

@marinier
Copy link
Contributor

Agreed, the text output needs work. I suspect it's gone unnoticed for so
long because I'm the primary soarunit user, and I always use the GUI.

As it is, you can probably use the test name to find the test (although
note that there's nothing that prevents multiple tests from having the same
name).

On Fri, Apr 17, 2015 at 3:11 AM, Nathan Glenn [email protected]
wrote:

SoarUnit outputs something like this for a failed test:

FAILED: test xyz returns nil with total 0, never called (pass) function. Ran 101 decisions. (0.378 s)

The main thing missing is the line number that the test occurs on. I'm
trying to write a text editor plugin for running SoarUnit, and having the
line number would allow the user to click and go straight to the problem
test.

Also, I don't understand what "returns nil with total 0" means in this
context. This output is not documented as far as I can see.


Reply to this email directly or view it on GitHub
#103.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants