Q: How about elements not yet in viewport / requiring a click to become visible?

What about fullscreen or partial overalys with tabbed content within the overlay?

Apart from that: What actually will I do with the generated file?
If I code an e.g. react app or whatever kind of app, I got my files and tests.

Then, your website either is using very bad engllish or very bad translators or the combination of both. It really hard to guess what your messaging is but its clear you are prooud of your extension. But what does it actually do and how does it fit into any developer worlkflow (even your blog posts are so generic, they even don’t cover your own solution).

Honestly. Testing is great. Whatever gives me better testing I “auto love”. Please help explaining your solution & how it integrates into any real life dev workflow or CI/CD & Testing Framework.

BTW: Which testing framwork?

nl8PLUSAug 11, 2024
Founder Team
Xeedle

Xeedle

Aug 21, 2024

A: Hey there,
Currently, Xeedle does not fetch any elements that are hidden or not yet in the viewport. This includes elements requiring a click to become visible, as well as those within fullscreen or partial overlays with tabbed content.

Xeedle is designed to simplify the process of generating XPath selectors by automatically creating a page object file based on the tool and technology you select. This means you don’t need to manually find or define XPaths or selectors. Instead, you can directly integrate the generated page object file into your existing framework, provided it supports page objects. This can significantly speed up the development process and ensure consistency across your tests.

Helpful?
Log in to join the conversation