-
Notifications
You must be signed in to change notification settings - Fork 675
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
Currently there are problems with opening the dropdown #7602
Comments
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. |
I encountered the same issue and created a minimal working example with the demos in the PrimeNg documentation. I ran the tests with testcafe 2.6.0 in Chrome 113.0.0.0 / Windows 11 with no special configuration. See this repo. Testcafe does not work properly with the basic dropdown in primeng versions 14 and 15, but does work correctly in primeng version 13. import { fixture, Selector } from 'testcafe';
fixture('primeng example');
test.page('https://www.primefaces.org/primeng-v15-lts/dropdown')('primeng v15 example', async (t) => {
const basicDropdown: Selector = Selector('dropdown-basic-demo p-dropdown');
const dropdownItems: Selector = basicDropdown.find('p-dropdownitem');
await t.click(basicDropdown);
await t.expect(dropdownItems.count).gt(0, 'No dropdown list items'); // fails
});
test.page('https://www.primefaces.org/primeng-v14-lts/dropdown')('primeng v14 example', async (t) => {
const header: Selector = Selector('h5').withExactText('Basic');
const basicDropdown: Selector = header.nextSibling('p-dropdown');
const dropdownItems: Selector = basicDropdown.find('p-dropdownitem');
await t.click(basicDropdown);
await t.expect(dropdownItems.count).gt(0, 'No dropdown list items'); // fails
});
test.page('https://www.primefaces.org/primeng-v13-lts/#/dropdown')('primeng v13 example', async (t) => {
const header: Selector = Selector('h5').withExactText('Basic');
const basicDropdown: Selector = header.nextSibling('p-dropdown');
const toggleExpandBtn: Selector = basicDropdown.find('div[role="button"]');
const dropdownItems: Selector = basicDropdown.find('p-dropdownitem');
await t.click(basicDropdown);
await t.expect(toggleExpandBtn.getAttribute('aria-expanded')).eql('true'); // passes
await t.expect(dropdownItems.count).gt(0, 'No dropdown list items'); // passes
}); |
In native automation mode the dropdown does work. See my example on github, branch Transitioning to native automation mode gives other issues in my test suite, e.g. no firefox support and issues with RequestMock and RequestLogger. |
Let's continue discussions in this thread. |
What is your Scenario?
after new angular 15 update testcafe not working properly with prime ng elements
p-multiselect.1.mp4
What are you suggesting?
previous versions of angular testcafe worked correctly, I think this process should be reviewed and to identify if testcafe has any problem with the https://primeng.org/ component with angular
What alternatives have you considered?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: