Results for “testing”

Load this skill whenever you are planning, executing, or reviewing manual accessibility testing. Manual testing with real assistive technologies is essential — automated tools catch only ~30–40 % of WCAG issues. Absolutely always include keyboard-only testing and at least one screen reader test before marking a feature accessible. Under no circumstances skip forced colors mode testing for UI components.

The English summary is being prepared. Showing the original description.

This skill outlines methodologies for performing authorized penetration testing against AWS, Azure, and GCP cloud environments. It covers understanding the shared responsibility model for testing scope, leveraging cloud-specific attack tools like Pacu and ScoutSuite, exploiting IAM misconfigurations, testing for SSRF to cloud metadata services, and reporting findings aligned to MITRE ATT&CK Cloud matrix.

The English summary is being prepared. Showing the original description.

Uses Postman to perform structured API security testing by building collections that test for OWASP API Security Top 10 vulnerabilities including authentication bypass, authorization flaws, injection, and data exposure. The tester creates environments with multiple user roles, writes test scripts for automated security validation, and integrates Postman with OWASP ZAP and Newman for CI/CD security testing. Activates for requests involving Postman security testing, API security collection, aut...

The English summary is being prepared. Showing the original description.

bu skill outlines methodologies for performing authorized penetration testing against AWS, Azure, and GCP cloud environments. It covers understanding the shared responsibility model for testing scope, leveraging cloud-specific attack tools like Pacu and ScoutSuite, exploiting IAM misconfigurations, testing for SSRF to cloud metadata services, and reporting Bul:ings aligned to MITRE ATT&CK Cloud matrix.

The English summary is being prepared. Showing the original description.

This skill outlines methodologies for performing authorized penetration testing against AWS, Azure, and GCP cloud environments. It covers understanding the shared responsibility model for testing scope, leveraging cloud-specific attack tools like Pacu and ScoutSuite, exploiting IAM misconfigurations, testing for SSRF to cloud metadata services, and reporting findings aligned to MITRE ATT&CK Cloud matrix.

The English summary is being prepared. Showing the original description.

Write comprehensive end-to-end tests that verify complete user workflows, integration between components, and system behavior from user perspective using Playwright, Cypress, or similar frameworks. Use when testing user flows, verifying feature integration, testing across real browsers, ensuring UI interactions work correctly, validating form submissions end-to-end, testing authentication flows, catching regressions, automating QA processes, testing API integrations, or building confidence in production deployments.

The English summary is being prepared. Showing the original description.

End-to-end Coval adversarial / red-team testing workflow. Builds one adversarial test set (12 core attack vectors plus legitimate controls, each with an expected-behavior checklist), creates a persistent "Adversarial User" persona and a Composite Evaluation metric that scores each scenario against its own expected behaviors, launches a multi-iteration run against the agent (voice or chat), polls for completion, builds a per-scenario pass/fail scorecard, and creates a saved report grouped by Test Case. Use when a user wants to follow the Adversarial & Red-Team Testing cookbook (https://docs.coval.dev/guides/adversarial-red-team-testing) without doing each step by hand. Triggers: "adversarial test set", "red team my agent", "jailbreak / prompt-injection testing", "test my agent against bad actors".

The English summary is being prepared. Showing the original description.

Consumer-Driven Contract Testing (CDC) using Pact framework and OpenAPI-based contract validation. Covers microservice-to-microservice contract verification, provider contract testing, consumer contract testing, contract publishing pipelines, and contract breaking-change detection. USE WHEN: designing microservice APIs, establishing service boundaries, verifying service-to-service contract compatibility, integrating with Pact framework, preventing contract-breaking changes, or setting up a contract testing pipeline in CI/CD. Triggers on "contract test", "Pact", "consumer- driven contract", "CDC", "service contract", "API contract", "breaking change".

The English summary is being prepared. Showing the original description.

Specialized skill for testing FluentValidation validators. Use when you need to create tests for Validator classes, validate business rules, or test error messages. Covers complete FluentValidation.TestHelper usage, ShouldHaveValidationErrorFor, async validation, cross-field logic, etc. Keywords: validator, validation, fluentvalidation, validation testing, UserValidator, CreateOrderValidator, TestHelper, ShouldHaveValidationErrorFor, ShouldNotHaveValidationErrorFor, TestValidate, TestValidateAsync, testing validators, validating business rules

The English summary is being prepared. Showing the original description.

This skill outlines methodologies for performing authorized penetration testing against AWS, Azure, and GCP cloud environments. It covers understanding the shared responsibility model for testing scope, leveraging cloud-specific attack tools like Pacu and ScoutSuite, exploiting IAM misconfigurations, testing for SSRF to cloud metadata services, and reporting findings aligned to MITRE ATT&CK Cloud matrix.

The English summary is being prepared. Showing the original description.

Write and run Perl tests with Test2::V0 or Test::More, replace external dependencies with controlled test substitutes, and measure coverage—the code exercised by tests. Guidance covers test-first development, failure diagnosis, and migration between testing modules.

• Writing Perl tests before implementation
• Migrating tests from Test::More to Test2::V0
• Testing API and database interactions in isolation

Guides implementation of signup confirmations, password resets, and other application emails through Mailtrap. Covers API authentication, verified sending domains, separate testing environments that capture messages without delivery, and handling failed send requests.

• Adding signup confirmation emails
• Implementing password reset emails
• Testing emails without sending them to real inboxes

Write and organize F# unit and integration tests with xUnit, FsUnit, and Unquote. Use FsCheck to generate test inputs and check general rules, replace dependencies for isolated tests, and review test quality and coverage.

• Writing unit tests for F# code
• Checking general rules with generated inputs
• Testing ASP.NET Core API integration

Write Django and Django REST Framework tests with pytest-django, starting with tests before implementation. Covers test data generation, simulated external services, model and API checks, and coverage reports showing which code the tests exercise.

• Developing Django features by writing tests first
• Testing API authentication and input validation
• Generating reusable test data

Test local web applications with Playwright, a browser automation tool. Check frontend functionality, investigate interface behavior, capture screenshots, and inspect browser logs, with a helper script that manages one or more application servers during testing.

• Checking buttons and forms in a local web app
• Investigating interface problems with screenshots and logs
• Testing with both frontend and backend servers running

Guide Rust development through test-driven development: write a failing test, implement enough code to pass, then refactor. Includes practical test patterns and final checks for formatting, static analysis, and test results.

• Adding Rust features with tests first
• Reproducing bugs with failing tests before fixing them
• Testing invalid inputs and error paths

Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.

• Review accessibility coverage for shared components
• Add accessibility checks to page flow tests
• Run accessibility tests in CI

Support authorized penetration testing of AWS environments by examining IAM permissions and resources such as S3, EC2, and Lambda. It guides identifying privilege escalation paths, where access can be expanded, and documenting security audit findings.

• Review IAM permissions for privilege escalation paths
• Assess access to S3 buckets and Lambda functions
• Validate credential exposure risks through EC2 metadata

Design mock APIs, simulated services that reproduce expected responses, authentication, errors, and delays. Define scenarios and repeatable test data to support frontend development, integration testing, and realistic demos before the real backend is ready.

• Developing a frontend before the backend is ready
• Simulating a partner or third-party API
• Preparing a demo with realistic API responses

Assess REST and GraphQL API security through checks of authentication, access permissions, input validation, and request limits. The workflow guides endpoint discovery, testing, and documentation of findings and remediation within an authorized scope.

• Checking API authentication and token handling
• Testing access permissions across roles and tenants
• Reviewing request limits and input validation

Test Android app flows defined in XML by performing taps, swipes, and text entry, then checking screen states. Produce a JSON report with step results, commands, and failure reasons, stopping at the first failure.

• Verify login flows against an XML test specification
• Test product search and cart navigation
• Investigate UI failures on devices or emulators

Design backtests that evaluate trading strategies against historical data. Account for trading costs, avoid using future information or excluding delisted securities, and compare strategies using separate development and evaluation periods.

• Build a backtesting system for trading strategies
• Check for bias in historical performance estimates
• Compare strategies after accounting for trading costs

Build end-to-end tests with Playwright and Cypress to check complete user workflows, such as login and checkout. Improve test reliability through stable element selection, independent test data, appropriate waits, and debugging with traces and screenshots.

• Automate tests for login and checkout workflows
• Investigate tests that fail intermittently
• Run browser tests in CI/CD pipelines

Create GitHub Actions workflows to automate testing, builds, and deployments. Includes patterns for Docker image publishing, Kubernetes deployment, security scans, and testing across multiple environments, plus reusable workflows and approval steps for production releases.

• Automating tests for pushes and pull requests
• Building and publishing Docker images
• Deploying to Kubernetes with production approvals