-
Notifications
You must be signed in to change notification settings - Fork 674
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
Injected Client Script only works the first time in Live Mode #4183
Labels
AREA: client
AREA: server
STATE: Auto-locked
An issue has been automatically locked by the Lock bot.
SYSTEM: runner
TYPE: bug
The described behavior is considered as wrong (bug).
Milestone
Comments
Thank you for your report, I've reproduced the issue. We will try to address it in the next development sprint. |
@AndreyBelym was this addressed? |
This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow. |
kirovboris
pushed a commit
to kirovboris/testcafe-phoenix
that referenced
this issue
Dec 18, 2019
…ss#4227) * initial * small refactoring
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
AREA: client
AREA: server
STATE: Auto-locked
An issue has been automatically locked by the Lock bot.
SYSTEM: runner
TYPE: bug
The described behavior is considered as wrong (bug).
What is your Test Scenario?
I like to inject a Client Script and use it in Live Mode
What is the Current behavior?
The injection works when TestCafé starts the Live Mode and runs the test for the first time, but a second time the element is not found and an error is produced:
What is the Expected behavior?
Injection keeps working in combination with Live Mode
Steps to Reproduce:
See https://testing-library.com/docs/testcafe-testing-library/intro for other queries to be used
Someone had a similar issue: testing-library/testcafe-testing-library#28
so we upgraded the testcafe-testing-library to 3.0.0 as suggested, but the problem unfortunately still persisted.
Your Environment details:
The text was updated successfully, but these errors were encountered: