メニュー
End-to-end test automation using testRigor's plain English syntax for writing maintainable tests without coding, covering cross-browser testing, mobile testing, API validation, and integrations with CI/CD pipelines.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/PramodDutta/qaskills --skill testrigor-plain-english-testingコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when publishing SEO blog articles to qaskills.sh, e.g. "publish today's articles", "daily SEO batch", "write 10 articles from keyword research", "add a blog post", or any request that creates files under packages/web/src/app/blog/posts.
Generate test data from the schemas you already have. Read OpenAPI, JSON Schema, SQL DDL, or TypeScript models and produce deterministic factories, boundary and negative cases, relational datasets with valid foreign keys, cleanup scripts, and PII-safe synthetic data. Production records never leave the machine.
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.
SOC 職業分類に基づく
SKILL.md を表示中
| name | testRigor Plain-English Testing |
| description | End-to-end test automation using testRigor's plain English syntax for writing maintainable tests without coding, covering cross-browser testing, mobile testing, API validation, and integrations with CI/CD pipelines. |
| version | 1.0.0 |
| author | thetestingacademy |
| license | MIT |
| tags | ["testrigor","plain-english","no-code","codeless-testing","natural-language","cross-browser","mobile-testing","ai-testing","test-automation","low-code"] |
| testingTypes | ["e2e","integration","api","mobile","accessibility"] |
| frameworks | ["testrigor"] |
| languages | ["typescript","javascript"] |
| domains | ["web","mobile","api"] |
| agents | ["claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp"] |
You are an expert in testRigor, the AI-powered plain-English test automation platform. When the user asks you to create tests using natural language, build codeless test suites with testRigor, integrate testRigor with CI/CD, or migrate from coded automation to plain-English tests, follow these detailed instructions.
testrigor-tests/
test-suites/
smoke/
login-smoke.md
navigation-smoke.md
search-smoke.md
regression/
auth/
login-tests.md
registration-tests.md
password-management.md
checkout/
cart-operations.md
payment-flow.md
order-management.md
user-profile/
profile-update.md
preferences.md
api/
user-api-tests.md
product-api-tests.md
mobile/
mobile-login.md
mobile-checkout.md
reusable-rules/
login-as-admin.md
login-as-user.md
add-product-to-cart.md
navigate-to-checkout.md
cleanup-test-data.md
data/
test-users.md
product-catalog.md
config/
environments.md
integrations.md
scripts/
testrigor-api-client.ts
ci-trigger.ts
result-parser.ts
<!-- test-suites/smoke/login-smoke.md -->
# Login Smoke Tests
## Test: Successful login with valid email and password
navigate to "login"
enter "testuser@example.com" into "Email"
enter stored value "userPassword" into "Password"
click "Sign In"
check that page contains "Welcome back"
check that url contains "/dashboard"
navigate to "login"
enter "testuser@example.com" into "Email"
enter "WrongPassword123" into "Password"
click "Sign In"
check that page contains "Invalid credentials"
check that url contains "/login"
navigate to "login"
click "Sign In"
check that page contains "Email is required"
check that page contains "Password is required"
navigate to "login"
enter "TestPassword" into "Password"
check that "Password" has attribute "type" with value "password"
navigate to "login"
click "Forgot password?"
check that url contains "/reset-password"
check that page contains "Reset your password"
<!-- test-suites/regression/checkout/cart-operations.md -->
# Cart Operations Tests
## Test: Add single product to cart and verify
navigate to "products"
click on "Wireless Headphones"
check that page contains "Wireless Headphones"
click "Add to Cart"
check that notification contains "Added to cart"
click on the cart icon
check that page contains "Wireless Headphones"
check that page contains "1" in the quantity field
save the value of "Total" as "cartTotal"
## Test: Update product quantity in cart
navigate to "products"
click on "Wireless Headphones"
click "Add to Cart"
click on the cart icon
clear the "Quantity" field
enter "3" into "Quantity"
click "Update"
check that the value of "Subtotal" is greater than stored value "cartTotal"
## Test: Remove product from cart
navigate to "products"
click on "Wireless Headphones"
click "Add to Cart"
click on the cart icon
click "Remove" for "Wireless Headphones"
check that page contains "Your cart is empty"
## Test: Cart persists after page refresh
navigate to "products"
click on "Wireless Headphones"
click "Add to Cart"
refresh the page
click on the cart icon
check that page contains "Wireless Headphones"
## Test: Apply discount code
navigate to "products"
click on "Wireless Headphones"
click "Add to Cart"
click on the cart icon
enter "SAVE10" into "Discount Code"
click "Apply"
check that page contains "Discount applied"
check that page contains "-10%"
<!-- reusable-rules/login-as-admin.md -->
# Rule: login as admin
navigate to "login"
enter stored value "adminEmail" into "Email"
enter stored value "adminPassword" into "Password"
click "Sign In"
check that page contains "Admin Dashboard"
<!-- reusable-rules/add-product-to-cart.md -->
# Rule: add product "productName" to cart
navigate to "products"
click on the value of "productName"
click "Add to Cart"
check that notification contains "Added to cart"
<!-- reusable-rules/navigate-to-checkout.md -->
# Rule: navigate to checkout
click on the cart icon
check that the cart is not empty
click "Proceed to Checkout"
check that url contains "/checkout"
<!-- test-suites/api/user-api-tests.md -->
# User API Tests
## Test: Create a new user via API
call api "POST" on "https://api.example.com/users" with headers "Content-Type:application/json" and body:
{
"name": "Test User",
"email": "generated email",
"role": "user"
}
check that api response status is "201"
check that api response contains "id"
save api response field "id" as "newUserId"
## Test: Get user details via API
call api "GET" on "https://api.example.com/users/${stored value 'newUserId'}" with headers "Authorization:Bearer ${stored value 'apiToken'}"
check that api response status is "200"
check that api response field "name" equals "Test User"
check that api response field "email" contains "@"
## Test: Update user via API
call api "PUT" on "https://api.example.com/users/${stored value 'newUserId'}" with headers "Content-Type:application/json,Authorization:Bearer ${stored value 'apiToken'}" and body:
{
"name": "Updated User"
}
check that api response status is "200"
check that api response field "name" equals "Updated User"
## Test: Delete user via API
call api "DELETE" on "https://api.example.com/users/${stored value 'newUserId'}" with headers "Authorization:Bearer ${stored value 'apiToken'}"
check that api response status is "204"
## Test: API returns 404 for non-existent user
call api "GET" on "https://api.example.com/users/nonexistent-id" with headers "Authorization:Bearer ${stored value 'apiToken'}"
check that api response status is "404"
// scripts/testrigor-api-client.ts
interface TestRigorConfig {
apiToken: string;
testSuiteId: string;
baseUrl?: string;
}
interface TestRun {
id: string;
status: 'running' | 'passed' | 'failed' | 'cancelled';
totalTests: number;
passedTests: number;
failedTests: number;
startTime: string;
endTime?: string;
url: string;
}
export class TestRigorClient {
private baseUrl: string;
private headers: Record<string, string>;
private testSuiteId: string;
constructor(config: TestRigorConfig) {
this.baseUrl = config.baseUrl || 'https://api.testrigor.com/api/v1';
this.testSuiteId = config.testSuiteId;
this.headers = {
'Content-Type': 'application/json',
'auth-token': config.apiToken,
};
}
async triggerTestRun(options?: {
labels?: string[];
environment?: string;
browser?: string;
}): Promise<string> {
const response = await fetch(
`${this.baseUrl}/apps/${this.testSuiteId}/retest`,
{
method: 'POST',
headers: this.headers,
body: JSON.stringify({
labels: options?.labels,
environment: options?.environment,
browser: options?.browser || 'chrome',
}),
}
);
if (!response.ok) {
throw new Error(`testRigor API error: ${response.status}`);
}
const result = await response.json();
return result.testRunId;
}
async getTestRunStatus(runId: string): Promise<TestRun> {
const response = await fetch(
`${this.baseUrl}/apps/${this.testSuiteId}/testRuns/${runId}`,
{ headers: this.headers }
);
if (!response.ok) {
throw new Error(`testRigor API error: ${response.status}`);
}
return response.json();
}
async waitForCompletion(runId: string, timeoutMs = 1800000): Promise<TestRun> {
const startTime = Date.now();
while (Date.now() - startTime < timeoutMs) {
const status = await this.getTestRunStatus(runId);
if (status.status === 'passed' || status.status === 'failed') {
return status;
}
await new Promise((resolve) => setTimeout(resolve, 15000));
}
throw new Error('Test run timed out');
}
}
# .github/workflows/testrigor-tests.yml
name: testRigor Tests
on:
push:
branches: [main]
pull_request:
jobs:
testrigor:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: 20
- name: Trigger testRigor Tests
env:
TESTRIGOR_TOKEN: ${{ secrets.TESTRIGOR_TOKEN }}
TESTRIGOR_SUITE_ID: ${{ vars.TESTRIGOR_SUITE_ID }}
run: npx tsx scripts/ci-trigger.ts
- name: Upload Results
if: always()
uses: actions/upload-artifact@v4
with:
name: testrigor-results
path: test-results/
<!-- test-suites/mobile/mobile-login.md -->
# Mobile Login Tests
## Test: Mobile login with email
open app "com.example.app"
tap "Sign In"
enter "user@example.com" into "Email"
enter stored value "password" into "Password"
tap "Log In"
check that screen contains "Welcome"
## Test: Biometric login prompt
open app "com.example.app"
tap "Sign In"
check that "Use Face ID" button is visible
tap "Use Face ID"
confirm biometric authentication
check that screen contains "Dashboard"
## Test: Mobile form validation
open app "com.example.app"
tap "Sign In"
tap "Log In" without filling fields
check that screen contains "Email is required"
## Test: Landscape orientation login
rotate device to landscape
open app "com.example.app"
tap "Sign In"
enter "user@example.com" into "Email"
enter "Password123" into "Password"
tap "Log In"
check that screen contains "Welcome"
rotate device to portrait
<!-- data/test-users.md -->
# Test Data Configuration
## Stored Values Setup
save value "testuser@example.com" as "userEmail"
save value "SecurePass123!" as "userPassword"
save value "admin@example.com" as "adminEmail"
save value "AdminPass456!" as "adminPassword"
## Generated Data Examples
# In test steps, use these generators:
# generated email -> produces unique email like test_a1b2c3@testrigor.com
# generated name -> produces random full name
# generated phone -> produces random phone number
# generated number between 1 and 100 -> random integer
## Using Variables in Tests
save value "generated email" as "newUserEmail"
enter stored value "newUserEmail" into "Email"
save the value of "Order ID" as "orderId"
check that the value of "Confirmation" contains stored value "orderId"
<!-- test-suites/regression/conditional-tests.md -->
# Conditional Test Scenarios
## Test: Handle optional modal
navigate to "home"
if page contains "Cookie Consent" then click "Accept All"
check that page contains "Welcome"
## Test: Different flows based on user type
navigate to "dashboard"
if page contains "Admin Panel" then
click "Admin Panel"
check that page contains "User Management"
else
check that page contains "My Account"
end if
## Test: Retry until element appears
navigate to "processing"
repeat up to 10 times
if page contains "Processing Complete" then exit loop
wait 2 seconds
end repeat
check that page contains "Processing Complete"
<!-- config/integrations.md -->
# testRigor Integrations
## Jira Integration
# testRigor automatically creates Jira tickets for failed tests when configured:
# - Project: QA
# - Issue Type: Bug
# - Priority: Based on test priority label
# - Description: Includes test steps, screenshots, and environment details
# - Assignee: Based on component mapping
## Slack Notifications
# Configure channels per test suite:
# - #qa-critical -> critical test failures
# - #qa-nightly -> nightly regression results
# - #qa-smoke -> smoke test results
## CI/CD Webhooks
# Trigger test runs via webhook:
# POST https://api.testrigor.com/api/v1/apps/{suiteId}/retest
# Headers: auth-token: {API_TOKEN}
# Body: {"labels": ["smoke"], "browser": "chrome"}
<!-- Organizing large test suites -->
# Label Strategy
# Use hierarchical labels for organization:
# Priority: p0-critical, p1-high, p2-medium, p3-low
# Type: smoke, regression, sanity, exploratory
# Feature: auth, checkout, search, profile, admin
# Platform: web, mobile-ios, mobile-android, tablet
# Running specific subsets:
# CI on commit: labels "smoke" AND "p0-critical"
# CI on merge: labels "regression" AND ("p0-critical" OR "p1-high")
# Nightly: labels "regression"
# Weekly: all tests
# Naming Convention
# Test names should be: [Feature] - [Scenario] - [Condition]
# Example: "Auth - Login - Valid credentials"
# Example: "Checkout - Payment - Expired card"
# Example: "Search - Filter - Multiple categories"
When scaling testRigor test suites beyond 500 tests, consider organizing tests into focused suites of 50-100 tests each. Use labels extensively to enable selective execution. Schedule full regression runs during off-peak hours. Monitor test execution time trends and investigate tests that gradually slow down.
For large teams, establish ownership of test suites by feature area. Each team owns their feature's tests and is responsible for maintenance. Use testRigor's built-in analytics to identify which teams have the most flaky or failing tests.
When integrating with multiple environments, create environment-specific configurations that include the base URL, API endpoints, feature flags, and test user credentials. Use testRigor's environment selector to run the same tests against different environments without duplicating test definitions.