No output when no tests found.

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: JtestR 0.3
  • Fix Version/s: JtestR 0.3.1
  • Component/s: Test running
  • Labels:
    None

Description

When no tests are found by for some reason (wrong src dir for tests specified, user has forgotten to let the class extend TestCase, etc) jtestr run is very quiet which can be confusing for new users:
test:
[jtestr] [debug] finding tests
[jtestr] [debug] loading helpers
[jtestr] [debug] loading factories
BUILD SUCCESSFUL

It would be helpful with a line that warns that no tests have been found, or at least "0 tests, 0 errors, 0 failed".

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Lars Westergren added a comment -

Here is a first attempt at fixing this, I've basically just added an array that keeps track of results. Testrun methods are now expected to return a resultset that responds to aggregate_results.

I haven't added any new tests for this yet unfortunately.

Show
Lars Westergren added a comment - Here is a first attempt at fixing this, I've basically just added an array that keeps track of results. Testrun methods are now expected to return a resultset that responds to aggregate_results. I haven't added any new tests for this yet unfortunately.
Hide
Permalink
Ola Bini added a comment -

Sorry, I will not apply this until there is some tests that document the behavior. =)

Show
Ola Bini added a comment - Sorry, I will not apply this until there is some tests that document the behavior. =)
Hide
Permalink
Ola Bini added a comment -

Also, the patch includes lots of changes due to whitespace and things like colons being replaced with 'then' statements in case-whens. Lots of noise that have nothing to do with the functionality. =/

Show
Ola Bini added a comment - Also, the patch includes lots of changes due to whitespace and things like colons being replaced with 'then' statements in case-whens. Lots of noise that have nothing to do with the functionality. =/
Hide
Permalink
Ola Bini added a comment -

This has been fixed on trunk, by implementing an aggregator object that gets sent to the generic result handler.

Show
Ola Bini added a comment - This has been fixed on trunk, by implementing an aggregator object that gets sent to the generic result handler.

People

  • Assignee:
    Ola Bini
    Reporter:
    Lars Westergren
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: