You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
I want to be able to run some basic tests in travis to avoid regressions during code merges
Impact
The desired behavior will allow me to be more confident about code changes and will encourage more testing around the code
Feature Suggestion
We can achieve the desired behavior by adding a line in the travis build that will run tests. Any tests that cannot be run in an automated manner (require API keys or HTTP access) can be set to a mode that will not run in the Travis build.
Desired Behavior
I want to be able to run some basic tests in travis to avoid regressions during code merges
Impact
The desired behavior will allow me to be more confident about code changes and will encourage more testing around the code
Feature Suggestion
We can achieve the desired behavior by adding a line in the travis build that will run tests. Any tests that cannot be run in an automated manner (require API keys or HTTP access) can be set to a mode that will not run in the Travis build.
Additional context
related to #51
The text was updated successfully, but these errors were encountered: