-
Notifications
You must be signed in to change notification settings - Fork 17k
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
Run simple autotests for each vehicle in CI #9592
Comments
On Fri, 19 Oct 2018, Patrick José Pereira wrote:
I think that it's possible to run small and fast autotests for each vehicle, this would help to identify if a PR breaks a vehicle functionality.
We should aim to use travis or another third party CI system just to test it (like appveyor).
Right now the full autotest setup takes 2h-ish to finish everything for all vehicles, that idea is to run just simple tests that can check the most basic
functionalities of each vehicle.
Something I've wanted to do for a while is to name the tests we pass into
"run_test". That would allow us to run individual tests by name. This
has the prerequisite that each test is self-contained, however - assuming
a precondition of being on the ground, disarmed.
|
... we have named tests now |
I think this can be closed? did we want to run more tests than this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think that it's possible to run small and fast autotests for each vehicle, this would help to identify if a PR breaks a vehicle functionality.
We should aim to use travis or another third party CI system just to test it (like appveyor).
Right now the full autotest setup takes 2h-ish to finish everything for all vehicles, that idea is to run just simple tests that can check the most basic functionalities of each vehicle.
The text was updated successfully, but these errors were encountered: