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
To run integration tests it would be better to rely on a client application, which communicates with caterpillar over d-bus instead of only testing the outcome of its actions.
With #5 the integration test for "there is no update" does not work anymore, as caterpillar has been turned into a long-running application and the tests relied on it exiting at some point.
The text was updated successfully, but these errors were encountered:
More specifically the test has now been removed (6ff7f17) and the test strategy has to be adapted to test using the new d-bus interface instead.
A separate client based on an auto-generated caterpillar proxy can be created to interact with the caterpillar service, depending on test scenario (interactive/ non-interactive).
To run integration tests it would be better to rely on a client application, which communicates with caterpillar over d-bus instead of only testing the outcome of its actions.
With #5 the integration test for "there is no update" does not work anymore, as caterpillar has been turned into a long-running application and the tests relied on it exiting at some point.
The text was updated successfully, but these errors were encountered: