testscript execution behaves differently in Firefox and Chrome while manipulating a element












1














I'm facing a weird problem, which I will try to describe in the next rows.

Thank you in advance for your help!



The problem is that in my case, Testcafe behaves differently when running the same test script on different browsers.
testcafe: 0.23.1
firefox: 63.0.1
chrome: 70.0.3538.102
typescript: 3.1.6



Typescript code from the executed test script:



import { Selector, t } from 'testcafe';
fixture `stackoverflow`
.page `https://www.verivox.de/internet-vergleich/internetundtelefon/?Prefix=030&speed=16000#/offer?i=eyJmaWx0ZXIiOltudWxsLDE2MDAwLDEsbnVsbCwiMDMwIiwxLDEsMSxudWxsLDEsMSxudWxsLC0xLG51bGwsbnVsbCwicHJpY2UtYXNjIiwyLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCw2XSwiZGlhbG9nIjpbbnVsbF0sIm9mZmVyQ3JpdGVyaWEiOlsiNjM0ODkyIiwiMTg0ODYiLG51bGwsIjI0IiwzLDIsIjUwMDAwIiwiMTAwMDAiLG51bGwsbnVsbCwxLG51bGwsbnVsbCxudWxsLCIyIiwxLG51bGwsIjAzMCIsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLDEsNixudWxsLG51bGwsbnVsbF19`;
test('1', async () => {

const acceptCookiesButton = Selector('span.gdpr-vx-consent-bar-button');
const showAvailabilityCheckButton = Selector(Selector('a').withAttribute('class', /offer-page-cta/));
const contactDataEMailTextInput = Selector('#PersonalData_ContactData_EMail');
const confirmationEmailTextInput = Selector('#PersonalData_ContactData_EMailConfirmation');
const genderSelect = Selector('select[name="PersonalData.AddressData.ConnectionAddress.Gender"]');
const genderSelectOptionGet = genderSelect.find('option');
const genderSelectOption = Selector(genderSelectOptionGet);
const firstNameTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_FirstName');
const nameTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_Name');
const zipTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_Zip');
const cityTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_City');
const buildingTypeRadioInput = Selector('#Einfamilienhaus');
const bankInformationTypeRadioInput = Selector('#PersonalData_BankData_BankInformationType_KnrBlz');
const bankCodeTextInput = Selector('#PersonalData_BankData_BankCode');

await t
.click(acceptCookiesButton)
.click(showAvailabilityCheckButton)
.wait(2000)
.typeText(contactDataEMailTextInput, 'asd@asd.asd')
.typeText(confirmationEmailTextInput, 'asd@asd.asd')
.click(genderSelect)
.click(genderSelectOption.withText('Herr'))
.typeText(firstNameTextInput, 'Test')
.typeText(nameTextInput, 'Test')
.typeText(zipTextInput, '67112')
.click(cityTextInput)
.expect(cityTextInput.value).eql('Mutterstadt')
.click(buildingTypeRadioInput)
.click(bankInformationTypeRadioInput)
.wait(2000)
.expect(bankCodeTextInput.exists).ok('field not displayed');

});


I am using VisualStudio Code to write my code, and I'm executing the test in Firefox browser, with the option -e:




testcafe firefox .stackoverflow.ts -e




Question 1:
I'm executing the exactly same test script with
Firefox: everything works, test passes
Chrome: test fails and I receive the below error:



1) The element that matches the specified selector is not visible.

Browser: Chrome 70.0.3538 / Windows 10.0.0

38 | .click(showAvailabilityCheckButton)
39 | .wait(2000)
40 | .typeText(contactDataEMailTextInput, 'asd@asd.asd')
41 | .typeText(confirmationEmailTextInput, 'asd@asd.asd')
42 | .click(genderSelect)
> 43 | .click(genderSelectOption.withText('Herr'))
44 | .typeText(firstNameTextInput, 'Test')
45 | .typeText(nameTextInput, 'Test')
46 | .typeText(zipTextInput, '67112')
47 | .click(cityTextInput)
48 | .expect(cityTextInput.value).eql('Mutterstadt')

