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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This test case automates the Test Case SU 2.5.
Verify the DUT behaves according the spec when is applying the software update.
In this test case Im using event handlers to verify the updates are happening in the expected timeframes, for this case Im validating updates are not happening and start in the limits of the expected values.
Some changes were made into run_python_test in the method monitor_app_restart_requests. The break from the while loop was removed because this only allowed one restart. Also the apps is stopped first to avoid por collisions in case the argument --secure-device-port is used to launch the app.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This test case automates the Test Case SU 2.5.
Verify the DUT behaves according the spec when is applying the software update.
In this test case Im using event handlers to verify the updates are happening in the expected timeframes, for this case Im validating updates are not happening and start in the limits of the expected values.
Related issues
Fixes: project-chip/matter-test-scripts#656
Testing
Launch the requestor:
./out/debug/chip-ota-requestor-app --discriminator 123 --passcode 2123 --secured-device-port 5540 --KVS /tmp/chip_kvs_requestor --autoApplyImageLaunch the test case
python3 src/python_testing/TC_SU_2_5.py --commissioning-method on-network --passcode 2123 --discriminator 123 --endpoint 0 --nodeId 123