End-to-End Page Tester FAQs

Question 1

How does it handle different local development ports?

Accepted Answer

The skill includes an intelligent port discovery workflow that automatically checks common ports like 3000, 5173, and 8000 if the primary application URL is not accessible.

Question 2

Can it test mobile and tablet layouts?

Accepted Answer

Yes, the skill systematically resizes the browser to multiple dimensions (Desktop 1920x1080, Tablet 768x1024, and Mobile 375x812) to ensure responsive design integrity.

Question 3

What specifically does it check for on each page?

Accepted Answer

It verifies that the page loads without 4xx/5xx errors, checks the browser console for JavaScript exceptions, ensures all CSS and JS assets are present, and confirms that key UI elements are visible.

Question 4

What happens if my application assets aren't built?

Accepted Answer

The skill includes a build verification step. If it detects missing files or unstyled content, it will prompt you to run build commands like 'npm run build' before continuing with the tests.

Question 5

Does this skill require a pre-existing test plan?

Accepted Answer

Yes, it typically reads from a plan file at tests/e2e-test-plan.md. If this file doesn't exist, it is recommended to run a test-plan generation skill first to map out your application routes.

End-to-End Page Tester

主要功能

使用场景

End-to-End Page Tester

主要功能

使用场景