Clean up testing docs
Motivation
Our testing docs are out of sync with the status of the code and not suggesting the right things for the cargo ODD work.
Documentation
There is a document about integration testing in the documentation https://autowarefoundation.gitlab.io/autoware.auto/AutowareAuto/integration-testing.html
It contains general information about integration testing, which is worth preserving. But it also
spends a great deal about explaining the integration_tests
framework that spun out of Apex.AI.
There is one paragraph on integration testing in
https://autowarefoundation.gitlab.io/autoware.auto/AutowareAuto/contributor-guidelines.html#integration-tests-in-ros
that proposes launch_testing
as the framework for integration, in line with Apex.AI internal
guidelines.
Available tests
There seems to be no more use of integration_tests
.
launch_testing
is used in
state_estimation_node
lidar_integration
spinnaker_camera_node
-
velodyne
driver pure_pursuit
Definition of done
-
https://autowarefoundation.gitlab.io/autoware.auto/AutowareAuto/integration-testing.html is revamped -
drop reference to integration_tests
framework all docs and recommendlaunch_testing
. Already the case inunit-testing.md
-
In contributor-guidelines.md
, the other articles on testing are referenced. -
the unit-testing.md
file is split into two articles: 1st half is about general testing, 2nd part is about unit -
mention component smoke tests in docs/MR template -
check if integration_tests
can be removed