Public collection
The relationship between Exploratory Testing and Automated Tests
The relationship between Exploratory Testing and Automated Tests
Emily O'Connor
Principal Quality Engineer
She/Her
Automation-savvy QE with a sixth sense for bugs. Avid learner and reader interested in decoding dev-speak to enable engineering teams. I believe good software starts with user-focused problem solving.
More Collections
List of resources and some experiences on how a system can be tested for issues and quality.
A collection of terms that testers might hear from devs and other engineers
Take your exploratory testing skills to the next level with this curated list of essential and advanced content related to exploratory testing.
With servers in >250 cities around the world, check your site for localization problenms, broken GDPR banners, etc.
Manage your entire QA lifecycle in one place. Sync Jira, automate scripts, and use AI to accelerate your testing.
Get hands-on fast with guided setup, AI-assisted test creation, and CI-friendly execution.
Create E2E tests visually. Get clear, readable YAML you can actually maintain.
Collection FAQs
- What are Collections? They are a way to organize our software testing and QA content into an easily shareable format.
- Why create Collections? We all want to learn and often share what we are learning, creating a collection helps organise software testing knowledge into a comprehensible way.
- What can we add to Collections? At the moment you can add content that is created and hosted on Ministry of Testing.
- Who can add collections? Professional Members have the ability to create unlimited collections, privately or publicly.
