-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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.
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
Failsafe testing #13216
Comments
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
@hamishwillee don't worry removing the |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
Describe problem solved by the proposed feature
We need failsafe testing to test the failsafes in the case of GPS loss, etc.. This means we need integration tests to execute it as well as hooks to cause failures.
As an example we start flying a mission and then RC and datalink fail. In this case we might need to e.g. abort the mission and do RTL.
Describe your preferred solution
This could be added to MAVSDK tests. The hooks to trigger a failure could either be a MAVLink message or a parameters.
The text was updated successfully, but these errors were encountered: