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

Use humane-test-output for better reporting #176

Closed
wants to merge 1 commit into from

Conversation

nenadalm
Copy link

@nenadalm nenadalm commented Apr 7, 2018

Hi. humane-test-output has better reporting than karma-reporter.

It was decided that humane-test-output won't be integrated into karma-reporter a while ago (honzabrecka/karma-reporter#9 (comment)). Now I am using clojurescript a bit more than before, so I thought it would be nice if my tests had better reports.

(defrecord Person [fname lname])

(deftest rec-example
  (is (= (Person. "fir" "las")
         (Person. "fir" "last"))))

Before:

LOG: 'Testing app.db-test'
LOG: ''
LOG: 'ERROR: Exception outside tests:'
LOG: 'ERROR: #object[Error Error: Assert failed: (symbol? tag)]'
LOG: ''
LOG: 'ERROR: No stacktrace available.'
LOG: 'WARNING: doo's exit function was not properly set'
LOG: '#object[TypeError TypeError: doo.runner._STAR_exit_fn_STAR_ is null]'

After:

Firefox 59.0.0 (Fedora 0.0.0) app.db-test rec-example FAILED
	
	FAIL in (rec-example) (cljs/core.js:13393:8)
	
	, , expected: #app.db-test.Person{:fname "fir":lname "las"}
	  actual: #app.db-test.Person{:fname "fir":lname "last"}
	    diff: - {:lname "las"}
	          + {:lname "last"}


@nenadalm
Copy link
Author

just cleaning up my prs (deleting those where there is no interest).

@nenadalm nenadalm deleted the humane_test_output branch June 12, 2024 16:42
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

Successfully merging this pull request may close these issues.

1 participant