Unexpected visibility check #30475
              
                Unanswered
              
          
                  
                    
                      nnaydenow
                    
                  
                
                  asked this question in
                Component Testing
              
            Replies: 0 comments
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm working on testing a piece of code, which you can view here: JSBin Example. The example includes web components and composition, where I aim to reuse a
popover-componentand display amenu-componentwith items. I've also implemented the same setup using native elements.When running tests with Cypress, I'm encountering unexpected behavior with the
"be.visible"assertion on these elements.Here's the code for testing the web components:
In this case, Cypress fails with an assertion error indicating that
popover-componentis not visible, even though the visibility assertion formenu-componentpasses.For comparison, here is the test code for the native elements:
In this test, Cypress fails with an assertion error stating that
.menu-componentis not visible.One difference between these tests is the element dimensions. In the first test,
menu-componenthas dimensions of0 x 18(width x height), whereas in the second test,.menu-componenthas dimensions of1000 x 0.I'm confused as to why the visibility assertion passes for the first test, as per Cypress Visibility Guidelines. Cypress documentation specifies that an element is considered hidden if it has a width or height of 0.
Am I missing something here?
Beta Was this translation helpful? Give feedback.
All reactions