54fe3c5fd5
mavsdk_tests: remove waitforgz helper, add sleep
...
This is an attempt to workaround the gz spawn timeout in CI.
Let's just hard-code a sleep before spawning the model.
5 years ago
28f4dc10ae
mavsdk_tests: make sure all log output is printed
...
This fixes the issue where the last lines of the log output was not
printed in case of error or on the verbose setting. This meant that
essentially the actual test error was not printed.
The fix involves two parts:
1. Firstly collect the output again even if a process has exited.
2. Collect all lines at once and not one line per iteration.
5 years ago
0edc2aa334
mavsdk_tests: don't stall on timeout
5 years ago
29c102b205
mavsdk_tests: wait for gz to run for model spawn
5 years ago
b1d3b95ebf
Add gzmdoelspawning to mavsdk tests
5 years ago
6d654cb50b
mavsdk_tests: improve usage text
...
These are improvements based on the review by @hamishwillee
in https://github.com/PX4/Devguide/pull/982 .
5 years ago
89599f345f
mavsdk_tests: c++ test_runner is now mavsdk_tests
5 years ago
4905ac5e2c
mavsdk_tests: add filter for cases
5 years ago
79387428c6
mavsdk_tests: fix missing space after number
5 years ago
3f1990b083
mavsdk_tests: print where to find logfiles
5 years ago
188177cef6
mavsdk_tests: print error on failure
5 years ago
ab2186f126
mavsdk_tests: improve and fix colors/result
5 years ago
b1ceef5b93
mavsdk_tests: add combined log
5 years ago
814d79cb32
mavsdk_tests: improve log file folder structure
5 years ago
8283d19682
mavsdk_tests: print overall results
5 years ago
a208129921
mavsdk_tests: satisfy mypy type checks
5 years ago
12252c97c5
mavsdk_tests: further argument cleanup, some types
5 years ago
ff64d87ae6
mavsdk_tests: import naming, easier coloring
5 years ago
11a28840f3
mavsdk_tests: split up Python script
...
Otherwise, the script will get a tangled mess.
5 years ago
b281d87b4a
mavsdk_tests: initialize Tester class in ctor
5 years ago
e2c80e546d
mavsdk_tests: properly exit on Ctrl+C
...
With threads we need to manually take care of it, otherwise it gets
messy and we need to press Ctrl+C multiple times.
5 years ago
2c2e314ffe
mavsdk_tests: improve output, allow log and stdout
...
This makes it possible to write to logfiles and at the same time print
everything to console in verbose mode.
5 years ago
b2e300ad1f
mavsdk_tests: improve test output readability
5 years ago
54645268ed
mavsdk_tests: only print error on failure
5 years ago
911cdc8774
mavsdk_tests: output less verbose unless needed
5 years ago
bfef243dba
mavsdk_tests: write output to logs folder
...
And create folder if it doesn't exist already.
5 years ago
70eb444f17
mavsdk_tests: improve naming of argument
...
We abort when we already failed so this makes more sense.
5 years ago
41b2362dcf
mavsdk_tests: add more config into JSON
5 years ago
b4916fdecb
mavsdk_tests: move config into json file
5 years ago
44a556717d
mavsdk_tests: remove plane tests
...
We can put them back once it's supported.
5 years ago
ae2032d29f
mavsdk_tests: use the min of the speed factors
...
Facepalm.
5 years ago
86f24f5121
mavsdk_tests: remove opt_flow test
...
It doesn't actually seem to work.
5 years ago
b7e8837562
mavsdk_tests: add max speed factor
...
This is required because some tests don't work at more than 1x.
5 years ago
d8b6c864cd
mavsdk_tests: PEP8 fixes
5 years ago
5bf2648c1f
Add debugger options for mavsdk test runner
5 years ago
eb50e89d87
Add flow tests to MAVSDK tests ( #14039 )
...
* workflows: remove unneeded pip dep and comments
* mavsdk_tests: simple test using flow/offboard
This adds a first proof of concept of a test using flow and offboard.
* Flow MAVSDK test: check against ground truth
* CleanUp
* workflows: use latest docker image with psutil
* mavsdk_tests: fix PEP8 issues
* Add VTOL CI tests back
* switch to non-rendering flow mockup
* workflows: install mavsdk from GitHub release .deb
* Add vision test and disable VTOL temporarlly
* Fist draft of combining test coverage and test in one workflow
* Add VTOL mavsdk tests back in CI
Co-authored-by: Julian Oes <julian@oes.ch>
Co-authored-by: kritz <kritz@ethz.ch>
5 years ago
a2e95f171f
mavsdk_tests: fix model name of plane
...
However, the test does not pass yet, so I'm leaving it commented out.
5 years ago
bb1c08fdd1
mavsdk_tests: enable VTOL, fix TEST_CASE name
...
We can't use commas in the TEST_CASE name. With the comma, the test did
not run and displayed:
Filters: Takeoff, transition and RTL
No test cases matched 'Takeoff'
No test cases matched 'transition and RTL'
==========================================
No tests ran
5 years ago
01f29a51a8
mavsdk_tests: DISPLAY env for gazebo, --verbose
5 years ago
de8fadf1f5
Test runner: Terminate all px4 apps correctly
...
Without this change an aborted run leaves zombie processes running.
5 years ago
f64a0982c7
mavsdk_tests: fix build instructions
5 years ago
0f77e3ba44
mavsdk_tests: actually use chosen model
...
This does not work for plane yet, and VTOL only acts as multicopter for
now, so doesn't make much sense just yet.
5 years ago
5589812104
mavsdk_tests: refactor/cleanup
...
This splits the main function which has become way too long.
5 years ago
3387c9599c
mavsdk_tests: don't constrain speed factor to int
...
Speed factors slower than 1 should also be possible.
5 years ago
9e239e47c4
mavsdk_tests: fix PEP8 issues
5 years ago
b0cb29ed82
MAVSDK tests: Add minimal plane example
...
This will add coverage for baseline plane controllers.
5 years ago
1edfee4fdd
mavsdk_tests: build should be independant of px4
5 years ago
7775dfbc56
mavsdk_test_runner.py remove verbose gazebo output
5 years ago
26d01b876c
GH Actions: Enable grind option
...
This allows to run the script in grind mode to find CI failures that are triggered through e.g. race conditions.
5 years ago
73edc21667
Tests: Add further instrumentation
5 years ago
Julian Oes
JaeyoungLim
Julian Kent
Lorenz Meier
Daniel Agar