> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/planning-and-decision-guides/choose-a-qa-conference.md).

# Choose a QA Conference

Select a QA conference, workshop, community event, or recording by role, operating problem, required takeaway, evidence access, budget, and follow-up capacity.

> **Editorial owner:** ContextQA Documentation · **Last updated:** September 12, 2026

## Quick answer

Choose an event format that can help answer a current operating question—not the conference with the longest agenda. Leaders usually need peer decision cases, practitioners need hands-on workshops, and evaluators need demonstrable workflows with accessible artifacts. The best event is one your team has time to convert into an owned experiment.

## Name the decision first

Examples:

* Which critical workflow should enter an AI testing pilot?
* How should we reduce flaky-test investigation time?
* What evidence must an agent-generated test carry?
* Should browser-grid replacement be full or incremental?
* Which role or tenant boundary is missing from regression?
* What team capability needs practice this quarter?

If the goal is only “learn what is new,” define what observable change would make the time worthwhile.

## Match format to need

| Need                 | Best event signal                                                    | Weak signal                             |
| -------------------- | -------------------------------------------------------------------- | --------------------------------------- |
| Leadership decision  | Practitioner case with constraints, ownership, and measured outcomes | Product vision without operating detail |
| Implementation skill | Hands-on workshop with prerequisites and take-home artifact          | High-level panel                        |
| Tool evaluation      | Live workflow, failure path, evidence, and Q\&A                      | Feature montage                         |
| Community benchmark  | Facilitated peer discussion with comparable contexts                 | Unstructured networking only            |
| Specialist depth     | Focused session and accessible technical material                    | Broad trend keynote                     |

## Score the candidate event

Use current organizer pages for dates, format, venue, recordings, and access. Those details can change.

| Criterion                                          | Weight | Score 0–3 | Evidence |
| -------------------------------------------------- | -----: | --------: | -------- |
| Agenda addresses the named decision                |      5 |           |          |
| Format permits the required depth                  |      4 |           |          |
| Speakers show relevant practitioner context        |      3 |           |          |
| Session artifacts or recordings will be accessible |      3 |           |          |
| Travel/time/budget fit                             |      3 |           |          |
| Team has an owner for follow-up                    |      5 |           |          |
| Accessibility and participation needs are met      |      4 |           |          |

Do not infer quality from sponsor count or attendance claims. Verify material details directly with the organizer.

## Current discovery starting points

As of September 12, 2026, the official [Ministry of Testing events directory](https://www.ministryoftesting.com/events) lists a mix of community, partner, and on-demand events. [Innovate QA](https://innovateqaevents.com/) describes its 2026 conference as completed with recordings available on demand. These are examples of discovery sources, not endorsements or a complete calendar. Recheck availability and terms when planning attendance.

## Set a follow-up contract

Before registering, assign:

```
Decision to inform:
Sessions or workshop selected:
Questions to ask:
Artifact to collect:
Person accountable for notes:
Experiment to propose:
Debrief date:
Budget and time boundary:
```

An event without follow-up capacity may be useful for community or professional development, but it should not be reported as a completed tooling evaluation.

## Frequently asked questions

### How do we choose between an in-person conference and an online event?

Choose the format that supports the required outcome. Use an in-person workshop when practice, peer discussion, or direct access matters; use an online session or recording when targeted knowledge, accessibility, schedule, and lower cost matter more.

### Can we rely on the dates and availability listed here?

No. Event schedules, venues, pricing, and recording access change. Treat the linked organizer pages as discovery starting points and verify the current details, cancellation terms, and accessibility provisions before spending budget.

### How do we turn conference attendance into measurable value?

Assign a question, note owner, artifact, experiment, and debrief date before registering. After the event, test one relevant claim against your own workflow and close ideas that have no owner or decision they can influence.

## Related documentation

* [Turn a Conference Demo into an Evaluation](/planning-and-decision-guides/conference-demo-to-evaluation.md)
* [AI Testing Vendor Demo Scorecard](/planning-and-decision-guides/ai-testing-vendor-demo-scorecard.md)
* [AI Testing Pilot Scorecard](/evaluation-and-governance/ai-testing-pilot-scorecard.md)
* [QA Skills for Agent-Assisted Teams](/planning-and-decision-guides/qa-skills-for-agent-assisted-teams.md)

{% hint style="info" %}
[**Turn one QA question into a scoped ContextQA evaluation →**](https://contextqa.com/book-a-demo/?utm_source=learning.contextqa.com\&utm_medium=referral\&utm_campaign=docs_demand_gen\&utm_content=choose_qa_conference) after using the event worksheet to define the workflow and evidence you need.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learning.contextqa.com/planning-and-decision-guides/choose-a-qa-conference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.