Build Test Automation Framework - Group Assignment

Instructor

0 reviews

Description
Curriculum
FAQ
Reviews

Short description

Most organisations don’t fail at test automation because they picked the wrong tool. They fail because the framework underneath the tests was never designed — it grew. The result is a suite that is slow, flaky, impossible to hand over and abandoned within a year.

Build Test Automation Framework is not a classroom course. It is a 9-week group assignment in which you build a complete test automation framework from scratch, in a small team, on your own technology stack. Week after week you work on a real framework, supported by a Brightest automation coach who shares the ins and outs, the tips and tricks, and above all the pitfalls we run into on client projects every day.

You start with an empty repository. You finish with a working, layered, CI-ready framework — and you defend it in a final presentation in front of your peers and your coach.

And the best part: the code is yours to keep. Many participants use the result as the starting point for the automation framework in their own project or company.

How it works

Intake & group composition (before the start) You tell us what you want to build and why. Based on your preferred technology, your context, your concrete need and your current level of knowledge, we compose groups of participants who are working towards a comparable goal. No mixed bags — the group is your peer group.
Build sprints (week 1 → 8) Each week has a theme, a set of framework decisions to make, and something concrete to deliver. Your group works on it between sessions; the coach reviews, challenges and unblocks. Expect code reviews, architecture discussions and honest feedback.
Guidance & follow-up (throughout) A dedicated Brightest coach follows your group for the full 9 weeks: recurring follow-up moments, review of your repository, and answers to the “how would you actually do this in practice?” questions that no tutorial covers.
Defence & final presentation (week 9) Your group presents and defends the framework: the architecture, the choices you made, the trade-offs you accepted and what you would do differently. You leave with feedback you can act on — and with your repository.

Quick info

Group assignment of ± 9 weeks, combining guided sessions with team work in between.
Advanced level: you build, we coach. This is not an introduction to programming or to a tool.
Your own stack: groups are formed around technology and context: C#, Java, TypeScript, Python, Selenium, Playwright, Cypress, Appium, REST, …
Real coaching, not a recording: continuous follow-up and code review by a Brightest automation expert.
Defence at the end: a final presentation of your framework to peers and coach.
You keep your code, ready to be used as a starting point in your own project or organization.
Eligible for the SME e-wallet / KMO-portefeuille

Who might want to attend this course?

Test automation engineers, SDETs and developers-in-test who need to set up a framework from the ground up — or who inherited one that has stopped scaling.
Teams that want to standardise their automation approach before it fragments across projects.
Participants who are proficient in at least one programming language (C#, Java, TypeScript, Python, …) and have hands-on experience with at least one automation tool.
Participants who can commit to the full 9 weeks and to working in a group — this track only delivers if you show up and build.

Not a fit if you are looking for an introduction to Selenium, Playwright, Appium or a programming language. Have a look at our course directory — we have dedicated courses for that.

Key takeaways

You can design and build a robust, layered test automation framework from scratch — and explain every choice you made.
You know the failure modes of test automation frameworks (flakiness, coupling, unmaintainable page objects, unreadable reporting) and how to design them away up front.
Your framework is CI/CD-ready and structured for handover to a team.
You have practised defending technical decisions to a critical audience — a skill that matters the moment you bring the framework back to your own organisation.
You take home a working repository that you may reuse as the starting point for your own project or company.

Kick-off, goals & group formation — context, constraints, target architecture and definition of done for your framework.

Framework foundations — project structure, dependency management, layering and separation of concerns.

Design patterns for automation — Page/Screen Object Model, factories, builders, fluent APIs and where patterns turn against you.

Configuration & test data management — environments, secrets, data builders, state and cleanup.

Stability & synchronisation — waiting strategies, retries, isolation, and the real causes of flaky tests.

The integration layer — API/REST testing, balancing your test portfolio and pushing checks down the trophy.

Readability & living documentation — BDD, Gherkin, custom DSLs: when they help and when they add cost.

Reporting, logging & CI/CD — pipeline integration, parallelisation, failure analysis and actionable results.

Hardening, review & defence — final code review, maintainability check and the group presentation.

What's the language of the course?

Coaching in Dutch or English, course materials in English.

When does the next group start?

There is no fixed calendar. We start a new group as soon as we have enough participants with a comparable technology and context — that is exactly what makes the coaching work. Register your interest and we'll come back to you with a start date, which we can discuss together to fit both calendars.

How much time should I plan per week?

Count on one Kick-Off session, a few follow-up sessions, and team work in between. Groups that invest the time will learn something and get a framework they can actually use; groups that don't, don't.

How are the groups composed?

Based on your intake: desired technology, context, concrete need and current knowledge level. We aim for groups that are working towards a comparable outcome so the coaching stays relevant for everyone.

Can I follow this with colleagues as a single team?

Yes. If you have enough participants, we can compose a group entirely from your own organisation and work on your own context.

Can I really use the code afterwards?

Yes — the framework your group builds is yours to keep and to reuse. Do plan time to refine and tailor it to your own environment; it is a solid foundation, not a finished product.

What if my technology isn't listed?

Mention it at intake. We regularly accommodate other stacks; some may require customisation.

Please, login to leave a review