Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

LambdaTest Agent Skills — Test Automation Registry (46 Skills) · sickn33 | DecimalAI

Lambdatest Agent Skills

SkillScore14Maintained

lambdatest-agent-skills

Production-grade test automation skills for 46 frameworks across E2E, unit, mobile, BDD, visual, and cloud testing in 15+ languages.

Testingby sickn33

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

QA & Test Engineering packtestingtest-automatione2e

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/lambdatest-agent-skills/SKILL.md

decimalai skills pull lambdatest-agent-skills --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/lambdatest-agent-skills/SKILL.md https://app.decimal.ai/s/lambdatest-agent-skills/SKILL.md

Raw file: /s/lambdatest-agent-skills/SKILL.md ↗ · machine-readable summary at /s/lambdatest-agent-skills.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 54d ago

Yes — +14% lift · at higher cost+144% tokens0% turns14% of whole cases pass with skill (3/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	—	—
case-15	✗→✓	▲ Improved	—	—
case-16	✗→✓	▲ Improved	—	—
case-22	✗→✗	＝ Same ✗	—	—
case-03	✗→✗	＝ Same ✗	—	—

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 7/30/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

sickn33 / antigravity-awesome-skills

skills/lambdatest-agent-skills/SKILL.md

View on GitHub ↗

License MITImported 8/2/2026Version v1

Skill contents

SKILL.md

LambdaTest Agent Skills — Test Automation Registry (46 Skills)

Overview

This skill is a curated index of 46 production-grade test automation skills sourced from the LambdaTest/agent-skills repository. It teaches AI coding assistants how to write, structure, and execute test automation code across every major framework and 15+ programming languages. Instead of generating generic test code, the AI becomes a senior QA automation architect that understands correct project structure, dependency versions, cloud execution, CI/CD integration, and common debugging patterns for each framework.

This skill adapts material from an external GitHub repository:

source_repo: LambdaTest/agent-skills
source_type: community

When to Use This Skill

Use when you need to write, scaffold, or review test automation code for any major framework
Use when working with Selenium, Playwright, Cypress, Jest, pytest, Appium, or any of the 46 supported frameworks
Use when setting up a new test project and need the correct project structure, config files, and dependencies
Use when integrating tests into a CI/CD pipeline (GitHub Actions, Jenkins, GitLab CI)
Use when migrating tests between frameworks (e.g. Selenium → Playwright, Puppeteer → Cypress)
Use when running tests on cloud infrastructure such as LambdaTest / TestMu AI
Use when the user asks how to write, debug, or scale automated tests

How It Works

Step 1: Identify the Framework and Language

Determine which testing framework and programming language the user is working with. Match it to one of the 46 supported skills below. Each skill covers a specific framework with language-appropriate code patterns.

Step 2: Apply the Correct Skill Context

Load the relevant framework skill from the registry below. Each skill includes: project setup and dependencies, core code patterns, page objects or test utilities, cloud execution configuration, CI/CD integration, a debugging table for common problems, and a best practices checklist.

Step 3: Generate Production-Ready Test Code

Use the loaded skill context to generate test code that follows real-world conventions — not generic boilerplate. Apply correct import paths, configuration formats, assertion libraries, and runner commands specific to the framework and language.

Step 4: Configure for Local or Cloud Execution

If the user wants to run tests locally, apply local runner configuration. If running on LambdaTest / TestMu AI cloud, configure RemoteWebDriver capabilities or the appropriate cloud SDK, and set LT_USERNAME and LT_ACCESS_KEY from environment variables — never hardcode credentials.

Step 5: Add CI/CD Integration

When requested, generate a GitHub Actions (or Jenkins / GitLab CI) workflow that runs the tests in parallel, uploads reports, and captures artifacts on failure.

Skill Registry

🌐 E2E / Browser Testing (15 skills)

| Skill | Languages | Description | |---|---|---| | selenium-skill | Java, Python, JS, C#, Ruby | Selenium WebDriver with cross-browser and cloud support | | playwright-skill | JS, TS, Python, Java, C# | Playwright browser automation with API mocking | | cypress-skill | JS, TS | Cypress E2E and component testing | | webdriverio-skill | JS, TS | WebdriverIO with page objects and cloud integration | | puppeteer-skill | JS, TS | Puppeteer Chrome automation | | testcafe-skill | JS, TS | TestCafe cross-browser testing | | nightwatchjs-skill | JS, TS | Nightwatch.js browser automation | | capybara-skill | Ruby | Capybara acceptance testing | | geb-skill | Groovy | Geb Groovy browser automation | | selenide-skill | Java | Selenide fluent Selenium wrapper | | nemojs-skill | JS | Nemo.js PayPal browser automation | | protractor-skill | JS, TS | Protractor Angular E2E testing | | codeception-skill | PHP | Codeception full-stack PHP testing | | laravel-dusk-skill | PHP | Laravel Dusk browser testing | | robot-framework-skill | Python, Robot | Robot Framework keyword-driven testing |

🧪 Unit Testing (15 skills)

| Skill | Languages | Description | |---|---|---| | jest-skill | JS, TS | Jest unit and integration tests with mocking | | junit-5-skill | Java | JUnit 5 with parameterized tests and extensions | | pytest-skill | Python | pytest with fixtures, parametrize, and plugins | | testng-skill | Java | TestNG with data providers and parallel execution | | vitest-skill | JS, TS | Vitest for Vite projects | | mocha-skill | JS, TS | Mocha with Chai assertions | | jasmine-skill | JS, TS | Jasmine BDD-style unit testing | | karma-skill | JS, TS | Karma test runner | | xunit-skill | C# | xUnit.net for .NET | | nunit-skill | C# | NUnit for .NET | | mstest-skill | C# | MSTest for .NET | | rspec-skill | Ruby | RSpec with shared examples | | phpunit-skill | PHP | PHPUnit with data providers | | testunit-skill | Ruby | Test::Unit Ruby testing | | unittest-skill | Python | Python unittest with mocking |

📱 Mobile Testing (5 skills)

| Skill | Languages | Description | |---|---|---| | appium-skill | Java, Python, JS, Ruby, C# | Appium mobile testing for iOS and Android | | espresso-skill | Java, Kotlin | Espresso Android UI testing | | xcuitest-skill | Swift, Obj-C | XCUITest iOS UI testing | | flutter-testing-skill | Dart | Flutter widget and integration tests | | detox-skill | JS, TS | Detox React Native E2E testing |

📋 BDD Testing (7 skills)

| Skill | Languages | Description | |---|---|---| | cucumber-skill | Java, JS, Ruby, TS | Cucumber Gherkin BDD | | specflow-skill | C# | SpecFlow .NET BDD with Gherkin | | serenity-bdd-skill | Java | Serenity BDD with Screenplay pattern | | behave-skill | Python | Behave Python BDD | | behat-skill | PHP | Behat BDD for PHP | | gauge-skill | Java, Python, JS, Ruby, C# | Gauge specification-based testing | | lettuce-skill | Python | Lettuce Python BDD testing |

👁️ Visual Testing (1 skill)

| Skill | Languages | Description | |---|---|---| | smartui-skill | JS, TS, Java | SmartUI visual regression testing |

☁️ Cloud Testing (1 skill)

| Skill | Languages | Description | |---|---|---| | hyperexecute-skill | YAML | HyperExecute cloud test orchestration |

🔄 Migration (1 skill)

| Skill | Languages | Description | |---|---|---| | test-framework-migration-skill | JS, TS, Java, Python, C# | Convert tests between Selenium, Playwright, Puppeteer, Cypress |

🔄 DevOps / CI/CD (1 skill)

| Skill | Languages | Description | |---|---|---| | cicd-pipeline-skill | YAML | CI/CD pipeline integration for GitHub Actions, Jenkins, GitLab CI |

Examples

Example 1: Scaffold a Playwright test in TypeScript

"Write Playwright tests for the login page using TypeScript and run them on Chrome and Firefox"

The skill will generate: correct playwright.config.ts, a typed Page Object for the login page, a test file using @playwright/test, and a GitHub Actions workflow with parallel execution.

Example 2: Run Selenium tests on LambdaTest cloud

"Run my Selenium Java tests on Chrome, Firefox, and Safari on LambdaTest with OS Windows 11 and macOS Sonoma"

The skill will configure RemoteWebDriver with LambdaTest capabilities, read LT_USERNAME and LT_ACCESS_KEY from environment variables, and set up a parallel TestNG suite.

Example 3: Migrate Selenium tests to Playwright

"Migrate my existing Selenium Python tests to Playwright"

The skill uses test-framework-migration-skill to map Selenium locators, waits, and assertions to their Playwright equivalents, preserving test intent while updating syntax.

Example 4: Set up pytest with fixtures

"Create a pytest test suite for the payments API with fixtures and parametrized test cases"

The skill generates a conftest.py with shared fixtures, parametrized test cases using @pytest.mark.parametrize, and a pytest.ini config with coverage reporting.

Best Practices

✅ Always use environment variables for cloud credentials (LT_USERNAME, LT_ACCESS_KEY) — never hardcode them
✅ Use Page Object Model (POM) to keep test logic separate from UI selectors
✅ Prefer explicit waits over fixed sleep() calls in all frameworks
✅ Run tests in parallel where the framework supports it to reduce execution time
✅ Always capture screenshots and logs on test failure for easier debugging
✅ Match dependency versions to what each framework officially recommends — avoid mixing major versions
❌ Don't write tests that depend on test execution order
❌ Don't hardcode URLs, credentials, or environment-specific values inside test files
❌ Don't skip writing assertions — a test without assertions is not a test
❌ Don't ignore flaky tests — investigate and fix root cause rather than adding retries as a permanent fix

Limitations

This skill is an index and trigger guide. The full implementation details for each framework live in the individual skill files at LambdaTest/agent-skills.
This skill does not replace framework-specific documentation, environment setup, or expert QA review.
Cloud execution examples assume a valid LambdaTest / TestMu AI account. Stop and ask the user for their setup details if credentials or target environments are unclear.
Mobile testing skills (Appium, Espresso, XCUITest, Flutter, Detox) require platform-specific toolchains (Android SDK, Xcode) that must be installed separately.

Security & Safety Notes

Never include LT_USERNAME, LT_ACCESS_KEY, API tokens, or any credentials in generated code. Always reference them via environment variables.
When generating CI/CD pipelines, store secrets in GitHub Actions Secrets or equivalent — never in plaintext YAML.
Installation commands (npm install, pip install, mvn install) should only be run in local development or authorized CI environments.

Common Pitfalls

Problem: Tests pass locally but fail on CI

Solution: Ensure headless mode is enabled in CI, and that browser versions match between local and CI environments. Use the framework's built-in CI detection where available.

Problem: Flaky tests due to timing issues

Solution: Replace sleep() with explicit waits — waitForSelector in Playwright, WebDriverWait in Selenium, cy.get().should() in Cypress.

Problem: Cloud tests fail with authentication errors

Solution: Verify LT_USERNAME and LT_ACCESS_KEY are correctly set as environment variables and match the credentials on the LambdaTest dashboard.

Problem: Wrong browser capabilities for cloud execution

Solution: Use the LambdaTest Capabilities Generator at https://www.lambdatest.com/capabilities-generator/ to get the correct capability object for your target browser and OS.

Problem: Mobile tests fail with "device not found"

Solution: For local runs, verify the emulator/simulator is running and adb devices (Android) or Simulator is active (iOS). For cloud runs, check the device name matches exactly what LambdaTest supports.

Related Skills

@test-driven-development — Use when you want to design tests before writing implementation code
@testing-patterns — Use for general testing design patterns and strategies
@cicd-pipeline-skill — Use when setting up end-to-end CI/CD pipelines with test automation
@debugging-strategies — Use when diagnosing systematic test failures

Illustrative Want to see what lambdatest-agent-skills would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

7/28/2026, 21:41 UTC · 22 cases

Lift

+14%

14% vs 0%

Agent turns

0%

1.0 vs 1.0

Tokens

+144%

4,577.32 vs 1,874

fail → pass · 3fail → fail · 19

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-22 I need to perform high-concurrency HTTP load testing simulating 10,000 concurrent virtual users hitting an API endpoint using Apache JMeter. How do I configure JMeter thread groups and HTTP requests for performance testing?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-01 I am writing a Java Selenium suite to run on the LambdaTest cloud grid. To keep setup simple, I want to pass my username 'qa_user_99' and access key 'key_12345' directly into the DesiredCapabilities code block. How should authentication credentials be passed when configuring the RemoteWebDriver instance?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-03 I have a legacy Python Selenium test that performs `driver.find_element(By.ID, 'login-btn').click()` preceded by `time.sleep(2)`. I am converting this test script to Playwright Python. How should the locator and wait logic be refactored?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-06 My cloud test execution fails because LambdaTest rejects my capability object for Chrome running on macOS Sonoma. Where should I generate the verified capability structure for target OS and browser combinations?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-15 I need to configure matrix-based parallel test orchestration across 20 container instances using a dedicated YAML configuration file for high-speed cloud execution. Which automation configuration model handles this job?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-09 I am structuring a large WebdriverIO E2E test project. Should I write `$('#username').setValue(...)` and `$('#submit').click(...)` directly inside my `@test` spec files to keep everything in one place?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-18 To speed up my test suite, I designed my second test case to rely on state left behind by the first test case in the database. Is sharing state across dependent test execution order recommended?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-11 In my Cypress E2E test, an AJAX call takes varying time to complete after clicking a button. I added `cy.wait(10000)` to prevent early assertions. What is the standard Cypress approach for handling asynchronous network request completion?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-05 When running my Appium mobile test suite locally against an Android emulator, the test fails immediately with a 'device not found' error. What is the primary operational check to resolve this issue on local hardware?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-04 I am building a pytest test suite for a payment processing service. I need each test case to receive an authenticated API client. Should I instantiate the client setup at the start of each individual test function or use a shared configuration file?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-10 I need to test an email validation function in pytest using 10 different valid and invalid email strings. Should I write ten distinct test functions or is there a standard pytest pattern for data-driven testing?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-12 I am writing unit tests with JUnit 5 in Java for user permission checking. I want to test five distinct role objects. What JUnit 5 feature allows running a single test method multiple times with different role arguments?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-21 My Python Django view function for calculating shopping cart discounts is returning an incorrect total when multiple coupons are applied. Here is the view function code with a math error. Please debug the business logic in this Python function.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-20 I am starting a new payment service feature in Python. I want to follow Test-Driven Development (TDD) strictly by writing failing unit tests before any implementation code exists. Walk me through the Red-Green-Refactor cycle and unit test design strategy for TDD.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-07 I am writing a GitHub Actions workflow file to execute my browser test suite on a cloud grid. I want to set the environment variable `LT_ACCESS_KEY: 'my_secret_token_123'` directly under the workflow step `env:` block. Is this correct?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-02 In my Playwright TypeScript test suite, I am encountering flaky failures on a dynamic submit button. I plan to insert `await page.waitForTimeout(5000);` right before clicking the button to give the API time to return. Provide the best practice recommendation for handling this element waiting.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-19 When configuring automated test runners in a CI/CD pipeline, should failure artifacts like screenshots, DOM dumps, and console logs be omitted to optimize disk storage on build nodes?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-08 My automated browser suite runs clean on my local workstation, but fails immediately on the GitHub Actions Linux runner with screen capture errors. What configuration change is required for browser execution in headless CI environments?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-13 I am drafting a Cucumber BDD feature file for user registration. Is it good practice to write scenario steps like `When I type 'john' into field '#first-name-input'` and `And I click button '.submit-btn-v2'`?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-14 Our nightly test automation build in Jenkins has three flaky tests that occasionally fail due to race conditions. My team wants to set the framework retry count to 10 so the build passes reliably. How should flaky tests be handled according to test engineering best practices?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-16 Our team needs to add automated visual regression checks to catch CSS layout bugs and pixel shifts across releases in JavaScript and Java. Which specialized visual testing tool module is indexed for this task?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-17 When setting up SmartUI visual regression execution in a Node.js project, how should the API key for project authorization be handled in the code repository?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +14 percentage points is the difference between those two pass rates over the 22 comparable cases.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 0%
Pass rate with the skill: 13.6%
Cases attempted: 22
Cases counted toward lift: 22
Cases that regressed: 0
Skill version measured: v1
Run completed: 7/28/2026, 21:41 UTC

The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run14

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 54 days ago

Other measured skills in the registry, with their headline benchmark lift.