Chrome Web Store reviewers test extension functionality manually. If your extension requires authentication to demonstrate its core features, reviewers without working test credentials will mark the submission as "Unable to review" and reject it. This is one of the most common avoidable rejection causes for extensions that connect to external services. The chrome-cws-test-account policy is explicit: extensions requiring login must provide valid test credentials in the submission notes, not the public README where they could be abused.
High because missing test credentials for authenticated extensions causes reviewer rejection as "Unable to review," requiring resubmission and adding weeks to launch timeline.
Create a dedicated reviewer test account pre-loaded with sample data. Document it in a private file you'll paste into the Chrome Web Store submission notes — not your public README.
## Notes to Reviewer
This extension requires authentication. Use the following test account:
- Login URL: https://app.example.com/login
- Email: reviewer-test@example.com
- Password: [submitted via Developer Dashboard notes]
The test account includes pre-loaded sample data demonstrating all features.
Core tab management functionality is visible without login on the popup.
Keep the test account active for at least 30 days after submission. If credentials expire, re-login to reset them before the review window closes.
ID: extension-store-readiness.review-prep.test-account-credentials
Severity: high
What to look for: Count every authentication or login flow in the extension. Check if a README or documentation file includes a section titled "Test Account" or "Notes to Reviewer" with sample credentials (username/password) for testing the extension, if applicable. This is required if the extension connects to an external service or requires authentication.
Pass criteria: If the extension requires login/authentication to function, at least 1 set of test credentials (username and password, or a test account URL) are clearly documented for reviewers in the README or a dedicated file. If no authentication is required, this check passes automatically.
Fail criteria: The extension requires authentication but 0 test credentials are provided, or credentials are provided but are unclear or non-functional.
Skip (N/A) when: The extension does not require authentication or external service login to demonstrate core functionality.
Detail on fail: "Extension requires login but no test credentials provided in documentation" or "Test account URL provided is broken/404".
Remediation: Create a test account and document it clearly:
## Test Account for Reviewers
To test the full functionality of this extension, use these credentials:
- **URL:** https://example.com/auth
- **Username:** reviewer@example.com
- **Password:** [Provided separately to Chrome Web Store reviewers]
The test account has sample data pre-loaded for demonstration.
Provide credentials directly in your store submission notes, not in the public README.