Power your agent
पब्लिशर का इंस्टॉल। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
रजिस्ट्री में अभी कोई पैकेज्ड रिलीज़ नहीं है। रिपॉज़िटरी का README देखें.
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चThe industry-leading, production-grade Playwright + TypeScript QE framework for UI, API, mobile, and AI testing at scale — with distributed Kubernetes execution, Claude vision-based assertions, interactive documentation, comprehensive example gallery, Docker containerization, GitHub Actions optimization, and complete observability via OpenTelemetry.
┌────────────────────────────────────────────────────────────────────────────┐
│ BestTester — Gold-Standard QA Platform │
├─────────┬─────────┬─────────┬─────────┬─────────┬─────────┬──────────┬────────┤
│UI Tests │API Tests│ Mobile │AI Tests │Security │ i18n │ File-Ops │ Perf │
│(PW) │(REST) │(Emulate)│(Claude) │(OWASP) │(Locale) │(xlsx/pdf)│(CWV) │
├────────────────────────────────────────────────────────────────────────────┤
│ Page Objects (src/pages/) │ API Clients (src/api/) │
│ Mobile Pages (src/mobile/) │ Security (src/security/) │
│ AI Integration (src/ai/) │ Data Builders (src/data/) │
│ Fixtures (src/fixtures/) │ i18n (src/i18n/) │
├────────────────────────────────────────────────────────────────────────────┤
│ AI: Claude Vision │ Semantic Matching │ Test Generation │ Seed Mgr │
│ Cleanup Registry │ Data Builders (Zod validated) │
├────────────────────────────────────────────────────────────────────────────┤
│ Execution: GitHub Actions (Optimized) │ Kubernetes (Distributed) │
│ Infrastructure: Docker (Multi-stage) │ Helm Charts │ Docker Compose │
├────────────────────────────────────────────────────────────────────────────┤
│ Reports: Allure │ Playwright HTML │ OTel Traces │ Jaeger │ Metrics │
│ Observability: OpenTelemetry Tracing │ Winston Structured Logging │
└────────────────────────────────────────────────────────────────────────────┘
# 1. Clone
git clone https://github.com/your-org/BestTester.git && cd BestTester
# 2. Install
npm ci
# 3. Configure
cp .env.example .env # edit with your credentials — NEVER commit .env
# 4. Install browsers
npm run setup
# 5. Run smoke tests
npm run test:smoke
BestTester/
├── .github/workflows/ # CI/CD: ci, smoke, docker-publish, docs deployment
├── config/ # Playwright configs, global setup, per-environment .env (dev/staging/prod)
├── docs/ # Interactive documentation (getting started, guides, examples)
│ ├── getting-started/ # quickstart, installation, first-test
│ ├── guides/ # architecture, test-writing, ai-testing, ci-cd, kubernetes
│ └── examples/ # linked to example gallery
├── examples/ # 26+ production-ready test patterns
│ ├── ui/ # form-validation, file-upload, interactions, responsive
│ ├── api/ # error-handling, authentication, pagination
│ ├── ai/ # vision-testing, semantic-similarity
│ ├── security/ # xss-prevention, csrf-protection, auth-bypass
│ └── README.md # example gallery with learning path
├── k8s/ # Kubernetes configuration
│ ├── job.yaml # Kubernetes Job manifest
│ ├── configmap.yaml # Non-secret configuration
│ ├── rbac.yaml # ServiceAccount, Role, RoleBinding
│ ├── secret.yaml.template # Secrets template (not committed)
│ ├── helm/ # Helm chart for deployment
│ │ ├── Chart.yaml
│ │ ├── values.yaml
│ │ └── templates/ # job, configmap, secret, pvc, rbac
│ └── DEPLOYMENT_GUIDE.md # Complete K8s deployment guide
├── scripts/ # Utility scripts
│ ├── k8s-run.ts # Kubernetes job runner with log streaming
│ ├── create-test.ts # Interactive test generation CLI
│ └── other scaffolding scripts
├── src/
│ ├── ai/ # Claude API integration, vision, semantic matching
│ ├── api/ # REST/GraphQL clients with Zod validation
│ ├── auth/ # Multi-role auth, storage state caching
│ ├── data/ # Fluent builders, seed manager, cleanup registry
│ ├── fixtures/ # Custom Playwright fixtures
│ ├── helpers/ # Wait helpers, formatters, utils
│ ├── observability/ # OpenTelemetry tracing, metrics
│ ├── page-objects/ # Page Object Model hierarchy
│ ├── mobile/ # Mobile page objects
│ ├── types/ # TypeScript interfaces
│ └── utils/ # Logger (Winston), file handlers, etc.
├── tests/ # Comprehensive test suites
│ ├── ui/ # UI tests (smoke, regression, visual, e2e)
│ ├── api/ # API tests with schema validation
│ ├── ai/ # AI/LLM tests
│ ├── security/ # Security/OWASP testing
│ ├── mobile/ # Mobile device emulation
│ ├── performance/ # Performance & Core Web Vitals
│ ├── a11y/ # Accessibility (WCAG 2.2 AA)
│ ├── data/ # Data management tests
│ └── flakiness/ # Flaky test detection & quarantine
├── Dockerfile # Multi-stage build with Playwright base
├── docker-compose.yml # Full stack: app, testsuite, allure, otel, jaeger
├── otel-collector-config.yml # OpenTelemetry collector configuration
├── package.json # 50+ npm scripts for all testing scenarios
└── README.md # This file
# All tests
npm test
# By type
npm run test:ui # UI tests
npm run test:api # API tests
npm run test:ai # AI/LLM tests
npm run test:mobile # Mobile device emulation tests
npm run test:file-ops # File operation tests
npm run test:security # Security tests
npm run test:i18n # Internationalization tests
npm run test:auth-matrix # Multi-role auth tests
npm run test:contracts # Consumer-driven contract tests (Pact)
npm run test:a11y # Accessibility tests (WCAG 2.2 AA)
npm run test:performance # Performance & Core Web Vitals tests
# By tag
npm run test:smoke # @smoke
npm run test:regression # @regression
npm run test:e2e # @e2e
npm run test:visual # @visual
npm run test:a11y # @a11y
npm run test:performance # @performance
# Debug modes
npm run test:headed # Headed browser
npm run test:debug # Playwright inspector
# Mutation testing
npm run test:mutation # Stryker mutation analysis
TEST_ENV=dev npm test
TEST_ENV=staging npm test
TEST_ENV=prod npm test
ALL_BROWSERS=true npm test # Chromium + Firefox + WebKit + mobile Chrome + mobile Safari
npm run test:mobile # Pixel 5 + iPhone 13
npm run test:mobile -- --project mobile-chrome # Android only
npm run test:mobile -- --project mobile-safari # iOS only
MOBILE_TABLET=true npm run test:mobile # Include iPad
npm run test:mobile -- --headed # Watch execution
Built on AWS Bedrock Converse API with Amazon Nova Pro as the default model. Supports chat, summarization, and embeddings (Titan Embed v2).
Multi-dimensional evaluation system with 6 built-in rubrics:
Scores across 6 dimensions: relevance, accuracy, coherence, safety, faithfulness, instruction adherence.
Anti-narcissistic bias: Primary model (Nova Pro) and judge model (Claude Haiku) use different architectures to prevent self-evaluation bias. Borderline scores (2–3) trigger automatic strict re-evaluation.
import { semanticExpect } from '@ai/semantic-assert';
await semanticExpect(response).toBeRelevantTo(prompt);
await semanticExpect(response).toBeGroundedIn(sourceContext);
await semanticExpect(response).toBeSafe();
await semanticExpect(response).toNotHallucinate(knownFacts);
await semanticExpect(response).toBeBetterThan(alternativeResponse);
await semanticExpect(response).toHaveScore({ min: 4.0, rubric: RUBRICS.CODE_GENERATION });
Model Context Protocol server for AI-driven test orchestration. Supports both stdio and SSE transports.
npm run mcp:server # stdio mode
npm run mcp:server:sse # SSE mode on port 3001
npm run mcp:generate # AI test generator client
Available MCP tools:
Test Generator Examples:
Generate a complete login test:
const result = await client.callTool('generate_test_from_description', {
description: 'User logs in with email and password, verifies dashboard appears'
});
// Returns TypeScript test file ready to run with npm run test:smoke
Generate a Page Object Model by analyzing a live page:
const pom = await client.callTool('generate_page_object', {
url: 'https://orangehrm-demo.com/web/index.php/auth/login'
});
// Returns class LoginPage with all selectors and helper methods
Generate API test suite from spec:
const apiTest = await client.callTool('generate_api_test', {
openapi_spec_url: 'https://api.example.com/v1/openapi.json'
});
// Returns complete test suite validating all endpoints and schemas
Identify test coverage gaps:
const gaps = await client.callTool('analyze_test_coverage', {
page_object_content: pomClassContent
});
// Returns array of missing test scenarios and accessibility checks
npm run agent:review -- --file tests/ui/login.spec.ts
npm run agent:review -- --file tests/ui/login.spec.ts --slack # post to Slack
Auto-detects broken locators in failed tests and suggests AI-powered fixes on a new git branch.
npm run agent:heal -- --test-result reports/playwright-report/results.json
Analyzes page objects + existing test coverage and generates 5–10 new test case suggestions.
npm run agent:suggest -- --page src/pages/employee.page.ts
npm run agent:jenkins -- --job playwright-tests --params ENV=staging
npm run agent:jenkins -- --job playwright-tests --build 42
npm run agent:jenkins -- --job playwright-tests --build 42 --logs
Auto-creates/updates/closes Jira bugs from test results. Attaches JUnit XML and links test executions.
npm run agent:jira -- --build latest
npm run agent:jira -- --junit reports/playwright-report/junit.xml --build 42
npm run agent:jira -- --junit reports/playwright-report/junit.xml --dry-run
Full workflow: trigger Jenkins → stream console → download artifacts → sync to Jira → notify Slack.
npm run agent:run-and-report
npm run agent:run-and-report -- --suite smoke --jira-key SCRUM-5
npm run agent:run-and-report -- --suite regression --jira-key SCRUM-5 --dry-run
npx ts-node agents/slack-bot-agent.ts --report reports/playwright-report/results.json
Consumer-driven contract testing using Pact to catch API breaking changes before they reach E2E tests.
Available contracts:
Running contract tests:
# Run all contracts
npm run test:contracts
# Run specific contract
npm run test:contracts -- --grep "Employee API Contract"
# Publish to Pact broker (CI only)
PACT_BROKER_URL=https://pact-broker.example.com npm run test:contracts
Pact configuration (pact.config.ts):
BestTester./pacts/Workflow:
Comprehensive WCAG 2.2 AA compliance testing using Axe and Playwright.
AccessibilityChecker features:
Running accessibility tests:
# Run all a11y tests
npm run test:a11y
# Run specific page accessibility
npm run test:a11y -- --grep "Login Page"
# Generate detailed report
npm run test:a11y -- --reporter=html
Usage in tests:
import { AccessibilityChecker } from '../../src/a11y/accessibility-checker';
const a11yChecker = new AccessibilityChecker();
// Check entire page (WCAG 2.2 AA)
const result = await a11yChecker.checkPage(page, {
standards: 'wcag22aa',
disableRules: ['skip-link'],
});
// Check specific component
const componentResult = await a11yChecker.checkComponent(page, '[role="main"]');
// Check color contrast only
const contrastIssues = await a11yChecker.checkColorContrast(page);
// Generate report
const report = a11yChecker.generateA11yReport(result.violations);
Supported standards:
Test coverage:
Core Web Vitals monitoring with configurable performance budgets.
Metrics collected:
Performance budgets by environment:
Running performance tests:
# Run all performance tests
npm run test:performance
# Run with custom environment
TEST_ENV=prod npm run test:performance
# Generate HTML performance report
npm run test:performance && open reports/performance-report.html
Usage in tests:
import { PerformanceCollector } from '../../src/performance/performance-collector';
import { PerformanceBudget } from '../../src/performance/performance-budget';
const collector = new PerformanceCollector();
const budget = new PerformanceBudget();
await page.goto(url);
await collector.waitForMetricsStability(page);
const metrics = await collector.collectMetrics(page);
const violations = budget.checkMetrics(metrics, 'prod');
expect(violations.filter(v => v.status === 'fail')).toHaveLength(0);
Historical trend tracking:
reports/performance-history.jsonPerformanceReporter.getTrendData(metric)Advanced visual regression with per-environment and per-browser baseline management.
Features:
Baseline organization:
reports/baselines/
├── login-page-dev-chromium.png
├── login-page-staging-chromium.png
├── login-page-prod-chromium.png
├── login-page-dev-firefox.png
├── metadata-dev-chromium.json
└── metadata-prod-chromium.json
Running visual tests:
# Run visual tests
npm run test:visual
# Update/regenerate baselines
npm run visual:update
# For specific environment
TEST_ENV=prod npm run test:visual
# For specific browser
BROWSER_NAME=firefox npm run test:visual
Usage in tests:
import { BaselineManager } from '../../src/visual/baseline-manager';
const baselineManager = new BaselineManager('prod', 'chromium');
// Save new baseline
await baselineManager.saveBaseline(page, 'login-page', 'Production login baseline');
// Load baseline (returns path if exists)
const baselinePath = baselineManager.loadBaseline('login-page');
// Update baseline metadata
baselineManager.updateBaseline('login-page', 'Updated description');
// List all baselines
const baselines = baselineManager.listBaselines();
// Get statistics
const stats = baselineManager.getStatistics();
// Returns: { totalBaselines, byEnvironment, byBrowser }
// Clean old baselines
const deleted = await baselineManager.clearOldBaselines(30); // days
Diff reporting:
Dedicated mobile test suite using Playwright device emulation against SauceDemo — a free, publicly available e-commerce demo app.
Device profiles:
Mobile page objects extend BaseMobilePage which provides:
swipe(direction, distance) — simulate touch swipe gesturestap(selector) — touch tap interactionisResponsive() — assert viewport is mobile-sized (<768px)getViewportSize() — retrieve current device dimensionsTest coverage:
import { Page } from '@playwright/test';
import { BaseMobilePage } from './base-mobile.page';
export class MobileCheckoutPage extends BaseMobilePage {
private readonly firstNameInput = this.page.locator('[data-test="firstName"]');
constructor(page: Page) { super(page); }
async fillName(name: string): Promise<void> { await this.firstNameInput.fill(name); }
}
Then register in src/fixtures/mobile.fixture.ts.
Jenkinsfile — full pipeline with parameterized suite selectionJenkinsfile.single-test — run a single test file remotelynpm run report:allure # Generate + open Allure report
npm run report:playwright # Open Playwright HTML report
Reports are generated in 4 formats: HTML, JSON, JUnit XML, and Allure. Allure is auto-published to GitHub Pages on nightly runs.
npm run scaffold:page -- --name MyFeature # → src/pages/my-feature.page.ts + test stub
npm run scaffold:test -- --name my-feature # → tests/ui/regression/my-feature.spec.ts
npm run scaffold:api -- --name my-resource # → src/api/my-resource.api.ts
import { Page } from '@playwright/test';
import { BasePage } from './base.page';
export class MyFeaturePage extends BasePage {
private readonly submitButton = this.page.getByRole('button', { name: 'Submit' });
constructor(page: Page) { super(page); }
async goto(): Promise<void> { await this.navigate('/my-feature'); }
async submit(): Promise<void> { await this.submitButton.click(); }
}
Then register in src/fixtures/base.fixture.ts.
Securely manage secrets via the 1Password CLI instead of storing them in .env.
op): https://developer.1password.com/docs/cli/get-startedOP_SERVICE_ACCOUNT_TOKEN in .envOnePassword utility in global-setup, fixtures, or scripts:import { OnePassword } from '@utils/one-password';
const op = new OnePassword('BestTester'); // vault name
// Inject all fields from a vault item into process.env
op.injectEnv('BestTester Secrets');
// Or map specific fields to env vars
op.injectEnv('BestTester Secrets', {
SLACK_BOT_TOKEN: 'Slack Bot Token',
JIRA_API_TOKEN: 'Jira API Token',
AWS_SECRET_ACCESS_KEY: 'AWS Secret Key',
});
// Create a new secret
op.createItem('API Credentials', { apiKey: 'sk-abc123' });
// Update an existing field
op.setField('BestTester Secrets', 'GitHub Token', 'ghp_new...');
See CONTRIBUTING.md for full guidelines.
git checkout -b feat/my-featurepage.waitForTimeout() — use Playwright auto-waiting@file, @description, @tagsnpm run lint && npm run typecheck && npm run test:smoke before opening a PRdevelopplaywright, typescript, test-automation, e2e-testing, api-testing, ai-testing, llm-testing, aws-bedrock, page-object-model, playwright-typescript, playwright-framework, playwright-boilerplate, playwright-template, test-framework, qa-automation, qe-framework, selenium-alternative, ui-testing, visual-regression, security-testing, owasp-zap, mutation-testing, stryker, allure-report, ci-cd, github-actions, jenkins, jira-integration, slack-bot, mcp, model-context-protocol, llm-as-judge, ai-assertions, semantic-testing, hallucination-detection, cross-browser-testing, i18n-testing, mobile-testing, device-emulation, responsive-testing, touch-testing, data-factory, test-data-management, download-verification, excel-testing, pdf-testing, playwright-best-practices, playwright-page-object, playwright-fixtures, playwright-ci-cd, playwright-ai, bedrock-testing, nova-pro, claude-haiku, titan-embeddings
Apache License 2.0 — see LICENSE for details.
You are free to use, modify, and distribute this framework in personal and commercial projects. Contributions are welcome and will be licensed under the same terms.
Production-grade Playwright + TypeScript QA framework with AI-powered testing, LLM-as-Judge evaluation, MCP server, 7 CLI agents, security fuzzing, CI/CD pipelines, Jira sync, and Slack reporting — ze
ओवरव्यू
Production-grade Playwright + TypeScript QA framework with AI-powered testing, LLM-as-Judge evaluation, MCP server, 7 CLI agents, security fuzzing, CI/CD pipelines, Jira sync, and Slack reporting — zero-config, plug-and-play.
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
BestTester stdio पर लोकल चलता है।
पिछली जाँच 2026-10-28 को हुई। Production-grade Playwright + TypeScript QA framework with AI-powered testing, LLM-as-Judge evaluation, MCP server, 7 CLI agents, security fuzzing, CI/CD pipelines, Jira sync, and Slack reporting — zero-config, plug-and-play.