aca1e85da4
mavsdk_tests: don't forget to check for rootfs dir
4 years ago
4184c204c4
autopilot_tester: don't poll mission progress
...
Instead use subscription here as well in order not to miss an update.
4 years ago
2971ce8664
mavsdk_tests: don't clear logs
4 years ago
176d932f23
mavsdk_tests: prevent missing updates
...
It seems like we are often missing updates from topics like flight mode
or in air state, both topics that are sent out infrequenctly e.g. at 1
Hz. Therefore, instead of polling for that data we should probably
subscribe to the updates and that way get notified of each an every
update.
For instance this should prevent the case where we miss the mode change
from mission to descend and back to mission once landed and disarmed.
4 years ago
2772022785
mavsdk_tests: disable mag stuck test
...
The estimator sometimes diverges in vz after landing which makes the
test fail. This needs to be dealt with first before we can enable the
test again.
4 years ago
e592bed7d3
mavsdk_tests: use timestamp from attitude field
...
The flight_information field was not updated often enough which lead
to timeouts.
4 years ago
397fa84cd0
mavsdk_tests: add time in front of debug lines
4 years ago
14cb98a6b4
Increase corridor check thresholds for mission tests
4 years ago
fda63f802e
Tone alarm: Adjust log levels
...
The earlier log levels represented normal operation scenarios as errors, this aligns the log levels.
4 years ago
3cc53f551d
MAVSDK tests: Use full system timeout off
...
Depending on loop iterations for timeouts is not accurate, as usleep behavior depends on the system load and asking for a 0 ms sleep can potentially return immediately.
4 years ago
565da15f2f
MAVSDK test: Increase timeout
4 years ago
fb1f360724
mavsdk_tests: consistent 180s disarm timeout
4 years ago
f5660c6b0c
mavsdk_tests: adjust px4 and gzserver priority relative to mavsdk_test
...
- this is to avoid starving the test runner
4 years ago
a8f665739d
mavsdk_tests: manual fly forward for slightly longer
4 years ago
756609c3e8
mavsdk_tests: relax corridor radius default for missions
4 years ago
d4d02f449f
Improve tailsitter tuning master ( #16078 )
...
* tailsitter SITL: improve hover tuning
Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
* Add SITL testing for tailsitter VTOLs
This enables SITL testing for Tailsitter vehicles
Co-authored-by: Jaeyoung-Lim <jaeyoung@auterion.com>
4 years ago
cf082d7f1c
Github actions: SITL tests upgrade MAVSDK v0.30.1 -> v0.33.1
4 years ago
76602b3a8f
mavsdk_tests: longer climb (5 -> 10 seconds) in fly forward altctl/posctl tests
4 years ago
9d3e159e65
Make mavsdk test runner handle generated sdf files ( #15797 )
...
Update sitl_gazebo
Fix indent errors
Fix syntax error
Fix indentation errors
Fix syntax errors
use autopep8
4 years ago
44b4a6eb74
mavsdk_tests: increase time for manual tests
4 years ago
e7651c94f6
mavsdk_tests: use custom rootfs, reset it
...
Instead of messing with existing params, use a separate rootfs for
tests, as suggested by @bkueng .
4 years ago
012763e5f1
mavsdk_tests: fly forward a bit longer
...
Hopefully, that's long enough for slow VTOLs.
4 years ago
58b4135ab0
mavsdk_tests: wait even longer
...
Again, hopefully that's enough.
4 years ago
a299e2c57d
mavsdk_tests: fly forward even longer
...
Hopefully that's enough.
4 years ago
4c00c1f561
mavsdk_tests: add missing switch to POSCTL
4 years ago
bbef07bc80
mavsdk_tests: init RC with throttle centered
4 years ago
c26b769cc0
mavsdk_tests: add missing type annotation
4 years ago
d2cb27e0de
mavsdk_tests: try with faster RC rate
4 years ago
f8f03835ad
mavsdk_tests: increase timeouts yet again
...
This is after using PX4 time to check for timeouts.
4 years ago
3135b94980
mavsdk_tests: use PX4 time for timeouts
...
This way we are less dependent on CPU load of the host.
4 years ago
ca0f26a003
mavsdk_tests: added posctl/altctl test
4 years ago
0a7dcf26d5
mavsdk_tests: clean up includes
4 years ago
630a6f3810
mavsdk_tests: clear params between test cases
4 years ago
a5a577a6c4
mavsdk_tests: use speed factor, increase timeouts
...
We had not actually properly adjusted the timeout to the lockstep speed
factor. Once we did that, we had to increase the timeouts quite a bit to
have the tests pass.
4 years ago
4eb1ea10f0
mavsdk_tests: don't block inside of callback
...
This is required with MAVSDK v0.29.0 and later!
4 years ago
8d3f1e63f0
mavsdk_tests: use all os env vars by default
4 years ago
55d2bdc438
mavsdk_tests: adapt to changed inject API
...
We now need to say which instance, for now it's all instances.
4 years ago
ed357cf356
mavsdk_tests: move math things to separate header
4 years ago
1eaceb17dc
mavsdk_tests: adjust timeouts by lockstep speed up
4 years ago
20621e6744
mavsdk_tests: add tests for GPS as height source
4 years ago
c31246e13a
mavsdk_tests: add test for stuck mag
4 years ago
afcfa2fbe0
mavsdk_tests: check for stuck baro
4 years ago
a05ad9c64c
mavsdk_tests: add wildcards for case filtering
4 years ago
c4efcbf895
mavsdk_tests: check for baro failure in mission
4 years ago
8d6ebf15b6
mavsdk_tests: test for losing mag during mission
4 years ago
ef7e4531f9
mavsdk_tests: enable GPS lost test for VTOL
...
This is in multicopter mode only for now though.
4 years ago
3c499fc3a2
mavsdk_tests: add first GPS lost failsafe test
4 years ago
055fa768d8
posix: enable ROMFSROOT
...
This will copy the ROMFS into the build directory under etc/, and thus
needs a change of the PX4 startup parameters and mixer paths.
5 years ago
435c2fe438
Fix rarely flakey test on Github Actions
5 years ago
5f2abb66a4
mavsdk_tests: add workaround to prevent failsafe
...
This workaround should fix the test failure where we disarm before
taking off because we accidentally switched to failsafe mode right
before taking off because we were still in Manual mode and not Hold yet.
5 years ago
Julian Oes
Julian Kent
Lorenz Meier
Daniel Agar
Silvan Fuhrer
JaeyoungLim
Beat Küng