at Object.<anonymous> (C:gcogco-e2e-baselinesrcplaygrounde2etestsstackoverflow.ts:43:10)


In order to avoid this error, I'm doing the next workaround:




.click(genderSelect).click(genderSelect)




and now, running the test script on Chrome browser also returns a pass result.
What is wrong in my code, and why do I encounter this difference in behavior?



Question 2:
Considering I'm using the above workaround (the 2 clicks), executing the test script under Chrome, gets me to the next problem:



 Running tests in:
- Chrome 70.0.3538 / Windows 10.0.0
stackoverflow
√ 1
1 passed (34s)


Test is passing, even tho not all the code lines are executed..., because looking at the radio box I'm trying to click and having the browser visible,




.click(buildingTypeRadioInput)




the radio box is clearly not clicked, but still the test passes?!
There are some other code lines after this line that are not executed
As a temporary solution, again I'm doing this:




.click(buildingTypeRadioInput).click(buildingTypeRadioInput)




just to make sure that the test does what I want him to do.
What is wrong in my code, and why do I encounter this issue, with returning a pass instead of a fail?










share|improve this question
























  • first workaround to eliminate the differences between browsers: 1. I am maximizing the browser window; 2. instead of selecting an effective option (the normal and logical way) from the combo, I will press the Down Key, which will select the first option... 3. now, without doing anything else, the radioBox is also clicked :)
    – Eugen
    Nov 23 '18 at 9:23












  • does the post need more details? is it reproducible for someone else except me?
    – Eugen
    Nov 23 '18 at 13:30
















1














I'm facing a weird problem, which I will try to describe in the next rows.

Thank you in advance for your help!



The problem is that in my case, Testcafe behaves differently when running the same test script on different browsers.
testcafe: 0.23.1
firefox: 63.0.1
chrome: 70.0.3538.102
typescript: 3.1.6



Typescript code from the executed test script:



import { Selector, t } from 'testcafe';
fixture `stackoverflow`
.page `https://www.verivox.de/internet-vergleich/internetundtelefon/?Prefix=030&speed=16000#/offer?i=eyJmaWx0ZXIiOltudWxsLDE2MDAwLDEsbnVsbCwiMDMwIiwxLDEsMSxudWxsLDEsMSxudWxsLC0xLG51bGwsbnVsbCwicHJpY2UtYXNjIiwyLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCw2XSwiZGlhbG9nIjpbbnVsbF0sIm9mZmVyQ3JpdGVyaWEiOlsiNjM0ODkyIiwiMTg0ODYiLG51bGwsIjI0IiwzLDIsIjUwMDAwIiwiMTAwMDAiLG51bGwsbnVsbCwxLG51bGwsbnVsbCxudWxsLCIyIiwxLG51bGwsIjAzMCIsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLDEsNixudWxsLG51bGwsbnVsbF19`;
test('1', async () => {

const acceptCookiesButton = Selector('span.gdpr-vx-consent-bar-button');
const showAvailabilityCheckButton = Selector(Selector('a').withAttribute('class', /offer-page-cta/));
const contactDataEMailTextInput = Selector('#PersonalData_ContactData_EMail');
const confirmationEmailTextInput = Selector('#PersonalData_ContactData_EMailConfirmation');
const genderSelect = Selector('select[name="PersonalData.AddressData.ConnectionAddress.Gender"]');
const genderSelectOptionGet = genderSelect.find('option');
const genderSelectOption = Selector(genderSelectOptionGet);
const firstNameTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_FirstName');
const nameTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_Name');
const zipTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_Zip');
const cityTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_City');
const buildingTypeRadioInput = Selector('#Einfamilienhaus');
const bankInformationTypeRadioInput = Selector('#PersonalData_BankData_BankInformationType_KnrBlz');
const bankCodeTextInput = Selector('#PersonalData_BankData_BankCode');

await t
.click(acceptCookiesButton)
.click(showAvailabilityCheckButton)
.wait(2000)
.typeText(contactDataEMailTextInput, 'asd@asd.asd')
.typeText(confirmationEmailTextInput, 'asd@asd.asd')
.click(genderSelect)
.click(genderSelectOption.withText('Herr'))
.typeText(firstNameTextInput, 'Test')
.typeText(nameTextInput, 'Test')
.typeText(zipTextInput, '67112')
.click(cityTextInput)
.expect(cityTextInput.value).eql('Mutterstadt')
.click(buildingTypeRadioInput)
.click(bankInformationTypeRadioInput)
.wait(2000)
.expect(bankCodeTextInput.exists).ok('field not displayed');

});


