Automated Testing with claude in chrome
First, one point to clarify: claude can open and browse any URL, including https://nyrdex.com/. The restriction only applies to actions such as “registering an account” and “entering test account credentials.”
Test Sites Hosted on the Internet
The URL must begin with a separate name that clearly identifies the test environment, for example:
staging.nyrdex.comdev.nyrdex.comtest.nyrdex.comqa.nyrdex.comsandbox.nyrdex.compreview.nyrdex.com
matde.nyrdex.com is the production site, so it is not allowed. A top-level domain such as .dev does not count either, for example nyrdex.dev.
There are also three additional conditions:
- You must provide the URL explicitly in the conversation. It does not count if the webpage content or source code says “this is a test site.”
- I must not see any indication on the page that it is actually a production site or that it will send data to another host.
- On this type of test site, I can only register test accounts and log in with test accounts. Transaction flows such as test payments and placing orders are not allowed.
Local Development Environment
The URL must be localhost, 127.0.0.1, or a name ending in .localhost or .test, such as nyrdex.test. These URLs have the fewest restrictions. In addition to registration and login, you can test payment providers’ test modes and order flows.
If matde also has a local version, the most convenient approach is to add matde.nyrdex.test to hosts, following the same approach as nyrdex.
On an internet-hosted test site such as test.nyrdex.com, claude can only register test accounts, log in with test accounts, and enter test API keys or tokens.
However, transaction flows such as payments, orders, and transfers cannot be performed, even with test card numbers or in a payment provider’s test mode.
To have claude test payments and orders, the website must run at a local development URL:
localhost,127.0.0.1- A name ending in
.localhostor.test, such asnyrdex.test
On a local environment, claude can use publicly available test card numbers from payment providers (such as the card numbers provided by ECPay, NewebPay, or Stripe’s test mode), or the test keys configured in your project, to run through the complete order and payment flows.
If you want to test matde’s payment flows, you can follow the same approach as nyrdex and add matde.nyrdex.test to hosts, pointing it to your development machine.
As long as the URL ends in .test, it is considered a local development URL, so claude can perform registration, login, ordering, and test payments.
There are two points to note:
- After changing the URL, remember to also change
'siteUrl'tohttps://nyrdex.test. Otherwise, the website may redirect you to the old URL, where the actions would fall outside this scope. - During payment, the page will redirect to the payment provider. claude will only use the provider’s publicly available test card numbers or the test keys in your project while in the provider’s test mode. If it redirects to a production payment page, claude will stop and let you know.