Test automation
From the first command to a framework that holds up: project structure, locators, proper waiting, the Page Object pattern, test data, and running the full suite in CI/CD.
Service
Onsite Enterprise Training
Three days in one room, and a team that walks out capable.
An intensive, in-person workshop we bring to your offices — in test automation or agentic AI. A private workshop for your team alone, not a public class where you book a seat: the curriculum is designed once we know your engineers’ level and gaps, followed by three full days of hands-on work under direct supervision.
What a screen can’t replace.
Time that actually gets blocked
Self-paced learning needs a daily hour nobody protects between releases. A workshop books the three days upfront, so the learning happens because the calendar demands it.
Blockers solved on the spot
Someone learning alone can stall on the first error for an hour or a day. In the room we walk over to their screen, the blocker is gone in a minute, and they keep going.
One team, one standard
Five engineers learning alone come out with five different approaches. Three days together leaves them with one agreed way of working they carry forward.
Pick the workshop your team needs.
Agentic AI for engineers
How an agent is built and connected to your tools, how it’s grounded in your data with retrieval, how it’s evaluated before it’s trusted — and where an agent isn’t the right fit at all.
Every day ends with something that works.
- 01
Day one — foundations
We build the concepts and set up the environment on the team’s own machines; by the end of the day every engineer has run their first example successfully.
- 02
Day two — supervised practice
Progressive exercises designed for your team’s level. Each engineer writes them, we go screen to screen and correct in the moment — no watching, only writing.
- 03
Day three — enablement
Running in CI/CD, the standards the team leaves with, and a joint review of what was built — then a written plan for the next four weeks.
We come to you.
These are the countries we currently cover, and the list is growing. If you’re outside it, get in touch — we can most likely arrange it.
JordanSaudi ArabiaUAEKuwaitOmanBahrainQatarIraqEgyptMoroccoTunisiaAlgeria
Five steps from request to classroom.
- 01
You send a request
Tell us the track you’re interested in, the number of engineers, their current level, and the city we’ll come to.
- 02
We send the workshop plan
A written day-by-day plan built on your stack, not a ready-made template — with the price and what it includes.
- 03
We agree on dates
You pick the three days that fit the team’s schedule, and we lock them in the calendar.
- 04
Agreement and payment
A purchase order or contract plus a confirmation payment — that secures the dates and lets us arrange travel.
- 05
We start at your offices
We arrive a day early, set up the room and environments, and start on time on the morning of day one.
What stays with you after we leave.
The full workshop material
Slides, exercises, solutions, and the workshop repository — yours to keep and reuse when onboarding every new hire.
The complete workshop repository
Everything written over the three days in one tidy repository — a ready reference for the team and a foundation to build on.
A certificate for every engineer
A named certificate for each participant, suitable for their professional profile and your training records.
A month of follow-up
A direct question channel with your team for a month after the workshop, so adoption doesn’t stall at the first obstacle.
How many engineers, and where are you?
Send us the track, the city, and the number of participants, and we’ll come back with a workshop plan and a clear price.
Request a workshopBefore you ask.
How many engineers can a workshop take?
Six to twenty. Below six, the workshop loses the value of shared discussion; above twenty, it’s hard to get to every machine — and that hands-on round is the whole point.
What level do participants need?
We build the plan once we know their level. The automation track assumes familiarity with one programming language; the agentic AI track assumes a general engineering background, no prior AI experience. If the team is mixed, we split the exercises into two levels.
Do you cover travel costs, or do we?
Travel and accommodation are covered by the host, and both are stated clearly in the proposal before signing. No surprises after the workshop.
What do we need to prepare?
A room, a projector, internet, and the engineers’ machines with permission to install tools. We send the full setup checklist a week before the date.
What happens after the three days?
The workshop is a shared first push, not the whole journey. Most teams follow it with an enterprise subscription to the platform, so each engineer can continue at their own pace through the year — the two are usually booked together.
Can the workshop be remote?
Yes, but we recommend in person. The difference isn’t the explanation; it’s moving between machines and fixing the blocker on the engineer’s own screen — and a video call can’t replace that.
What if we want just two days, or five?
Three is the format we find works best, but it isn’t a requirement. Tell us the time you have and we’ll redistribute the plan around it, and be upfront about what gets cut.
Do you train students and universities too?
Yes. We offer the same format to universities and training centres, with different arrangements and pricing from enterprises — send us the institution’s details and the number of students.
What language is the workshop delivered in?
Arabic, with technical terms in English as they’re used at work. We also deliver it fully in English if the team is multinational.