[Meetup] AI skills for QA that get you hired: Solo task

Hello Team,
Solo Activity Submission – AI Testing Agents Orchestration

• 📁 Implementation Repository:
  End-to-end solution showcasing multi-agent orchestration (Playwright, API, BDD) with scalable design and CI-ready structure:
  👉 https://github.com/SriniCh1980/shiftsync-solo-activity/tree/main/SOLO_ACTIVITY
• 📊 Execution Results (Playwright Report):
  Detailed test execution report with UI validation insights and run metrics:
  👉 https://github.com/SriniCh1980/shiftsync-solo-activity/blob/main/SOLO_ACTIVITY/tests/playwright_test_results.html

Solo task submission.
I have added respective tests and now I am giving link to repo

https://github.com/aarti-kulkarni-5393/solo_task.git

I have uploaded all tests here

UI Tests:

API Tests:

 Agentic Playwright Test Suite with Live CI Report

Built a production-ready Playwright E2E test suite for the Employee Manager app, driven by a custom AI agent with a SKILL.md domain knowledge file that encodes application-specific selectors, reusable helpers, and known pitfalls.
 

✨ What was built:

45 tests across 4 spec files covering every user journey: authentication (all 3 users), employee CRUD with API seeding, real-time search, navigation & route guards
SKILL.md — a reusable domain knowledge capsule containing the full selector reference, loginAs/seed/clearAll helper patterns, and a pitfall table (e.g., MUI empty state always renders a row — you can never use toHaveCount(0))
100% pass rate — zero flakiness achieved by isolating each test with API seeding and scoping ambiguous selectors to dialogs

GitHub Actions CI — automated on every push, publishes Playwright HTML report to GitHub Pages
📊 Live report: https://gauravkhuraana.github.io/ActivityAI/solo/

🔗 Repository: https://github.com/gauravkhuraana/ActivityAI

Checkout the readme file 

Key architectural decisions:

1. API seeding (POST /employees) before each test — no UI setup, true test isolation
2. Scoped delete dialog button (dialog.getByRole('button', { name: 'Delete' })) — avoids row/dialog button ambiguity
3. Text-based empty state assertion (getByText('No employees found.')) — robust against MUI's always-present <TableRow>

Thanks to Tricentis for organizing such great events and inviting experts like Karthik and these challenges are icing on the cake

Thank you

Thank you everyone for participating in the challenge.

And special thanks to ​@executeautomation for hosting it.

And our winner is ​@gauravkhurana 🎉

Congratulations! I will reach out to you shortly to organize the prize!

Congratulations, Gaurav! wooho! 🎉

Thanks a lot ​@vgudipati . The comprehensive coverage screenshot that you added in report was impressive. Really liked your work