Playwright Test Framework Example for AI & Playwright MCP Course by jaktestowac.pl

Created By
jaktestowaca year ago
This repository provides an empty Playwright test framework that was designed to test AI and Playwright MCP (Model Context Protocol) in course
Overview

What is Playwright Test Framework Example?

This project provides an empty Playwright test framework designed to test AI and Playwright MCP (Model Context Protocol) as part of a course offered by jaktestowac.pl.

How to use Playwright Test Framework Example?

To use this framework, clone the repository, install the necessary dependencies, and run the tests using npm commands. You can run all tests or specific test files as needed.

Key features of Playwright Test Framework Example?

  • UI Tests with Page Object Model for automated browser testing.
  • API Testing for end-to-end health checks and user interactions.
  • Custom fixtures and helpers for code reuse.
  • Test reporting and configuration options for various formats.

Use cases of Playwright Test Framework Example?

  1. Automating user registration and login processes.
  2. Testing article viewing functionality for both guest and logged-in users.
  3. Implementing API tests for backend services.

FAQ from Playwright Test Framework Example?

  • What prerequisites are needed to run the tests?

You need Node.js, the GAD application, and VSCode installed.

  • How do I run the tests?

Use the command npm run test to run all tests or specify a test file with npx playwright test tests/login.spec.ts.

  • What should I do if tests fail?

Ensure the GAD application is running and check your Node.js version.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jaktestowac
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago