nopcommerce-qa-mcp
MCP server for nopCommerce QA automation using Playwright. Enables running tests, viewing reports, analyzing failures, and generating QA dashboards.
README
🧪 nopCommerce QA Automation + MCP
A professional QA Automation project built with Playwright, TypeScript, Node.js, and Model Context Protocol (MCP) to automate end-to-end testing and provide structured QA reports, test history, failure analysis, and dashboards.
🚀 Project Overview
This project combines Playwright automation with an MCP server that allows QA tests to be executed and analyzed through dedicated automation tools.
Architecture
QA Engineer
│
▼
MCP Inspector
│
▼
MCP Server
│
├── Run Tests
├── Test Summary
├── Test Details
├── QA Report
├── Test History
├── Failure Analysis
└── QA Dashboard
│
▼
Playwright
│
▼
nopCommerce
🛠️ Tech Stack
- Playwright
- TypeScript
- Node.js
- MCP (Model Context Protocol)
- MCP Inspector
- JSON Test Reporting
- GitHub Actions
- End-to-End Testing
🧪 Automated Tests
The project currently contains 7 automated Playwright tests:
| # | Test | Status |
|---|---|---|
| 1 | Update product quantity in cart | ✅ Passed |
| 2 | Complete checkout after login | ✅ Passed |
| 3 | nopCommerce homepage loads successfully | ✅ Passed |
| 4 | Invalid login credentials | ✅ Passed |
| 5 | Customer logout | ✅ Passed |
| 6 | Add product to cart | ✅ Passed |
| 7 | Remove product from cart | ✅ Passed |
🤖 MCP QA Tools
The MCP server provides dedicated tools for interacting with the Playwright test suite:
run_tests— Run the complete Playwright test suitetest_summary— Display test names and statusestest_details— Display detailed information for a testqa_report— Generate a complete QA automation reporttest_history— Track previous test executionsfailure_analysis— Analyze failed and timed-out testsqa_dashboard— Display the latest QA dashboardrun_test— Run a specific Playwright testlist_tests— List available automated testsrun_all_and_dashboard— Execute all tests and generate a dashboardrun_failed_tests— Re-run failed testscompare_test_runs— Compare recorded test executions
📊 Latest Test Results
QA AUTOMATION DASHBOARD
Total Tests: 7
Passed: 7
Failed: 0
Skipped: 0
Flaky: 0
Pass Rate: 100%
Status: ALL TESTS PASSED
Execution Time: ~50 seconds
📁 Project Structure
nopcommerce-qa-mcp/
│
├── .github/
│ └── workflows/
│ └── playwright.yml
│
├── mcp/
│ └── server.ts
│
├── tests/
│ ├── cart.spec.ts
│ ├── checkout.spec.ts
│ ├── example.spec.ts
│ ├── login.spec.ts
│ ├── logout.spec.ts
│ ├── products.spec.ts
│ └── remove-from-cart.spec.ts
│
├── playwright.config.ts
├── package.json
├── package-lock.json
├── tsconfig.json
└── .gitignore
▶️ Run the Tests
Install dependencies:
npm install
Run all Playwright tests:
npx playwright test
Run tests with the line reporter:
npx playwright test --reporter=line
Run TypeScript validation:
npx tsc --noEmit
📋 Test Reporting
Playwright generates a JSON test report used by the MCP server for test analysis and dashboards.
The report contains:
- Test names
- Test files
- Pass/Fail status
- Execution duration
- Test output
- Errors
- Test execution timestamps
Generated test results are intentionally excluded from Git using .gitignore.
🔄 CI/CD
The project includes a GitHub Actions workflow for Playwright testing.
GitHub Push
│
▼
GitHub Actions
│
▼
Install Dependencies
│
▼
Run Playwright Tests
│
▼
Test Results
🎯 QA Capabilities
This project demonstrates practical experience with:
- End-to-End Testing
- UI Automation
- Test Automation Architecture
- Test Reporting
- Test Result Analysis
- Failure Analysis
- Test History Tracking
- Automated Regression Testing
- CI/CD Testing
- MCP-based QA tooling
🔐 Security
The project excludes sensitive and generated files such as:
node_modules/
test-results/
playwright-report/
.env
nopCommerce-develop/
👨💻 Author
Omar Aljerbi
QA Automation Engineer | Cloud & Automation
GitHub: https://github.com/Omar-Aljerbi
⭐ If you find this project useful, feel free to explore the repository.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。