"Because 'It works on my machine' is not a valid test status."
Welcome to my flagship automation project! I engineered this suite to solve the three biggest headaches in QA: Tests that take too long, Reports that no one understands, and Bugs that disappear when you try to record them. I built this from the ground up to be a high-speed, BDD-driven engine that doesn't just "test"—it provides a full forensic audit of your application's health.
I believe every tool in a stack should serve a specific purpose for the team. Here is the engine under the hood:
| 🚀 Technology | 🎯 My "Why" (The Personality Behind the Choice) |
|---|---|
| .NET 10.0 | The latest and greatest. If it’s not .NET 10, is it even a modern framework? |
| ReqnRoll (BDD) | The "Translator." It turns "Given I am on the login page" into actual code, so the Product Owner can sleep at night. |
| Playwright | My chosen weapon. It’s like Selenium, but it actually respects your time and doesn't flake out for no reason. |
| MSTest (Parallelized) | I tuned this to run 16 scenarios at once. If your CPU fans aren't spinning, you're not testing hard enough. |
| ReportPortal & Docker | AI-powered dashboards because looking at raw console logs in 2026 is just masochism. |
| EF Core | To keep our database as clean as a whistle. No "ghost data" allowed here. |
I’ve designed this framework to act like a "Crime Scene Investigator." If a test fails, it leaves behind a trail of breadcrumbs so you can fix it in minutes, not hours:
- 📸 Automatic Screenshots: Captured at the exact moment of failure.
- 🕵️ Smart Traces: I configured Playwright to save full
.tracefiles only on failure. This gives you a play-by-play video of every click and network request without clogging up your storage. - 📊 Living Documentation: Human-readable reports that show the "Green vs. Red" status of actual business requirements.
- 📂 File Verification: If you're testing a "Download PDF" button, the framework actually catches the file and verifies its contents.
This project was a journey of many coffees and several "What have I done?" moments.
- The Honeymoon: I got ReqnRoll and Playwright to talk to each other. One test passed, and I felt like a god.
- The "Spaghetti" Incident: As I added more tests, the code got messy. I spent a week refactoring everything into SOLID principles and a clean Page Object Model. Now, the code is so clean you could eat off it.
- The Need for Speed: I implemented 16-worker parallelism. My computer briefly hovered off the desk, but the test suite now finishes in record time.
- AI Integration: Bringing in ReportPortal via Docker. Now, the framework uses AI to tell me if a failure is a real bug or just the environment being "moody."
If you've just joined the team, here is how you get this running before your first stand-up:
1. Don't Touch the Brain!
The test data lives in testdata.json. Update your credentials there, but do not change the structure unless you want to see me cry.
2. Choose Your Mode Open your terminal and run the helper script:
# Mode 1: The "I'm in a hurry" (Smoke tests)
.\run-tests.ps1 -Category "smoke"
# Mode 2: The "Warp Speed" (Full Parallel execution)
.\run-tests.ps1 -Parallel -Workers 16[Placeholder: A video of me explaining this framework while trying not to look at my own git commit messages from 2 AM]
Final Note: Whether you're a developer joining the team or a recruiter looking for an engineer who takes quality seriously—this is for you. Let’s build something that doesn't break!