-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add unit tests #18
Add unit tests #18
Conversation
Why is there no assertion on the generated motion in terms of their coordinate/PoseWithCell/spline etc.? (to ensure the behaviour doesn't change over new commits). Same goes for some other similar tests. |
I have added tests for the various types of motions, their associated splines / poses, and the computation of costs. Each motion type from Forward, Backward, Point-turn and Lateral has unique aspects which are individually tested. Added also tests which check the validity of underlying values of position and orientation splines in the planner generated trajectories etc. |
# Conflicts: # src/test/CMakeLists.txt # src/test/test_EnvironmentXYZTheta.cpp # src/test/test_ugv_nav4d.cpp
4b32d93
to
7b1dac0
Compare
# Conflicts: # src/test/CMakeLists.txt
# Conflicts: # src/test/CMakeLists.txt
The changes looks good to me |
Added unit tests for core classes. The unit tests for now are just the start and will add more over time.