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

Problem with starting mp4 player #8345

Open
JakubMaz opened this issue Nov 22, 2024 · 2 comments
Open

Problem with starting mp4 player #8345

JakubMaz opened this issue Nov 22, 2024 · 2 comments
Labels
STATE: Need response An issue that requires a response or attention from the team. TYPE: bug The described behavior is considered as wrong (bug).

Comments

@JakubMaz
Copy link

JakubMaz commented Nov 22, 2024

What is your Scenario?

I would like to run a player on the site that downloads mp4

What is the Current behavior?

Mp 4 downloads, but it takes a long time, much more than without testCafe.
This has resulted in the fact that it cannot be tested.
Normally the request requires ~100ms.
2024-11-22_09h47_52
With testcafe it takes ~25s.
2024-11-22_09h45_59

What is the Expected behavior?

Downloading mp4 through the player takes a normal amount of time

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

https://www.livereacting.com/tools/mp4-player

What is your TestCafe test code?

import { RequestLogger, Selector, t } from "testcafe";

const loggerMp4 = RequestLogger({ url: 'https://test-videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4', method: 'get' }, {
    logResponseHeaders: true,
    logResponseBody: true,
    logRequestHeaders: true,
    logRequestBody: true,
});

fixture`test player mp4`
    .page('https://www.livereacting.com/tools/mp4-player');

test('load player', async () => {
    await t.addRequestHooks(loggerMp4);
    await t.click(Selector('#play-button'));
    await t.expect(loggerMp4.contains(record => record.response.statusCode === 200)).ok({ timeout: 10_000 });
});

TestCafe version

3.7.0

Command-line arguments

testcafe chrome tests/test.js --disable-native-automation

Platform(s) and version(s)

chrome, edge

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

Hello @JakubMaz,

I couldn't reproduce the issue based on the scenario you described. The video takes slightly longer to load compared to running without TestCafe, but it's not as delayed as you mentioned.

Without Testcafe:
image
Testcafe Native Automation mode:
image
Testcafe Proxy mode:
image

Could you please clarify if you have tried running it in Native Automation mode? Additionally, could you share your operating system and Node.js version?

@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 Nov 28, 2024
@JakubMaz
Copy link
Author

@PavelMor25 I'm runing testcafe with flag --disable-native-automation. On Native Automation mode it works.
My system: Windows 11 Pro 22H2.
My node: 20.18.0

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

No branches or pull requests

2 participants