Event Proposals

6 proposals

1. Proposed

   API Contract Court: Break, Version, and Fix a Public API

   A role-played engineering trial where client teams expose why breaking changes hurt.

   Difficulty: Mixed Duration: 2 hours Target date: July 21, 2026 #api-design#contracts#testing
2. Proposed

   Dependency Upgrade Gauntlet: Patch a Critical Library Without Breaking Users

   Practice upgrading under risk using changelogs, tests, canaries, and rollback plans.

   Difficulty: Mixed Duration: 2 hours Target date: December 30, 2026 #dependencies#security#testing
3. Proposed

   Documentation Test Kitchen: Prove the Guide Works Before Publishing

   Treat documentation like software by testing setup guides, examples, and failure paths.

   Difficulty: Mixed Duration: 1 hour 30 minutes Target date: August 11, 2026 #developer-experience#documentation#testing
4. Proposed

   Flaky Test Court: Put Unreliable Tests on Trial With Evidence

   Separate product bugs from timing problems, test data leaks, order dependence, and bad assertions.

   Difficulty: Mixed Duration: 2 hours Target date: December 21, 2026 #flaky-tests#qa#testing
5. Proposed

   Permission Boundary Testing: Roles, Scopes, and Admin UI Access

   A practical two-hour session on Permission Boundary Testing, focused on Roles, Scopes, and Admin UI Access. Attendees work through concrete engineering tradeoffs, review examples, and leave with a checklist they can apply in real team projects.

   Difficulty: Intermediate Duration: 2 hours Target date: September 5, 2026 #authorization#security#testing
6. Proposed

   Spec to Test Matrix: Catch Ambiguity Before It Becomes a Bug

   Turn a fuzzy feature request into edge cases, acceptance tests, and reviewable behavior.

   Difficulty: Mixed Duration: 1 hour 30 minutes Target date: August 14, 2026 #product#requirements#testing