e2e-test-automation

Execute phase-based E2E tests across Telegram bot workflows using MCP tools and gcloud CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill executes comprehensive end-to-end tests for Nikita using MCP tools and gcloud CLI to validate new implementations, ensure regressions are caught, and verify user journeys.

Core Features & Use Cases

  • Phase-based E2E tests across Telegram bot, Gmail OTP, Supabase DB, and Chrome portal
  • Scope-based testing (full, telegram, portal, otp)
  • Regression analysis with failure-mode references
  • Quickstart examples and documentation templates

Quick Start

After /implement completes, run this Skill with a scope (e.g., full, telegram, portal) to validate the end-to-end flow.

Frequently Asked Questions about e2e-test-automation

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

FAQPage Schema
How do I automate end-to-end testing for a Telegram bot and web portal?

End-to-end test automation validates complete user journeys across multiple services. This Skill executes comprehensive E2E tests for Nikita across Telegram bot, Gmail OTP flows, Supabase database, and Chrome portal using MCP tools and gcloud CLI, catching regressions and verifying implementations in one workflow.

Can I test Gmail OTP flows and Supabase database queries together in one test run?

Yes. This Skill supports phase-based testing that combines Gmail OTP verification, Supabase database checks, and Chrome portal validation in a single parameterized workflow, using parameterized SQL queries and MCP tool references for repeatable test runs.

What's the best way to set up E2E tests with Chrome DevTools and production log analysis?

Use phase-based E2E workflows that integrate Chrome DevTools portal testing with production log analysis. This Skill provides preflight prerequisites, scope-based testing (full, telegram, portal, otp), and structured MCP tool references to enable reportable test runs with failure-mode references.

Do I need gcloud CLI and MCP tools configured before running E2E tests?

Yes. This Skill requires gcloud CLI and MCP tool loading via MCPSearch as preflight prerequisites. After /implement completes, you run the Skill with a scope parameter (full, telegram, portal, or otp) to validate the end-to-end flow.

How do I catch regressions across Telegram, Gmail, and database layers in one test?

Regression analysis is built into phase-based E2E testing across Telegram bot, Gmail OTP, Supabase database, and Chrome portal. This Skill uses structured references to the MCP tool suite and failure-mode documentation to identify and report regressions in a single comprehensive test run.