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 the usability of test runner scripts #909

Merged

Conversation

akosthekiss
Copy link
Member

  • First of all, remove the counter-intuitive "OUT_DIR" second
    argument of run-test-suite.sh. This, way, the invocation of the
    script becomes easier to remember:
    tools/runners/run-test-suite.sh <engine> <testsuite>
    However, this also means that all output files (lists of
    executed, passed, and failed tests) are generated in the current
    working directory.
  • Align the behaviour of run-unittests.sh with the above, i.e.,
    don't try to guess where to put output files but write them in
    the CWD.
  • Adapt Makefile to the change in the use of the test runner
    scripts: create and change to "check" directories before invoking
    test runner scripts.

Extras:

  • tools/runners/run-test-suite.sh collected fail tests from
    directories twice. This does no harm but is inefficient, thus
    removing.
  • tools/runners/run-test-suite.sh was too permissive on the
    contents of test suite list files. Better to accept those lines
    only which really contain paths to JS test files.

JerryScript-DCO-1.0-Signed-off-by: Akos Kiss [email protected]

@akosthekiss akosthekiss added enhancement An improvement tools Related to the tooling scripts labels Feb 21, 2016
@zherczeg
Copy link
Member

I like simplifications, LGTM

@LaszloLango
Copy link
Contributor

LGTM

* First of all, remove the counter-intuitive "OUT_DIR" second
  argument of run-test-suite.sh. This, way, the invocation of the
  script becomes easier to remember:
  `tools/runners/run-test-suite.sh <engine> <testsuite>`
  However, this also means that all output files (lists of
  executed, passed, and failed tests) are generated in the current
  working directory.

* Align the behaviour of run-unittests.sh with the above, i.e.,
  don't try to guess where to put output files but write them in
  the CWD.

* Adapt Makefile to the change in the use of the test runner
  scripts: create and change to "check" directories before invoking
  test runner scripts.

Extras:
* tools/runners/run-test-suite.sh collected fail tests from
  directories twice. This does no harm but is inefficient, thus
  removing.
* tools/runners/run-test-suite.sh was too permissive on the
  contents of test suite list files. Better to accept those lines
  only which really contain paths to JS test files.

JerryScript-DCO-1.0-Signed-off-by: Akos Kiss [email protected]
@akosthekiss akosthekiss force-pushed the test-runner-usability branch from 1c94e8b to d857fe0 Compare February 22, 2016 11:04
@akosthekiss akosthekiss merged commit d857fe0 into jerryscript-project:master Feb 22, 2016
@akosthekiss akosthekiss deleted the test-runner-usability branch February 22, 2016 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement An improvement tools Related to the tooling scripts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants