writing-automation-tests

Write, register, debug, and run Selenium and Appium automation tests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mykaarma/claude-sutras --skill writing-automation-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-automation-tests
Source: https://github.com/mykaarma/claude-sutras/tree/main/skills/writing-automation-tests
Command: npx skills add https://github.com/mykaarma/claude-sutras --skill writing-automation-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reduces the time, friction, and errors involved in creating, registering, debugging, and running automation tests for the qa-automation / automationsuite codebase by providing conventions, templates, and operational run guidance.

Core Features & Use Cases

  • Create tests and page objects: guidance and templates for Selenium web tests and Appium mobile tests with recommended locator and package conventions.
  • Register and map tests: step-by-step instructions to insert tests into QAAutomationDB, assign Module and Platform mappings, and add stable tests to the Sanity suite.
  • Run and debug locally: instructions for local execution using a Selenium Hub, handling Jasypt decryption for properties, capturing screenshots on failure, and diagnosing flaky CI or environment-specific failures.
  • Use Case: scaffold a Login feature test, create its page object, register the test in QAAutomationDB, run it against a local Selenium Hub, and iterate on failures until stable.

Quick Start

Create a new Selenium web test for the Login feature, add a page object class, register the test in QAAutomationDB with the correct ModuleID, and run it locally to verify results.

Frequently Asked Questions about writing-automation-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write and register Selenium web tests in the qa-automation automationsuite?

Selenium web tests in the automationsuite are written using page object classes with recommended locator and package conventions, then registered in QAAutomationDB with Module and Platform mappings to enable local execution.

How do I register automation tests in QAAutomationDB with Module and Platform mappings?

Registering automation tests in QAAutomationDB requires inserting the test and assigning the correct ModuleID and Platform mappings, then adding stable tests to the Sanity suite to verify results against the local Selenium Hub.

Can I run Appium mobile tests locally using a Selenium Hub for the automationsuite?

Yes, you can run Appium mobile tests locally using a Selenium Hub, handling Jasypt decryption for properties and capturing screenshots on failure to iterate on test results until stable.

What conventions do I need to follow when creating page objects for automation tests?

Creating page objects requires following explicit wait conventions, correct package and locator placement, and screenshot-on-failure patterns to ensure tests run reliably in both local and CI environments.

Why do my local automation test runs fail without Jasypt decryption for properties?

Local automation test runs fail without Jasypt decryption because the automationsuite requires decrypting properties locally to properly connect to the Selenium Hub and execute tests against the configured environments.

How do I debug flaky automation test failures in CI and local environments?

Debugging flaky automation test failures involves diagnosing environment-specific issues, verifying Jasypt property decryption, checking explicit waits and locators, and using screenshot-on-failure outputs to iterate until stable.