Skip to content
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

Spawn in same tab for rhods 1.17+ #571

Merged
merged 3 commits into from
Sep 21, 2022

Conversation

lugi0
Copy link
Contributor

@lugi0 lugi0 commented Sep 21, 2022

Signed-off-by: Luca Giorgi lgiorgi@redhat.com

Signed-off-by: Luca Giorgi <lgiorgi@redhat.com>
Signed-off-by: Luca Giorgi <lgiorgi@redhat.com>
Signed-off-by: Luca Giorgi <lgiorgi@redhat.com>
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@@ -133,6 +133,12 @@ Get Spawner Environment Variable Value
Spawn Notebook
[Documentation] Start the notebook pod spawn and wait ${spawner_timeout} seconds (DEFAULT: 600s)
[Arguments] ${spawner_timeout}=600 seconds
# TODO: Make sure server spawns in same tab in 1.17+
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe my solution wasn't the best but I dealt with something similar at

${is_data_collection_enabled}= Run Keyword And Return Status Checkbox Should Be Selected

@lugi0 lugi0 merged commit 95cfd21 into red-hat-data-services:master Sep 21, 2022
@@ -133,6 +133,12 @@ Get Spawner Environment Variable Value
Spawn Notebook
[Documentation] Start the notebook pod spawn and wait ${spawner_timeout} seconds (DEFAULT: 600s)
[Arguments] ${spawner_timeout}=600 seconds
# TODO: Make sure server spawns in same tab in 1.17+
# Currently no way to know if option already selected or not
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about something like that ? 🤔

  ${notebook_browser_tab_preference}=  Set Variable  //input[@id="checkbox-notebook-browser-tab-preference"]
  ${new_tab_checked}  Get Element Attribute  ${notebook_browser_tab_preference}  checked
  Run Keyword If  "${new_tab_checked}" == "${None}"  Click Element  xpath:${notebook_browser_tab_preference}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Last I looked at this the checked attribute was no different between the checkbox actually being checked or not.
I went down a rabbit hole chasing Checkbox Should Be Selected and Select Checkbox keywords inherited from Selenium to try and understand what they were doing, but I came up empty handed since it looks like those rely on the WebDriver / Browser / WebElement combination to behave according to the Living HTML standard and self-report their own selectedness or checkedness

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants