DevExpress/testcafe-hammerhead

http method not working for invalid credentials

vikaschoudhary89 opened this issue · 2 comments

What is your Scenario?

I am testing an application which is using window based authentication, so I am using testcafe httpmethod for it.

it works fine for valid and invalid credentials but when some user after providing login details, same window pop-op is displayed (validated manually ), for this sort of user I am getting the attached screenshot (error) and it get stuck here and no-further tests are executed.

What is the Current behavior?

image

Attached error page is displayed and next testcase are not running.

What is the Expected behavior?

test should be able to identity error and continue with next tests.

What is your public website URL? (or attach your complete example)

No a public URL

What is your TestCafe test code?

// it never reaches the test logic section.

test
.httpAuth({
username: 'XXX',
password: 'XXX'
})
('Login Test for user ', async t => {

    // test logic
});

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

  1. Launch a website which uses httpmethod
  2. provide credential which doesn't work and show that credentials pop-op again.
  3. Attached error is displayed and next test are not running.

TestCafe version

1.18.4

Node.js version

14.17.3

Command-line arguments

testcafe firefox .\tests\test.ts --skip-js-errors

Browser name(s) and version(s)

chrome 101.0.4951.41

Platform(s) and version(s)

No response

Other

No response

Thank you for submitting this issue. We would love to assist you and diagnose it. However, we need a simple sample that we can easily run on our side in order to replicate the issue and research its cause. Without a sample, we are not able to figure out what's going on and why this issue occurs. Refer to this article to create the best example: How To: Create a Minimal Working Example When You Submit an Issue. We look forward to your response.

This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.