Skip to content

[WIP] MAVLink tests - what do we have now? #134

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[WIP] MAVLink tests - what do we have now? #134

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions en/SUMMARY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,4 +59,5 @@
* [ualberta.xml](messages/ualberta.md)
* [uAvionix.xml](messages/uAvionix.md)
* [Contributing](contributing/contributing.md)
* [Testing](guide/testing.md)
* [Support](about/support.md)
18 changes: 18 additions & 0 deletions en/guide/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Testing

## Changes to Mavgen

Changes to the mavgen generator (in [ArduPilot/pymavlink](https://github.com/ArduPilot/pymavlink)) are tested on every PR prior to acceptance into the master branch.

You can run the test code yourself in Ubuntu.
1. Install additional dependencies for gtest:
```sh
sudo apt-get install cmake libgtest-dev
```
1. Run the test generator from the pymavlink directory:
```sh
cd pymavlink
./test_generator.sh
```
> **Tip** The tests require message definitions in **../message_definitions/** (i.e. at the level above the **pymavlink** directory).
This is how things are set up when you're running the tests from the *mavlink* repo.