Skip to content
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

Use proper link to integration test guide #1901

Merged
merged 1 commit into from
Feb 21, 2023
Merged
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions docs/UsersGuide/best/development-practice.md
Original file line number Diff line number Diff line change
Expand Up @@ -206,10 +206,10 @@ To add a component to the topology:
As the topology comes together, it is helpful to write system-level tests for subsystems of the
overall deployment. This makes sure that as a system, top-level requirements are met.

The fprime-gds has a python API that can be used to write integration test cases that support sending commands, checking for events, and getting telemetry channel readings. To get started with writing integration tests, check out the [GDS integration test guide](../dev/testAPI/user_guide).
The fprime-gds has a python API that can be used to write integration test cases that support sending commands, checking for events, and getting telemetry channel readings. To get started with writing integration tests, check out the [GDS integration test guide](../dev/testAPI/user_guide.md).

## Conclusion

This guide was an overview of the workflow most F´ developers follow, from the start to completion
of a project. These workflows can be applied to any F´ project and should hopefully provide the
smoothest development experience.
smoothest development experience.