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

Issue with TestCafe Test Step - Dropdown Menu Out of View in CI Pipeline #8049

Closed
asarraj opened this issue Oct 19, 2023 · 2 comments
Closed
Labels
STATE: Need clarification An issue lacks information for further research. TYPE: bug The described behavior is considered as wrong (bug).

Comments

@asarraj
Copy link

asarraj commented Oct 19, 2023

What is your Scenario?

I am encountering an issue with a specific test step in TestCafe. The problem arises when attempting to interact with a dropdown menu item during testing, especially in the context of a Continuous Integration (CI) pipeline.

Test Step: The problematic test step involves clicking a dropdown menu item using await t.click(element); with the appropriate selector.

CI Pipeline: This issue occurs when running the test suite within our CI pipeline. The problem doesn't manifest in local test runs.

I have tried using the .scroll() function in an attempt to bring the dropdown menu item into view, but this did not resolve the issue.

What is the Current behavior?

In the CI pipeline environment, the dropdown menu appears to be displayed on the right side of the page, but it extends beyond the viewable area of the page. As a result, the dropdown menu item becomes inaccessible and cannot be interacted with.

What is the Expected behavior?

The dropdown menu item should be displayed in the viewable area and should be clickable.

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

An example will follow.. Because the application is not public

What is your TestCafe test code?

Example test code will follow

Your complete configuration file

{
"src": ["hooks//*.ts", "utils//.ts", "steps/**/.ts", "tests//*.ts", "tests//*.feature"],
"screenshots": {
"path": "screenshots/",
"takeOnFails": true,
"fullPage": true,
"pathPattern": "${DATE}${TIME}/${TEST_ID}/${RUN_ID}/${USERAGENT}/${FILE_INDEX}.png"
},
"videoPath": "screenshots/",
"videoOptions": {
"failedOnly": true,
"singleFile": false,
"pathPattern": "${DATE}
${TIME}/${TEST_ID}/${RUN_ID}/${USERAGENT}/${FILE_INDEX}.mp4"
},
"compilerOptions": {
"typescript": {
"configPath": "tsconfig.json"
}
},
"debugOnFail": false
}

Your complete test report

No response

Screenshots

image

Steps to Reproduce

Example will follow

TestCafe version

3.2.0

Node.js version

No response

Command-line arguments

gherkin-testcafe --reporter factshub,xunit:report.xml --tags @wip -- --skip-js-errors "chrome:headless --lang=en_US --window-size='1920,1080'" --selector-timeout 20000 --assertion-timeout 5000 utils steps tests hooks

Browser name(s) and version(s)

chrome

@asarraj asarraj added the TYPE: bug The described behavior is considered as wrong (bug). label Oct 19, 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 Oct 19, 2023
@AlexKamaev AlexKamaev added the STATE: Need simple sample A simple sample is required to examine the issue. label Oct 20, 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 Oct 20, 2023
@github-actions
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Need clarification An issue lacks information for further research. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

2 participants