-
Notifications
You must be signed in to change notification settings - Fork 4
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
Diagnostic Aggregator Testing #4
Diagnostic Aggregator Testing #4
Conversation
Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
…iagnostic_aggregator_demo
* Adds launch-based test, starting aggregator with a yaml configuration * Test is not yet working, something wrong with process orchestration Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
* One passing test, just looking for output of the bond statemachine * One failing test, looking for the actual analyzer output we want to test for Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
Four tests working, testing creation of various analyzers and analyzer groups from yaml specification. |
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.
Generally looks good to me. I'd like to have the std::cout
though addressed.
also I went ahead and pushed 087d391 to address some failing linters.
* launch testing now working withou previous stdcout hack * deleted deprecated (not working) tests Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
@norro I've seen you've updated your branch here. Is this good to be merged in your original PR? |
Signed-off-by: Arne Nordmann <arne.nordmann@de.bosch.com>
@Karsten1987 yes, this could/should be merged into the original PR, as it now has a small demo and working tests. |
This PR introduces a demo and two tests, but...:
One of the tests is supposed to test the analyzer creation of the aggregator from a yaml file. This one, however, is failing since the output it is supposed to match somehow only appears after the test times out.
The second test is succeeding, but only checks for output of the bond state machine, which somehow already appears before the test times out, but is not meaningful to test.
@Karsten1987: This kind-of fixes this as is shows how the tests should look like IMHO. Do you have an idea why the logging output is stalled until launch-testing sends a
SIGINT
to the process under test (aggregator_node
)?The stalling does not happen, if I start the
aggregator_node
withros2 run
(see the demo), so it might be me using ros2 launch-testing not in the intended way.