From a63f4943156a84dff68eb0a16d76d71d2acdadc3 Mon Sep 17 00:00:00 2001 From: Jiri Spilka Date: Fri, 20 Mar 2026 09:59:14 +0100 Subject: [PATCH] Add E2E test prerequisites to CONTRIBUTING.md Document the build/link steps and OAuth profile setup needed to run E2E tests, so contributors don't have to discover these requirements from test failures. Co-Authored-By: Claude Opus 4.6 (1M context) --- CONTRIBUTING.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 7fc9ce3..2631d06 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -47,6 +47,27 @@ npm run test:e2e # Run e2e tests only npm run test:coverage # Run all tests with coverage ``` +### E2E test prerequisites + +E2E tests require `mcpc` to be built first: + +```bash +npm run build +npm link +``` + +Some E2E tests connect to a real remote MCP server and require OAuth authentication profiles. +Without these profiles, the affected tests will be skipped or fail. + +To set them up, [create a free Apify account](https://console.apify.com/sign-up) (you can use the same account for both profiles), then run: + +```bash +mcpc login mcp.apify.com --profile e2e-test1 +mcpc login mcp.apify.com --profile e2e-test2 +``` + +The test runner does not take any destructive actions. + ## Release process Use the release script to publish a new version