sdet-software-development-engineer-in-test
Creates end-to-end tests, evaluates test coverage, identifies testing gaps, and builds test automation infrastructure. Focuses on test strategy, framework design, and ensuring comprehensive test coverage.
Discover blockchain testing skills, compare source repositories and read the instructions for each workflow.
Creates end-to-end tests, evaluates test coverage, identifies testing gaps, and builds test automation infrastructure. Focuses on test strategy, framework design, and ensuring comprehensive test coverage.
Create Behavior-Driven Development (BDD) feature files using Gherkin syntax. Write clear, executable specifications that describe system behavior from the user's perspective. Use for requirements documentation,...
Generate comprehensive async pytest tests for Quart endpoints, database operations, and WebSocket connections. Activates when writing tests or ensuring code coverage.
Design comprehensive test strategies with risk-informed prioritization (P0/P1/P2), test levels (unit/integration/E2E), mock strategies, and CI/CD integration. Creates Given-When-Then scenarios for all acceptanc...
Implements user stories by reading requirements, following coding standards, and executing tasks with comprehensive testing. Updates story files with implementation details and test results.
Guide to running and writing tests for Actions and Record Behaviors.
Defines unit testing standards for the Sigil project. Applies when writing tests, reviewing test code, creating fixtures or mocks, or answering questions about testing conventions. Covers test structure, fixtur...
Use when user says "執行 e2e 測試" or "run e2e tests" - run end-to-end tests with proper server setup
Execute one complete TDD cycle (tests first, then implementation)
Write tests for Python code with three tiers (Unit/Integration/E2E). Use when testing Python or writing Python tests.
Use when writing tests for Swift StateTree - ensures proper Swift Testing framework usage
Learn how to test code without mocking. Use when learning testing approach or before writing tests.
.NET test execution patterns and diagnostics. Use when running tests, analyzing test failures, or configuring test options.
Generate test PDF fixtures with known, extractable content. Creates PDFs with sections, tables, figures, requirements, equations, and annotations. Use when user needs "create test PDF", "generate PDF fixture",...
Write TypeScript code that's type-safe and tested. Use when coding TypeScript or implementing features.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure fir...
구현 전 테스트 케이스 설계 (TDD 준비). Use when (1) 구현 전 테스트 설계, (2) Acceptance Criteria 기반 테스트 케이스, (3) TDD 테스트 스켈레톤 생성.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Read all specs for a story, feature, or capability before starting work. Use when starting implementation to load requirements and context.
Execute Unity Test Runner via uloop CLI. Use when you need to: (1) Run unit tests (EditMode tests), (2) Run integration tests (PlayMode tests), (3) Verify code changes don't break existing functionality.
Write tests for TypeScript code with three tiers (Unit/Integration/E2E). Use when testing TypeScript or writing TypeScript tests.
Automatically applies when writing pytest tests. Ensures proper use of fixtures, parametrize, marks, mocking, async tests, and follows testing best practices.
Create and execute comprehensive testing strategies including unit tests, integration tests, test-driven development, and test coverage analysis. Use when writing tests, implementing TDD, checking test coverage...
Generates failing tests that reproduce reported bugs in FanHub. Use when a bug report comes in and you need to create a test that demonstrates the issue before fixing it. Follows FanHub's testing patterns and d...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.