Converted from the question
https://bex-demo.finartz.com/checkout
This is caused by bex-expess.js recource loading
On this site the properties of the html element are enumerated in for...in loop. It finds our the processedContext property and defines the getter on it.
fixed by https://github.com/DevExpress/testcafe-hammerhead/pull/1206
Thanks for the fix, when will it be released?
Today or tomorrow we'll release a new version of TestCafe.
@utkusonmez We've published the fix in the latest alpha version.
npm install -g testcafe@alpha or npm install -g [email protected]
Our test is still not working properly. switchtoIframe function seems to be the problem. Because if we remove it from the test it passes. It throws
"The specified selector does not match any element in the DOM tree."
error right now. In addition after clicking the button, it does not load the iframe, if we add more steps to the test.
/cc @LavrovArtem
Hi @ismailgmutlu,
Could you please provide URL to your page, if it possible?
And what is you testcafe version?
I am running the same test with the same URL and uploaded my version to 0.17.0-alpha2.
Hi @ismailgmutlu,
I have investigated your test and it is incorrect. I made some changes in it, see below:
import { Selector } from 'testcafe';
fixture `databasetesting`
.page `http://bex-demo.finartz.com/checkout`;
const loginButton = Selector('#test');
test(`Test Speed`, async t => {
await t
.maximizeWindow()
.hover(loginButton)
.expect(loginButton.visible).ok()
.switchToIframe(loginButton)
// changes
.click('#loginButton')
.typeText('#username', 'admin')
.typeText('#password', 'admin')
.click('#login');
});
You are right, it is working now. Thanks for help.
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.
Most helpful comment
You are right, it is working now. Thanks for help.