Skip to content

Side Runner does not take the variables from the previous test case in the same test suite #1735

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

Closed
ianhe1 opened this issue Nov 27, 2023 · 11 comments

Comments

@ianhe1
Copy link

ianhe1 commented Nov 27, 2023

🐛 Bug Report

I have a test suite that contains a number of test cases.
test suite 1
test case 1 - set environment variables (one of the variables is user ID)
test case 2 - login (using the used ID that was set in the test case 1)
test case 3 - carry out web page operations
test case 4 - ....

The test runs fine in Selenium IDE
But it failed when I run from side runner
I can see that the user ID is not passed to the login test case.

Environment

OS: Windows 11
Selenium IDE Version: 3.1.7
Selenium SIDE Runner Version: 4.0.0-alpha.60
Please note that selenium-side-runner supports Node.js 8 - 10
-->
Node version: 18.16.0
Only required if using selenium-side-runner
-->
Browser:
Browser Version: Chrome Version 119.0.6045.160 (Official Build) (64-bit)

@ianhe1
Copy link
Author

ianhe1 commented Nov 27, 2023

I remember the similar test was running fine before. Could it be due to that node version? I have latest node js installed on my machine. I noticed that the side runner supports node.js 8-10

@ianhe1
Copy link
Author

ianhe1 commented Nov 27, 2023

IanheTestProject.zip
Here is the sample side file for reproduce the issue.

@toddtarsi
Copy link
Contributor

@ianhe1 - Thank you for sharing repro and steps. I'll try taking a look later tonight. I probably need to adjust my handling of the variables w/r/t the persist session boolean

@ianhe1
Copy link
Author

ianhe1 commented Nov 27, 2023

@toddtarsi Thank you very much Todd.

@toddtarsi
Copy link
Contributor

@ianhe1 - Sorry that took a couple extra days, batched up a bunch of little improvements and fixes.

.58 is going out tonight and should be an overall improvement here. I used your side file to test, thanks for that! Please let me know your experience.

@ianhe1
Copy link
Author

ianhe1 commented Nov 30, 2023

Thank you @toddtarsi for your help. I will test it out and let you know. How can I get your fix? Just reinstall the latest side runner?

@toddtarsi
Copy link
Contributor

Yep! I keep publishing new versions here:

https://github.com/SeleniumHQ/selenium-ide/releases

@toddtarsi
Copy link
Contributor

Oh oops, that's the IDE! Yes, there should be a new version of the side runner on npm

@toddtarsi
Copy link
Contributor

npm i selenium-side-runner@latest

@ianhe1
Copy link
Author

ianhe1 commented Dec 1, 2023

@toddtarsi Got it. I reinstalled the runner and tested your fix. It works now! Thank you very much Todd for your help in resolving this issue so quickly. Very much appreciated!

@ianhe1 ianhe1 closed this as completed Dec 1, 2023
Copy link

github-actions bot commented Jan 1, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants