c4d54d983b
mavsdk_tests: bump MAVSDK version to 0.40.0
4 years ago
4f52c0b6da
mavsdk_tests: unused var and index fix
4 years ago
f16913c175
mavsdk_tests: fix timeout at 1x speed
4 years ago
e7fcfbf658
mavsdk_tests: use global position instead of local
...
We are currently not testing with flow only anyway, so we might as well
remove this for now.
4 years ago
43fccece61
mavsdk_tests: check installed version
...
Starting with MAVSDK 0.39.0 we can specify the version required. This
way we can fail at configure time instead of later during compilation or
linking.
4 years ago
7384bd2675
mavsdk_tests: specify required MAVSDK version
...
This way it can be better picked up by CI scripts.
4 years ago
bb0fe9ee61
mavsdk_tests: losen time limit for VTOL mission
4 years ago
2eaf677de3
mavsdk_tests: correctly locate plan
4 years ago
cd66a79747
mavsdk_tests: move waypoints to vehicle position
...
This way it shouldn't matter where the test is run.
4 years ago
d714c2faec
mavsdk_tests: add VTOL mission tests
...
This adds VTOL mission tests to the CI integration tests.
This depends on MAVSDK v0.38.0.
4 years ago
1e88939605
mavsdk_tests: report speed factor every second
...
This helps in debugging slow CI.
4 years ago
82200fab9e
mavsdk_tests: relax MC "Fly straight" speed threshold
4 years ago
46e75ebddb
mavsdk_tests: remove leftover debug line
4 years ago
2703a34900
mavsdk_tests: add link back to github action
4 years ago
64d0ce43b6
mavsdk_tests: upload to logs.px4.io in test_runner
...
By doing the upload directly inside the mavsdk_test_runner.py we have
more context such as the model, case, etc.
4 years ago
2315618b85
mavsdk_tests: use autopilot timestamps to sleep
...
This way we should be able to avoid some of the timeouts happening on
the PX4 side if MAVSDK doesn't send setpoints in time.
4 years ago
6c26387e85
mavsdk_tests: try to prevent auto-disarm
...
We should not spend too much time sending RC init messages because if it
takes too long, we might auto-disarm in the meantime.
4 years ago
c1de27acf7
mavsdk_tests: use more conservative speed_factor
4 years ago
0ebb8c6981
mavsdk_tests: use microseconds to avoid sleep(0)
4 years ago
b6b9ce5f11
mavsdk_tests: robustify test by climbing longer
4 years ago
b79553862e
mavsdk_tests: remove timeout for mission upload
...
Just use what is MAVSDK internal.
4 years ago
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
TSC21
Julian Oes
Daniel Agar
Julian Kent
Lorenz Meier
Silvan Fuhrer
JaeyoungLim