DevExpress / testcafe

A Node.js tool to automate end-to-end web testing.
https://testcafe.io
MIT License
9.82k stars 670 forks source link

Testcafe adding Prefix to Authorisation Header #7475

Closed prasad21jan closed 1 year ago

prasad21jan commented 1 year ago

What is your Scenario?

We have SSO login page implementation. we are using chrome browser for running our application , we are getting TOKEN from XHR request and we are using this TOKEN in the next subsequent API request as authorisation token , But when website makes an XHR request testcafe is adding his own prefix content with that token.

Like :

:~TestCafe added this prefix to control the authorization flow ~ TOKEN_XXX

What is the Current behavior?

we are using a token as uri parameter to our website, But the website makes an XHR request test is adding prefix :~TestCafe added this prefix to control the authorization flow ~ TOKEN_XXX

because of that prefix, our request not authenticated and request got failed every time IMAG

What is the Expected behavior?

I belive this prefix shouldn't be added to this request. Is there any flag is present for avoid such type prefix content ?

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

import { Selector } from 'testcafe';

fixture Fixture .page('https://my_url');

test('test', async t => { await t .expect(Selector('h1').text).eql('Example Domain'); });

What is your TestCafe test code?

import { Selector } from 'testcafe';

fixture Fixture .page('https://my_url');

test('test', async t => { await t .expect(Selector('h1').text).eql('Example Domain'); });

Your complete configuration file

No response

Your complete test report

No response

Screenshots

IMAG

Steps to Reproduce

1. 2. 3.

TestCafe version

2.2.0

Node.js version

16.13.2

Command-line arguments

npm run testcafe chrome test/cases/*.test.js --experimental-proxyless

Browser name(s) and version(s)

chrome 108

Platform(s) and version(s)

windows 10

Other

No response

github-actions[bot] commented 1 year ago

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.

github-actions[bot] commented 1 year ago

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.