-
Notifications
You must be signed in to change notification settings - Fork 60
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/widget support #2218
Feature/widget support #2218
Conversation
@theresalech, this PR is already reviewed and approved by Ford (by @kshala-ford) and ready for Livio review. |
common.Step("SDL transfers OnSCU notification", sendOnSCU, { 1 }) | ||
common.Step("App sends GetSC RPC for DISPLAYS, no subscribe", sendGetSC, { "DISPLAYS", nil }) | ||
common.Step("SDL transfers OnSCU notification", sendOnSCU, { 2 }) | ||
common.Step("App sends GetSC RPC for DISPLAYS, subscribe=true", sendGetSC, { "DISPLAYS", true }) |
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.
I think this test should at least check for the info string
"Subscribe parameter is ignored. Auto Subscription/Unsubscription is used for DISPLAY capability type."
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.
@JackLivio Please find update in 89f5721
--[[ Local Variables ]] | ||
local params = { | ||
windowID = 1, | ||
windowName = "Name of the primary widget", |
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.
Shouldn't this case be a failure? Proposal hints at the primary widget and needing the same name.
From the proposal:
The primary widget is a special widget, that can be associated with a service type, which is used by the HMI whenever a single widget needs to represent the whole app. The primary widget should be named as the app and can be pre-created by the HMI.
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.
@JackLivio It was agreed with proposal author that SDL should not validate WindowName
for all WIndowIDs = 1 (thus for all PRIMARY WIDGETS).
Mostly by the reason that the name of the main window matches the app name.
@JackLivio Please note one script was updated in 626def3 to verify case described in smartdevicelink/sdl_core#2980 (comment) |
@JackLivio Please note same script was extended to check cases with deleted windows |
I had an issue with this test.
|
@JackLivio That's right since fix in sdl_core has not committed yet. |
@JackLivio Please notice 2 additional scripts were introduced in 1c3147a to cover specific cases described in comments below:
All scripts related to feature can be run on a latest SDL commit: smartdevicelink/sdl_core@ee4e1c7 |
1c3147a
to
46848d9
Compare
Please notice PR is re-based onto HEAD of develop |
Please notice additional script was added in (85d700f) in order to cover cases discussed in |
Expected HMI level is corrected due to SDL requirement:
|
ATF Test Scripts to check #2918
This PR is [ready] for review.
Summary
Scripts for [SDL 0216] - Widget support feature
ATF version
develop
Manual checklist with screenshots
TBA
Changelog
Enhancements
utils.wait()
functionBug Fixes
actions.allowSDL()
function which is required to fix SDL issue for policies inEXTERNAL_PROPRIETARY
flowCLA