6d654cb50b
mavsdk_tests: improve usage text
...
These are improvements based on the review by @hamishwillee
in https://github.com/PX4/Devguide/pull/982 .
2020-03-19 08:53:21 +01:00
d0349fcf07
mc_pos_control: allow zero thrust during takeoff and landing
...
Otherwise the takeoff ramp doesn't start with zero thrust and
the land thrust cut cannot cut to zero.
2020-03-18 20:36:05 +01:00
5027c68c0a
mc_pos_control: handle takeoff and landing thrust limit the same way
...
The landing thrust limit was after the position controller and
could be inconsistent with what the takeoff limit did. This
resulted in different thrust values sequentially getting applied
during landing.
2020-03-18 20:36:05 +01:00
3049a3d14d
mc_pos_control: prevent takeoff with thrust setpoint
...
This was only necessary for stabilized mode before #10805 .
The unit length thrust setpoint will anyways not be available
anymore soon because it gets replaced with the acceleration
setpoint in m/s².
2020-03-18 20:36:05 +01:00
1f98ebdb47
mc_pos_control: switch order of setpoint amendment
...
to make sure the takeoff limitation is always done last.
2020-03-18 20:36:05 +01:00
a8063ac948
HTE: enable by default
2020-03-18 19:47:30 +01:00
89599f345f
mavsdk_tests: c++ test_runner is now mavsdk_tests
2020-03-18 17:57:41 +00:00
ade39481ad
mavsdk_tests: only env vars that are set
...
Otherwise this raises a KeyError.
2020-03-18 17:57:41 +00:00
5ea40c57c6
workflows: add more tests outside of Europe
2020-03-18 17:57:41 +00:00
759e3d6a04
mavsdk_tests: pass PX4_HOME_ env variables on
...
This way tests can be run at different locations.
2020-03-18 17:57:41 +00:00
4a91d791b1
mavsdk_tests: remove commented out code
2020-03-18 17:57:41 +00:00
9d124c2b1a
mavsdk_tests: a timeout of 5min should be enough
2020-03-18 17:57:41 +00:00
23a3002178
github: try to get latest tools using pip
2020-03-18 17:57:41 +00:00
6dfe0c3d72
github: new check for MAVSDK tester Python scripts
2020-03-18 17:57:41 +00:00
eb1141bbea
mavsdk_tests: remove unused import
2020-03-18 17:57:41 +00:00
c6160d4e3f
mavsdk_tests: fix error for Python < 3.8
2020-03-18 17:57:41 +00:00
41341cd985
mavsdk_tests: name files consistently
2020-03-18 17:57:41 +00:00
b5048a3414
mavsdk_tests: add header and fix style
2020-03-18 17:57:41 +00:00
9b61ce1006
Tools: check style of mavsdk_tests files
2020-03-18 17:57:41 +00:00
4905ac5e2c
mavsdk_tests: add filter for cases
2020-03-18 17:57:41 +00:00
79387428c6
mavsdk_tests: fix missing space after number
2020-03-18 17:57:41 +00:00
3f1990b083
mavsdk_tests: print where to find logfiles
2020-03-18 17:57:41 +00:00
188177cef6
mavsdk_tests: print error on failure
2020-03-18 17:57:41 +00:00
ab2186f126
mavsdk_tests: improve and fix colors/result
2020-03-18 17:57:41 +00:00
b1ceef5b93
mavsdk_tests: add combined log
2020-03-18 17:57:41 +00:00
814d79cb32
mavsdk_tests: improve log file folder structure
2020-03-18 17:57:41 +00:00
8283d19682
mavsdk_tests: print overall results
2020-03-18 17:57:41 +00:00
a208129921
mavsdk_tests: satisfy mypy type checks
2020-03-18 17:57:41 +00:00
12252c97c5
mavsdk_tests: further argument cleanup, some types
2020-03-18 17:57:41 +00:00
ff64d87ae6
mavsdk_tests: import naming, easier coloring
2020-03-18 17:57:41 +00:00
11a28840f3
mavsdk_tests: split up Python script
...
Otherwise, the script will get a tangled mess.
2020-03-18 17:57:41 +00:00
b281d87b4a
mavsdk_tests: initialize Tester class in ctor
2020-03-18 17:57:41 +00:00
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.
2020-03-18 17:57:41 +00:00
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.
2020-03-18 17:57:41 +00:00
d7eb600b59
mavsdk_tests: improve test name/description
2020-03-18 17:57:41 +00:00
b2e300ad1f
mavsdk_tests: improve test output readability
2020-03-18 17:57:41 +00:00
54645268ed
mavsdk_tests: only print error on failure
2020-03-18 17:57:41 +00:00
911cdc8774
mavsdk_tests: output less verbose unless needed
2020-03-18 17:57:41 +00:00
0989e90b4a
Tools: exit as straightaway with DONT_RUN set
2020-03-18 17:57:41 +00:00
bfef243dba
mavsdk_tests: write output to logs folder
...
And create folder if it doesn't exist already.
2020-03-18 17:57:41 +00:00
5ba28d417a
mavsdk_tests: try using tags as intended
...
The tags should enable use to assemble the tests in various ways. This
will probably require some iterations though.
2020-03-18 17:57:41 +00:00
512faa6ebe
mavsdk_tests: use CHECK if we don't need to abort
2020-03-18 17:57:41 +00:00
821f7c3cd9
mavsdk_tests: remove unused/not working test
...
We can add it again once fixedwing is supported. Until then, this is
just confusing.
2020-03-18 17:57:41 +00:00
fb5b05ec39
mavsdk_tests: add missing unit
2020-03-18 17:57:41 +00:00
a5d1ce91e4
mavsdk_tests: consolidate level of abstraction
...
This moves the CHECK/REQUIRE inside of AutopilotTester.
2020-03-18 17:57:41 +00:00
6a4a4bd0d6
workflows: adapt to mavsdk_tests cli changes
2020-03-18 17:57:41 +00:00
70eb444f17
mavsdk_tests: improve naming of argument
...
We abort when we already failed so this makes more sense.
2020-03-18 17:57:41 +00:00
41b2362dcf
mavsdk_tests: add more config into JSON
2020-03-18 17:57:41 +00:00
c61cd10db5
mavsdk_tests: without speedup the VTOL takes time
2020-03-18 17:57:41 +00:00
b4916fdecb
mavsdk_tests: move config into json file
2020-03-18 17:57:41 +00:00
Julian Oes