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

t.request() not working with proxyless #7523

Closed
BenDriesen opened this issue Feb 20, 2023 · 3 comments
Closed

t.request() not working with proxyless #7523

BenDriesen opened this issue Feb 20, 2023 · 3 comments
Labels
TYPE: bug The described behavior is considered as wrong (bug).

Comments

@BenDriesen
Copy link

BenDriesen commented Feb 20, 2023

What is your Scenario?

When sending api requests with the experimental proxyless feature, the test directly fails with a type error:

TypeError: Cannot read properties of null (reading 'proxy')

When proxyless is disabled, this works fine

What is the Current behavior?

Test fails with TypeError: Cannot read properties of null (reading 'proxy')

What is the Expected behavior?

API request is executed similarly as without proxyless

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

https://google.com

What is your TestCafe test code?

test('Request google page', async t => { const res = await t.request('https://google.com') })

Your complete configuration file

{ "experimentalProxyless": true }

Your complete test report

` ✖ Request google page

  1. TypeError: Cannot read properties of null (reading 'proxy')`

Steps to Reproduce

  1. Create a request with t.request() and execute the request without the proxyless setting enabled, the test runs fine
  2. Now run the same test with --experimental-proxyless. The test now fails with a type error

TestCafe version

2.3.1

Node.js version

19.0.1

Command-line arguments

testcafe chrome test.js --experimental-proxyless

Browser name(s) and version(s)

Chrome 109.0.0.0

Platform(s) and version(s)

macOS 10.15.7

@BenDriesen BenDriesen added the TYPE: bug The described behavior is considered as wrong (bug). label Feb 20, 2023
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Feb 20, 2023
@Artem-Babich Artem-Babich added the STATE: Need simple sample A simple sample is required to examine the issue. label Feb 21, 2023
@github-actions
Copy link

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 github-actions bot 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. STATE: Need simple sample A simple sample is required to examine the issue. labels Feb 21, 2023
@BenDriesen
Copy link
Author

@Artem-Babich, I've added an example

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Feb 21, 2023
@github-actions github-actions bot removed the STATE: Need clarification An issue lacks information for further research. label Feb 21, 2023
@miherlosev
Copy link
Contributor

Hi @BenDriesen,

Support for the t.request action was implemented in #7504.
This feature will be available in the next release.

@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 22, 2023
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

3 participants