> For the complete documentation index, see [llms.txt](https://docs.does.qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.does.qa/guides.md). # Guides - [Working with Node Groups](https://docs.does.qa/guides/working-with-node-groups.md): Node Groups can help you maintain common steps across multiple flows. - [Test Tagging](https://docs.does.qa/guides/test-tagging.md): Tag and run specific test cases. - [Interacting With Emails](https://docs.does.qa/guides/interacting-with-emails.md) - [Avoiding Login Rate Limits](https://docs.does.qa/guides/avoiding-login-rate-limits.md): Reduce redundant logins and prevent authentication rate limits. - [Codeless vs Code](https://docs.does.qa/guides/codeless-vs-code.md): Discover why teams are switching from code-heavy frameworks to DoesQA. - [DoesQA Compared](https://docs.does.qa/guides/doesqa-compared.md): Compare Playwright, Cypress, and DoesQA for web automation testing. Compare features, capabilities and speed of the top 3 test automation solutions. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.does.qa/guides.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.