-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Feature] Adding Step Endpoint Information #35662
[Feature] Adding Step Endpoint Information #35662
Conversation
Review changes with SemanticDiff. Analyzed 5 of 5 files. Overall, the semantic diff is 15% smaller than the GitHub diff.
|
PR #35662: Size comparison from 0d17a40 to 9be444b Full report (82 builds for bl602, bl702, bl702l, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #35662: Size comparison from 0d17a40 to 9be67e1 Full report (82 builds for bl602, bl702, bl702l, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
7afb143
to
3b00bf5
Compare
PR #35662: Size comparison from 12f04dc to 3b00bf5 Full report (82 builds for bl602, bl702, bl702l, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
3b00bf5
to
ec803c5
Compare
PR #35662: Size comparison from 4bdafa2 to ec803c5 Full report (82 builds for bl602, bl702, bl702l, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
…h logging. Also, the TC_ACE_1_3 and TC_BOOLCFG_2_1 tests were updated to demonstrate how to used the updated hooks to inform the endpoint associated with every step.
Co-authored-by: Boris Zbarsky <[email protected]>
e7ff05b
to
0b0368c
Compare
PR #35662: Size comparison from 237e450 to 0b0368c Full report (88 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
This reverts commit 36fff94. This breaks the TH and the API for the step command is overkill.
This reverts commit 36fff94. This breaks the TH and the API for the step command is overkill.
@cecille This PR entered by mistake in the v1.4 but it was meant to enter only in the v1.5 in sync with the Backend's PR project-chip/certification-tool-backend#147 to handle the feature request project-chip/certification-tool#367. Since I noticed the change was reverted for both master and v1.4, let me know if it's ok to create this PR again for this feature request or if it's necessary to try a different solution. |
* Adding endpoint information to test steps methods and hooks along with logging. Also, the TC_ACE_1_3 and TC_BOOLCFG_2_1 tests were updated to demonstrate how to used the updated hooks to inform the endpoint associated with every step. * Rolling back the test stop unnecessary exception parameter * Updating TestDecoratorHooks with endpoint as well. * Minor grammar fix Co-authored-by: Boris Zbarsky <[email protected]> --------- Co-authored-by: Boris Zbarsky <[email protected]>
…" (project-chip#36198) This reverts commit 36fff94. This breaks the TH and the API for the step command is overkill.
Solves: project-chip/certification-tool#367
Backend Dependency PR: project-chip/certification-tool-backend#147
Warning
The frontend changes and images shown here are not official and for experimental purpose only.
Description
Updating the Step Start hooks and the related code to include an optional endpoint information. Also, some logging were updated to show the endpoint if it exists.
This change depends on the backend's PR, mentioned above, that receives the new endpoint data and redirect it to the frontend via test UI observables so it may access and show as desired.
Please, mind this current solution will not store the endpoint information in the DB and it will not be retrieved for the UI after loading old executions. Anyway, the logs still points the endpoint on the step completion lines.
The
TC_ACE_1_3
andTC_BOOLCFG_2_1
tests were updated to demonstrate how to send the endpoint through the backend hooks. | update to demonstrate how to used the updated hooks to inform the endpoint associated with every step.Use Case Example:
Warning
The frontend changes and images shown here are not official and for experimental purpose only.
The images below show a possible usage of the new endpoint information passed to the frontend using the SDK and Backend changes:
The TC ACE 1.3 example
The TC BOOLCFG 2.1 example