You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: planning/planning_test_utils/README.md
+9-3
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
-
# Planning Test Utils
1
+
# Test Utils
2
2
3
3
## Background
4
4
5
-
Several planning components and modules have already adopted unit testing, so a common library to ease the process of writing unit tests is necessary.
5
+
Several Autoware's components and modules have already adopted unit testing, so a common library to ease the process of writing unit tests is necessary.
6
6
7
7
## Purpose
8
8
9
-
The objective of the `planning_test_utils` is to develop a unit testing library for the planning components. This library will include
9
+
The objective of the `test_utils` is to develop a unit testing library for the Autoware components. This library will include
10
10
11
11
- commonly used functions
12
12
- input/mock data parser
@@ -36,3 +36,9 @@ The following illustrates the design of the map.
36
36
## Implemented tests
37
37
38
38
The mock data parser is unit tested to ensure there are no defects when parsing the input data.
39
+
40
+
## Example use cases
41
+
42
+
### Autoware Planning Test Manager
43
+
44
+
The goal of the [Autoware Planning Test Manager](https://autowarefoundation.github.io/autoware.universe/main/planning/autoware_planning_test_manager/) is to test planning module nodes. The `PlanningInterfaceTestManager` class ([source code](https://github.com/autowarefoundation/autoware.universe/blob/main/planning/autoware_planning_test_manager/src/autoware_planning_test_manager.cpp)) creates wrapper functions based on the `test_utils` functions.
0 commit comments