# Websites

A website platform is checked in Chrome, both while you record and when it runs. Each run gets a fresh browser with no cookies or stored data from earlier runs.

## Setting it up

Create a **Web** platform with the website's **Base URL**. Every recording and every run starts by going to that address.

To test a staging site or an internal tool that is not on the internet, see [Testing inside your network](/docs/connector).

## What the recorder can do on a page

- **Click, type, clear, double-click, hover, press keys.**
- **Dropdowns:** **Choose an option** works on a real `<select>` and on custom dropdowns built from other elements, by opening them and choosing the option by its words.
- **Dates:** **Set a date** sets a date field to a calendar date, with the events a page listens for, so the same step means the same date in every browser.
- **Scrolling:** **Scroll until you see…** scrolls until an element is on screen, for long pages and lists that load more as you scroll.
- **Pop-ups:** a page's own alert, confirm or prompt box is answered with **Accept the pop-up**, **Dismiss the pop-up** or **Type into the pop-up**. While one is open, the recorder shows what the box says. Boxes are never closed automatically, so "Are you sure?" can be tested.
- **Frames:** choosing an element inside a frame enters it. **Leave the frame** comes back out.
- **New windows and tabs:** **Go to the new window** follows a link that opened one.
- **Emoji and accented text** type like any other text.

## Signing in

Record your sign-in as its own journey, such as "Sign in", and make it the first journey of the others (**Runs first → Add a prerequisite**). It is recorded once, and every journey that needs it starts already signed in.

Use a test account. The values you type are stored with the journey so that it can be run again.

Sign-ins that send you to another site and back, such as "Sign in with Google", are recorded like any other step, but identity providers often ask for extra checks when they see a new browser, which makes them a poor fit for automated runs. A test account with a password is more reliable.

## Changing the address

**Change address** on the platform moves it, for example from staging to production. Recorded steps that start with the old address are moved to the new one, so the journeys test the new environment, and BitAssure says how many it moved. Steps that go to other sites, such as a payment page, are left alone.

## Limits

- Chrome only. Firefox and Safari are not offered.
- A run may take up to 10 minutes.
- BitAssure checks what a person would see and do. It does not compare screenshots pixel by pixel, read your server's logs or confirm that an email arrived.