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

Add MINITEST_REPORTER env variable to override ENV detection #256

Merged
merged 8 commits into from Mar 21, 2018
Merged

Add MINITEST_REPORTER env variable to override ENV detection #256

merged 8 commits into from Mar 21, 2018

Conversation

brettwgreen
Copy link
Contributor

  • RubyMate, RubyMine, and TeamCity ENV detection overrides any specific reporter passed to use! method.
  • Add a MINITEST_REPORTER env detection so users can override this detection and force usage of a specific reporter.
  • Specific use case was attempting to use XML/JUnit style reports on TeamCity because of limitations of built-in Rake Runner step.
    • Rake Runner Build Step in TeamCity does a very poor job of choosing ruby versions automatically. Using a command-line runner for tests allows rvm to work as intended, and JUnit Reporter test output can be captured by TeamCity's XML Report Processing Build Feature.

@os97673 os97673 merged commit 41f7129 into minitest-reporters:master Mar 21, 2018
@os97673
Copy link
Collaborator

os97673 commented Mar 21, 2018

published as 1.3.0.beta1 to get feedback. Feel free to ping me to release 1.3.0 in a week (or two ;)

@brettwgreen
Copy link
Contributor Author

Cool... I will pull into a few projects on my TeamCity setup and convert them over to try it out.

Thanks!

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.

None yet

2 participants