I am using VisualStudio Code to write my code, and I'm executing the test in Firefox browser, with the option -e:




testcafe firefox .stackoverflow.ts -e




Question 1:
I'm executing the exactly same test script with
Firefox: everything works, test passes
Chrome: test fails and I receive the below error:



1) The element that matches the specified selector is not visible.

Browser: Chrome 70.0.3538 / Windows 10.0.0

38 | .click(showAvailabilityCheckButton)
39 | .wait(2000)
40 | .typeText(contactDataEMailTextInput, 'asd@asd.asd')
41 | .typeText(confirmationEmailTextInput, 'asd@asd.asd')
42 | .click(genderSelect)
> 43 | .click(genderSelectOption.withText('Herr'))
44 | .typeText(firstNameTextInput, 'Test')
45 | .typeText(nameTextInput, 'Test')
46 | .typeText(zipTextInput, '67112')
47 | .click(cityTextInput)
48 | .expect(cityTextInput.value).eql('Mutterstadt')

at Object.<anonymous> (C:gcogco-e2e-baselinesrcplaygrounde2etestsstackoverflow.ts:43:10)


In order to avoid this error, I'm doing the next workaround:




.click(genderSelect).click(genderSelect)




and now, running the test script on Chrome browser also returns a pass result.
What is wrong in my code, and why do I encounter this difference in behavior?



Question 2:
Considering I'm using the above workaround (the 2 clicks), executing the test script under Chrome, gets me to the next problem:



 Running tests in:
- Chrome 70.0.3538 / Windows 10.0.0
stackoverflow
√ 1
1 passed (34s)


Test is passing, even tho not all the code lines are executed..., because looking at the radio box I'm trying to click and having the browser visible,




.click(buildingTypeRadioInput)




the radio box is clearly not clicked, but still the test passes?!
There are some other code lines after this line that are not executed
As a temporary solution, again I'm doing this:




.click(buildingTypeRadioInput).click(buildingTypeRadioInput)




just to make sure that the test does what I want him to do.
What is wrong in my code, and why do I encounter this issue, with returning a pass instead of a fail?










share|improve this question
























  • first workaround to eliminate the differences between browsers: 1. I am maximizing the browser window; 2. instead of selecting an effective option (the normal and logical way) from the combo, I will press the Down Key, which will select the first option... 3. now, without doing anything else, the radioBox is also clicked :)
    – Eugen
    Nov 23 '18 at 9:23












  • does the post need more details? is it reproducible for someone else except me?
    – Eugen
    Nov 23 '18 at 13:30














1












1








1







I'm facing a weird problem, which I will try to describe in the next rows.

Thank you in advance for your help!



The problem is that in my case, Testcafe behaves differently when running the same test script on different browsers.
testcafe: 0.23.1
firefox: 63.0.1
chrome: 70.0.3538.102
typescript: 3.1.6



Typescript code from the executed test script:



import { Selector, t } from 'testcafe';
fixture `stackoverflow`
.page `https://www.verivox.de/internet-vergleich/internetundtelefon/?Prefix=030&speed=16000#/offer?i=eyJmaWx0ZXIiOltudWxsLDE2MDAwLDEsbnVsbCwiMDMwIiwxLDEsMSxudWxsLDEsMSxudWxsLC0xLG51bGwsbnVsbCwicHJpY2UtYXNjIiwyLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCw2XSwiZGlhbG9nIjpbbnVsbF0sIm9mZmVyQ3JpdGVyaWEiOlsiNjM0ODkyIiwiMTg0ODYiLG51bGwsIjI0IiwzLDIsIjUwMDAwIiwiMTAwMDAiLG51bGwsbnVsbCwxLG51bGwsbnVsbCxudWxsLCIyIiwxLG51bGwsIjAzMCIsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLDEsNixudWxsLG51bGwsbnVsbF19`;
test('1', async () => {

const acceptCookiesButton = Selector('span.gdpr-vx-consent-bar-button');
const showAvailabilityCheckButton = Selector(Selector('a').withAttribute('class', /offer-page-cta/));
const contactDataEMailTextInput = Selector('#PersonalData_ContactData_EMail');
const confirmationEmailTextInput = Selector('#PersonalData_ContactData_EMailConfirmation');
const genderSelect = Selector('select[name="PersonalData.AddressData.ConnectionAddress.Gender"]');
const genderSelectOptionGet = genderSelect.find('option');
const genderSelectOption = Selector(genderSelectOptionGet);
const firstNameTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_FirstName');
const nameTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_Name');
const zipTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_Zip');
const cityTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_City');
const buildingTypeRadioInput = Selector('#Einfamilienhaus');
const bankInformationTypeRadioInput = Selector('#PersonalData_BankData_BankInformationType_KnrBlz');
const bankCodeTextInput = Selector('#PersonalData_BankData_BankCode');

await t
.click(acceptCookiesButton)
.click(showAvailabilityCheckButton)
.wait(2000)
.typeText(contactDataEMailTextInput, 'asd@asd.asd')
.typeText(confirmationEmailTextInput, 'asd@asd.asd')
.click(genderSelect)
.click(genderSelectOption.withText('Herr'))
.typeText(firstNameTextInput, 'Test')
.typeText(nameTextInput, 'Test')
.typeText(zipTextInput, '67112')
.click(cityTextInput)
.expect(cityTextInput.value).eql('Mutterstadt')
.click(buildingTypeRadioInput)
.click(bankInformationTypeRadioInput)
.wait(2000)
.expect(bankCodeTextInput.exists).ok('field not displayed');

});


I am using VisualStudio Code to write my code, and I'm executing the test in Firefox browser, with the option -e:




testcafe firefox .stackoverflow.ts -e




Question 1:
I'm executing the exactly same test script with
Firefox: everything works, test passes
Chrome: test fails and I receive the below error:



1) The element that matches the specified selector is not visible.

Browser: Chrome 70.0.3538 / Windows 10.0.0

38 | .click(showAvailabilityCheckButton)
39 | .wait(2000)
40 | .typeText(contactDataEMailTextInput, 'asd@asd.asd')
41 | .typeText(confirmationEmailTextInput, 'asd@asd.asd')
42 | .click(genderSelect)
> 43 | .click(genderSelectOption.withText('Herr'))
44 | .typeText(firstNameTextInput, 'Test')
45 | .typeText(nameTextInput, 'Test')
46 | .typeText(zipTextInput, '67112')
47 | .click(cityTextInput)
48 | .expect(cityTextInput.value).eql('Mutterstadt')

at Object.<anonymous> (C:gcogco-e2e-baselinesrcplaygrounde2etestsstackoverflow.ts:43:10)


In order to avoid this error, I'm doing the next workaround:




.click(genderSelect).click(genderSelect)




and now, running the test script on Chrome browser also returns a pass result.
What is wrong in my code, and why do I encounter this difference in behavior?



Question 2:
Considering I'm using the above workaround (the 2 clicks), executing the test script under Chrome, gets me to the next problem:



 Running tests in:
- Chrome 70.0.3538 / Windows 10.0.0
stackoverflow
√ 1
1 passed (34s)


Test is passing, even tho not all the code lines are executed..., because looking at the radio box I'm trying to click and having the browser visible,




.click(buildingTypeRadioInput)




the radio box is clearly not clicked, but still the test passes?!
There are some other code lines after this line that are not executed
As a temporary solution, again I'm doing this:




.click(buildingTypeRadioInput).click(buildingTypeRadioInput)




just to make sure that the test does what I want him to do.
What is wrong in my code, and why do I encounter this issue, with returning a pass instead of a fail?










share|improve this question















I'm facing a weird problem, which I will try to describe in the next rows.

Thank you in advance for your help!



The problem is that in my case, Testcafe behaves differently when running the same test script on different browsers.
testcafe: 0.23.1
firefox: 63.0.1
chrome: 70.0.3538.102
typescript: 3.1.6



Typescript code from the executed test script:



import { Selector, t } from 'testcafe';
fixture `stackoverflow`
.page `https://www.verivox.de/internet-vergleich/internetundtelefon/?Prefix=030&speed=16000#/offer?i=eyJmaWx0ZXIiOltudWxsLDE2MDAwLDEsbnVsbCwiMDMwIiwxLDEsMSxudWxsLDEsMSxudWxsLC0xLG51bGwsbnVsbCwicHJpY2UtYXNjIiwyLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCw2XSwiZGlhbG9nIjpbbnVsbF0sIm9mZmVyQ3JpdGVyaWEiOlsiNjM0ODkyIiwiMTg0ODYiLG51bGwsIjI0IiwzLDIsIjUwMDAwIiwiMTAwMDAiLG51bGwsbnVsbCwxLG51bGwsbnVsbCxudWxsLCIyIiwxLG51bGwsIjAzMCIsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLDEsNixudWxsLG51bGwsbnVsbF19`;
test('1', async () => {

const acceptCookiesButton = Selector('span.gdpr-vx-consent-bar-button');
const showAvailabilityCheckButton = Selector(Selector('a').withAttribute('class', /offer-page-cta/));
const contactDataEMailTextInput = Selector('#PersonalData_ContactData_EMail');
const confirmationEmailTextInput = Selector('#PersonalData_ContactData_EMailConfirmation');
const genderSelect = Selector('select[name="PersonalData.AddressData.ConnectionAddress.Gender"]');
const genderSelectOptionGet = genderSelect.find('option');
const genderSelectOption = Selector(genderSelectOptionGet);
const firstNameTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_FirstName');
const nameTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_Name');
const zipTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_Zip');
const cityTextInput = Selector('#PersonalData_AddressData_ConnectionAddress_City');
const buildingTypeRadioInput = Selector('#Einfamilienhaus');
const bankInformationTypeRadioInput = Selector('#PersonalData_BankData_BankInformationType_KnrBlz');
const bankCodeTextInput = Selector('#PersonalData_BankData_BankCode');

await t
.click(acceptCookiesButton)
.click(showAvailabilityCheckButton)
.wait(2000)
.typeText(contactDataEMailTextInput, 'asd@asd.asd')
.typeText(confirmationEmailTextInput, 'asd@asd.asd')
.click(genderSelect)
.click(genderSelectOption.withText('Herr'))
.typeText(firstNameTextInput, 'Test')
.typeText(nameTextInput, 'Test')
.typeText(zipTextInput, '67112')
.click(cityTextInput)
.expect(cityTextInput.value).eql('Mutterstadt')
.click(buildingTypeRadioInput)
.click(bankInformationTypeRadioInput)
.wait(2000)
.expect(bankCodeTextInput.exists).ok('field not displayed');

});


I am using VisualStudio Code to write my code, and I'm executing the test in Firefox browser, with the option -e:




testcafe firefox .stackoverflow.ts -e




Question 1:
I'm executing the exactly same test script with
Firefox: everything works, test passes
Chrome: test fails and I receive the below error:



1) The element that matches the specified selector is not visible.

Browser: Chrome 70.0.3538 / Windows 10.0.0

38 | .click(showAvailabilityCheckButton)
39 | .wait(2000)
40 | .typeText(contactDataEMailTextInput, 'asd@asd.asd')
41 | .typeText(confirmationEmailTextInput, 'asd@asd.asd')
42 | .click(genderSelect)
> 43 | .click(genderSelectOption.withText('Herr'))
44 | .typeText(firstNameTextInput, 'Test')
45 | .typeText(nameTextInput, 'Test')
46 | .typeText(zipTextInput, '67112')
47 | .click(cityTextInput)
48 | .expect(cityTextInput.value).eql('Mutterstadt')

