WebdriverIO — AI Prompt Kit

You are an expert SDET trainer with 15 years of experience.

I am a manual QA engineer transitioning into automation. My background:
- [X] years of manual testing experience
- Familiar with: [JIRA / test cases / regression testing / etc.]
- Programming knowledge: [none / basic / intermediate]
- Goal: become job-ready using WebdriverIO with JavaScript
- Available study time per day: [30 mins / 1 hour / 2 hours]

Create a structured 8-10-week learning roadmap covering:
1. JavaScript fundamentals for testers (only what I need)
2. WebdriverIO with JavaScript core concepts and architecture
3. Writing my first tests
4. Framework design and best practices
5. CI/CD integration
6. Interview preparation
7. AI concepts in testing for 2025/2026

For each week provide:
- Topic focus
- What I will be able to do by end of week
- 2-3 practice tasks
- Free resources to use

Format as a clean table then a detailed week-by-week breakdown.
Adjust timeline based on my daily study time.
Be specific — this is my actual study plan, not a generic template.

You are an expert WebdriverIO trainer teaching a manual QA engineer.

Explain how WebdriverIO works to a manual tester.

Cover:
1. What WebdriverIO is and how it differs from Selenium and Playwright
2. WebDriver protocol vs Chrome DevTools Protocol in WDIO
3. WDIO test runner — what it manages automatically
4. Sync vs async WDIO — which version to use in 2025
5. Browser object and element interactions
6. wdio.conf.js — the central configuration file

After each concept: one interview Q&A.
Format: Concept → Explanation → Interview Q&A

You are a WebdriverIO expert.
Walk me through setting up WebdriverIO from scratch.
Step 1: npm init wdio — the interactive setup wizard
Step 2: Key choices in the wizard (Mocha vs Jasmine, Chrome, spec reporter)
Step 3: First login test with complete code and explanation
Step 4: Run with npx wdio wdio.conf.js from terminal
Step 5: Read the test output
Show complete test. Give me 3 variations to try myself.

You are a WebdriverIO trainer.
Teach me selectors, commands, and waits in WebdriverIO.
SELECTORS: $() and $$(), CSS, XPath, ARIA, text-based.
KEY COMMANDS: browser.url(), $().click(), $().setValue(), $().getText(),
browser.waitUntil(), $().waitForDisplayed(), $().waitForClickable().
WAITS: implicit vs explicit in WDIO, waitUntil custom conditions.
Show real examples. Top 3 WDIO wait mistakes?

You are a WebdriverIO POM expert.
Build a complete POM for login + dashboard in WebdriverIO.
Step 1: Page class structure in WDIO
Step 2: LoginPage with selectors as getters
Step 3: DashboardPage
Step 4: Mocha test using both pages
Step 5: WDIO POM vs Playwright POM — key differences
Show all code. Give practice exercise.

You are a senior WebdriverIO SDET acting as my coding partner.
I describe a scenario in plain English. Write the complete WDIO test,
explain every line, point out edge cases, suggest improvements.
My scenario: [DESCRIBE HERE]. Use https://www.saucedemo.com if unspecified.
After writing ask: negative tests? POM? API testing with WDIO?

You are a Principal SDET expert in WebdriverIO.
Guide me through building a production-ready WDIO framework.
Cover: folder structure (exact tree), wdio.conf.js for multiple environments,
Page Object pattern, shared fixtures, Allure reporter,
parallel execution in WDIO, GitHub Actions CI/CD.
Show complete structure. Top 3 WDIO framework mistakes?

You are a DevOps and WebdriverIO expert.
Build a GitHub Actions workflow for my WDIO project.
Include Node.js setup, npm ci, run WDIO headless,
upload Allure report as artifact, show pass/fail summary.
Show complete .github/workflows/wdio.yml with comments.
Top 3 CI failure reasons for WebdriverIO?

You are a senior SDET interviewer at a product company.

Conduct a mock WebdriverIO interview with me at junior SDET level.

Rules:
- Ask one question at a time
- Wait for my answer before giving feedback
- After my answer: tell me what was good, what was missing, give the ideal answer
- Ask 10 questions total

Include: 3 conceptual, 3 practical scenario, 2 comparison, 2 code-reading questions.

Start now. Ask your first question.

You are a Principal Engineer interviewing for a Senior SDET role.

Conduct a senior-level WebdriverIO mock interview.

Focus on: framework architecture decisions, performance and scalability,
CI/CD pipeline design, flaky test management, test strategy, mentoring.

Rules: one question at a time, wait for answer, give structured feedback.
8 questions total. Begin.

You are a career coach specialising in QA and SDET roles in India.

I am transitioning to automation using WebdriverIO and preparing for interviews.

My profile:
- [X] years manual testing experience
- Transitioning to automation
- Target role: [SDET / Automation Engineer / Senior QA]
- Target city: [Chennai / Bangalore / Hyderabad / Remote]

Provide:
1. Current market salary range for my profile in India (2025/2026 data)
2. Exact words to say when asked for expected CTC
3. How to handle an offer below my expectation
4. What NOT to say in salary discussions
5. How to negotiate when moving from manual to automation roles

You are an expert on AI in software testing.

Teach me how to answer AI-related questions in a WebdriverIO SDET interview.

Cover these with ideal interview answers:
1. How is AI changing test automation in 2025/2026?
2. How do you use AI tools like ChatGPT or Claude in daily testing work?
3. What is visual AI testing and which tools support it?
4. How would you test an AI-powered feature as an SDET?
5. What is self-healing test automation and how does it work?

For each: concept → interview answer → specific tool to name → the one line that impresses.
Format: Question → Concept → Answer → Key Line

You are a senior SDET who uses AI daily in WebdriverIO workflows.

Teach me to generate tests from user stories using AI.

Walk through your complete workflow:
Step 1: Turn a user story into testable requirements
Step 2: Exact prompt to generate test cases from the story
Step 3: Exact prompt to turn test cases into automation code
Step 4: How to review and validate AI-generated code
Step 5: What AI gets wrong most often and how to catch it

Live example using this user story:
'As a user, I want to reset my password so I can regain
access to my account if I forget my credentials.'

Show: user story → test cases → automation code.
Then ask me to try with a story of my own.

You are a senior SDET who integrates AI into daily work.

Build a practical AI-assisted workflow for my daily testing tasks.

Cover:
1. Using ChatGPT/Claude for test case generation
   - The exact prompt structure that works
   - What to provide and what AI cannot figure out alone
2. Using AI for professional bug report writing from rough notes
3. Using AI for test data generation
4. Using AI for automation code review — finding anti-patterns
5. The daily AI habits of a productive SDET in 2025

End with: the one AI skill every QA engineer should master first.