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

integrationTest sbt task - streamline access to outputs #4

Open
matanox opened this issue Nov 14, 2015 · 1 comment
Open

integrationTest sbt task - streamline access to outputs #4

matanox opened this issue Nov 14, 2015 · 1 comment

Comments

@matanox
Copy link
Member

matanox commented Nov 14, 2015

At present time, running the the integrationTest task ends up creating files in two locations, which aren't referred to by the task's sbt output:

  1. Canve output files are written to canve-data under
/sbt-plugin-integration-test/target/scala-2.11/classes/integration-test-projects/PROJECT_NAME
  1. stdout & stderr are piped to /out at the root directory of the overall repo

This may seem a little disconcerted, especially given, that there are at present no links between the two - nor an interface for navigating all of the integration test's triggered outputs.

Suggested Changes

It would be good to link to these outputs from the summary shown in sbt for the integrationTest task. I.e. add a terminal hyperlink (file:/// pointing at the outputs, at least it will work on linux) to an html report that doesn't look ugly, the html report hosting a row per project, each row comprising:

  1. the project's name
  2. test status for/with it
  3. elapsed time run or anything I've forgotten here
  4. link to its run's standard output file (currently being produced in /out).
  5. link to its resulting canve-data directory (currently under /sbt-plugin-integration-test/target/scala-2.11/classes/integration-test-projects/PROJECT_NAME)

If you're aware of a framework for hosting and proper navigation of test results, which seamlessly affords the above without sucking, it can be implemented with/in such framework, but otherwise simple html and css would do and avoid all the boilerplate and dependencies coming with a framework.

Also out is a sucky name for an integration tests output directory in the root of the project, and should be changed to something like integration-test-log or canve-integration-test-log, it it remains written to the root of the integration test project.

@matanox matanox changed the title integrationTest sbt task access to output locations integrationTest sbt task - access to outputs Nov 14, 2015
@matanox matanox changed the title integrationTest sbt task - access to outputs integrationTest sbt task - streamline access to outputs Nov 14, 2015
@matanox
Copy link
Member Author

matanox commented Dec 14, 2015

Maybe just rename out to integration-test-out at first, providing scripted access to a project's canve-data/ with the project name as argument or such..

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

No branches or pull requests

1 participant