at Object.<anonymous> (C:gcogco-e2e-baselinesrcplaygrounde2etestsstackoverflow.ts:43:10)


In order to avoid this error, I'm doing the next workaround:




.click(genderSelect).click(genderSelect)




and now, running the test script on Chrome browser also returns a pass result.
What is wrong in my code, and why do I encounter this difference in behavior?



Question 2:
Considering I'm using the above workaround (the 2 clicks), executing the test script under Chrome, gets me to the next problem:



 Running tests in:
- Chrome 70.0.3538 / Windows 10.0.0
stackoverflow
√ 1
1 passed (34s)


Test is passing, even tho not all the code lines are executed..., because looking at the radio box I'm trying to click and having the browser visible,




.click(buildingTypeRadioInput)




the radio box is clearly not clicked, but still the test passes?!
There are some other code lines after this line that are not executed
As a temporary solution, again I'm doing this:




.click(buildingTypeRadioInput).click(buildingTypeRadioInput)




just to make sure that the test does what I want him to do.
What is wrong in my code, and why do I encounter this issue, with returning a pass instead of a fail?







typescript visual-studio-code automated-tests e2e-testing testcafe






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 '18 at 13:42









Alex Skorkin

2,1171532




2,1171532










asked Nov 21 '18 at 15:34









Eugen

312112




312112












  • first workaround to eliminate the differences between browsers: 1. I am maximizing the browser window; 2. instead of selecting an effective option (the normal and logical way) from the combo, I will press the Down Key, which will select the first option... 3. now, without doing anything else, the radioBox is also clicked :)
    – Eugen
    Nov 23 '18 at 9:23












  • does the post need more details? is it reproducible for someone else except me?
    – Eugen
    Nov 23 '18 at 13:30


















  • first workaround to eliminate the differences between browsers: 1. I am maximizing the browser window; 2. instead of selecting an effective option (the normal and logical way) from the combo, I will press the Down Key, which will select the first option... 3. now, without doing anything else, the radioBox is also clicked :)
    – Eugen
    Nov 23 '18 at 9:23












  • does the post need more details? is it reproducible for someone else except me?
    – Eugen
    Nov 23 '18 at 13:30
















first workaround to eliminate the differences between browsers: 1. I am maximizing the browser window; 2. instead of selecting an effective option (the normal and logical way) from the combo, I will press the Down Key, which will select the first option... 3. now, without doing anything else, the radioBox is also clicked :)
– Eugen
Nov 23 '18 at 9:23






first workaround to eliminate the differences between browsers: 1. I am maximizing the browser window; 2. instead of selecting an effective option (the normal and logical way) from the combo, I will press the Down Key, which will select the first option... 3. now, without doing anything else, the radioBox is also clicked :)
– Eugen
Nov 23 '18 at 9:23














does the post need more details? is it reproducible for someone else except me?
– Eugen
Nov 23 '18 at 13:30




does the post need more details? is it reproducible for someone else except me?
– Eugen
Nov 23 '18 at 13:30












1 Answer
1






active

oldest

votes


















1














I was able to reproduce the first issue. I think this unexpected behavior is somehow connected with the information popup. You mentioned that you are maximizing the browser window and it helps. As I see, this leads to changes in the render, so the cause of the issue lies here. I think it is a bug so I've created a bug report in the TestCafe repository. For now, I recommend using the workaround with the maximizing.



As for the second question, I've found that the markup of radio input is complex (inputs are invisible, opacity equals  0), so I recommend you modify your selector in the following manner:



const buildingTypeRadioInput = Selector('label[for="Einfamilienhaus"]');






share|improve this answer





















  • 10Q @alex. Will try this out.
    – Eugen
    Nov 26 '18 at 7:01










  • yes, the selection of the radiobox is much faster now. It's doing it like instant, not waiting anymore after the timeout
    – Eugen
    Nov 26 '18 at 10:43











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53415501%2ftestscript-execution-behaves-differently-in-firefox-and-chrome-while-manipulatin%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














