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

Non Responsive Ui Button #8127

Closed
Devdatt-Joshi opened this issue Jan 23, 2024 · 4 comments
Closed

Non Responsive Ui Button #8127

Devdatt-Joshi opened this issue Jan 23, 2024 · 4 comments
Labels
TYPE: bug The described behavior is considered as wrong (bug).

Comments

@Devdatt-Joshi
Copy link

What is your Scenario?

Verify weather user is able to Login To the Portal

What is the Current behavior?

User is not Able to login to the portal because login button is not getting pressed

What is the Expected behavior?

user is able to login and "Login" button got is clicked.

What is the public URL of the test page? (attach your complete example)

I have written a test case in this test case we are logging to our portal but Login button is non responsive now.
Initially is was working but from last 5 days i am observing the same. I am Blocked with the further execution because initial stage itself is not working. even when we press this "Login" Button on screen displayed in test cafe screen its not working.
But this Button is working on my local on same browser having same version, only when i am running this test case from TestCafe Its failing.
URL : https://qa-rapidquoteui-appservice.azurewebsites.net/app/dashboard

What is your TestCafe test code?

await t.wait(10000);

await t.click(Selector('button[class="MuiButtonBase-root MuiButton-root MuiButton-contained jss40 MuiButton-containedPrimary"][type="submit"]'));

await t.wait(10000);
image

Your complete configuration file

No response

Your complete test report

No response

Screenshots

image

Steps to Reproduce

1.Open https://qa-rapidquoteui-appservice.azurewebsites.net/app/dashboard
2.Click on Login Button

TestCafe version

3.3.0

Node.js version

v20.10.0

Command-line arguments

testcafe chrome .\App_Process.js

Browser name(s) and version(s)

Chrome 120.0.0.0

Platform(s) and version(s)

Windows 11

Other

the button is clickable manually but not clickable using Test cafe.

@Devdatt-Joshi Devdatt-Joshi added the TYPE: bug The described behavior is considered as wrong (bug). label Jan 23, 2024
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Jan 23, 2024
@PavelMor25
Copy link
Collaborator

Hello @Devdatt-Joshi, I was able to reproduce the issue.
Could you please elaborate on why you are running your test in proxy mode? Native automation resolves the issue.

@PavelMor25 PavelMor25 added STATE: Need clarification An issue lacks information for further research. and removed STATE: Need response An issue that requires a response or attention from the team. labels Jan 26, 2024
@Devdatt-Joshi
Copy link
Author

Devdatt-Joshi commented Jan 31, 2024

yes, this issue is resolved now for VS Code but still getting the same error for Desktop Application of TestCafe and not able to Disable the Proxys.
When i started to record the test case and open the below link
LINK : https://qa-rapidquoteui-appservice.azurewebsites.net/app/dashboard
Its starting the recording but "Login" Button not works.

Please refer below attached video for the same.
We are blocked in the process please help us to resolve it.

TestCafe.issue.mp4

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Jan 31, 2024
@github-actions github-actions bot removed the STATE: Need clarification An issue lacks information for further research. label Jan 31, 2024
@Devdatt-Joshi
Copy link
Author

i have changed the setting also tried with settings>>Bypass proxy for>> but not working getting same issue

@PavelMor25
Copy link
Collaborator

Hello @Devdatt-Joshi,

The option to disable proxy mode is planned for the next TestCafe Studio update. Please stay tuned for updates. Unfortunately, there is currently no solution or workaround to the issue in TestCafe Studio.

Since this issue is reproducible only in TestCafe Studio, I'll close the issue as it works as expected in TestCafe with native automation mode.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

2 participants