-
Notifications
You must be signed in to change notification settings - Fork 334
Split controller switch test #2177
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
base: master
Are you sure you want to change the base?
Split controller switch test #2177
Conversation
Could you please verify if what I have done is what was expected in the issue description? Should I do it for the rest of the tests like async_controller_lifecycle, async_controller_lifecycle_at_cm_rate etc.? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heyy @ashwinsnambiar
Can you explain the changes a bit?
All I see is that you have moved a part of the test into a different test case. Why?
The idea is to check which part of the BEST_EFFORT strictness logic is covered and add tests to cover the other parts
Hey @saikishor, From what I understood, the I was just following the comment in the issue: #521 (comment). I started out this draft PR which satisfies the first requirement of the splitting the test into lifecycle test and switching multiple controllers. I haven't done the second part, adding a new test for activating multiple controllers when resource collision occurs. Please let me know if I misunderstood the intent somewhere. |
@saikishor, did you understand what I was trying to do? |
Sorry I didn't get back to you on this. Yes, you are right. You are on the right direction :) |
Closes #521
I have split the existing test into two: lifecycle test for single controller and a switch_controller test with unknown or fake controller.
To send us a pull request, please:
colcon test
andpre-commit run
(requires you to install pre-commit bypip3 install pre-commit
)