I was able to reproduce the first issue. I think this unexpected behavior is somehow connected with the information popup. You mentioned that you are maximizing the browser window and it helps. As I see, this leads to changes in the render, so the cause of the issue lies here. I think it is a bug so I've created a bug report in the TestCafe repository. For now, I recommend using the workaround with the maximizing.



As for the second question, I've found that the markup of radio input is complex (inputs are invisible, opacity equals  0), so I recommend you modify your selector in the following manner:



const buildingTypeRadioInput = Selector('label[for="Einfamilienhaus"]');






share|improve this answer





















  • 10Q @alex. Will try this out.
    – Eugen
    Nov 26 '18 at 7:01










  • yes, the selection of the radiobox is much faster now. It's doing it like instant, not waiting anymore after the timeout
    – Eugen
    Nov 26 '18 at 10:43
















1














I was able to reproduce the first issue. I think this unexpected behavior is somehow connected with the information popup. You mentioned that you are maximizing the browser window and it helps. As I see, this leads to changes in the render, so the cause of the issue lies here. I think it is a bug so I've created a bug report in the TestCafe repository. For now, I recommend using the workaround with the maximizing.



As for the second question, I've found that the markup of radio input is complex (inputs are invisible, opacity equals  0), so I recommend you modify your selector in the following manner:



const buildingTypeRadioInput = Selector('label[for="Einfamilienhaus"]');






share|improve this answer





















  • 10Q @alex. Will try this out.
    – Eugen
    Nov 26 '18 at 7:01










  • yes, the selection of the radiobox is much faster now. It's doing it like instant, not waiting anymore after the timeout
    – Eugen
    Nov 26 '18 at 10:43














1












1








1






I was able to reproduce the first issue. I think this unexpected behavior is somehow connected with the information popup. You mentioned that you are maximizing the browser window and it helps. As I see, this leads to changes in the render, so the cause of the issue lies here. I think it is a bug so I've created a bug report in the TestCafe repository. For now, I recommend using the workaround with the maximizing.



As for the second question, I've found that the markup of radio input is complex (inputs are invisible, opacity equals  0), so I recommend you modify your selector in the following manner:



const buildingTypeRadioInput = Selector('label[for="Einfamilienhaus"]');






share|improve this answer












I was able to reproduce the first issue. I think this unexpected behavior is somehow connected with the information popup. You mentioned that you are maximizing the browser window and it helps. As I see, this leads to changes in the render, so the cause of the issue lies here. I think it is a bug so I've created a bug report in the TestCafe repository. For now, I recommend using the workaround with the maximizing.



As for the second question, I've found that the markup of radio input is complex (inputs are invisible, opacity equals  0), so I recommend you modify your selector in the following manner:



const buildingTypeRadioInput = Selector('label[for="Einfamilienhaus"]');







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 23 '18 at 15:24









Alex Kamaev

61117




61117












  • 10Q @alex. Will try this out.
    – Eugen
    Nov 26 '18 at 7:01










  • yes, the selection of the radiobox is much faster now. It's doing it like instant, not waiting anymore after the timeout
    – Eugen
    Nov 26 '18 at 10:43


















  • 10Q @alex. Will try this out.
    – Eugen
    Nov 26 '18 at 7:01










  • yes, the selection of the radiobox is much faster now. It's doing it like instant, not waiting anymore after the timeout
    – Eugen
    Nov 26 '18 at 10:43
















10Q @alex. Will try this out.
– Eugen
Nov 26 '18 at 7:01




10Q @alex. Will try this out.
– Eugen
Nov 26 '18 at 7:01












yes, the selection of the radiobox is much faster now. It's doing it like instant, not waiting anymore after the timeout
– Eugen
Nov 26 '18 at 10:43




yes, the selection of the radiobox is much faster now. It's doing it like instant, not waiting anymore after the timeout
– Eugen
Nov 26 '18 at 10:43


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53415501%2ftestscript-execution-behaves-differently-in-firefox-and-chrome-while-manipulatin%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

404 Error Contact Form 7 ajax form submitting

How to know if a Active Directory user can login interactively

Refactoring coordinates for Minecraft Pi buildings written in Python