> For the complete documentation index, see [llms.txt](https://ultimatewebsolutions.gitbook.io/qa-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ultimatewebsolutions.gitbook.io/qa-knowledge-base/what-to-test-in-time-pressure.md).

# What to test in time pressure?

If I had limited time, I would use a risk-based approach rather than trying to execute the entire test suite.

First, I would identify what changed and what the highest-risk and highest-impact areas are. Then I would run a quick smoke test to make sure the environment and critical services are working.

After that, I would focus on the most important business-critical flows, high-risk functionality, negative and boundary cases, and targeted regression around the changed areas. If time allows, I would also perform some exploratory testing to look for unexpected issues.

I would communicate clearly what was tested, what was not tested, and what residual risks remain. The goal is to provide the best possible quality information within the available time.