> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/contributor/contributor-guides/testing-standards/testing-e2e.md).

# Testing E2E

{% hint style="info" %}
This section is currently a Work in Progress (WIP).
{% endhint %}

This section describes how developers will test codebase related to the e2e tests.

## Testing stack

All of our UI tests MUST be done using [Cypress](https://www.cypress.io/) as the main testing frameworks with [Synpress](https://github.com/Synthetixio/synpress) for wallet support. The test's code MUST be written using [Typescript](https://www.typescriptlang.org/) and ran using [ts-jest](https://github.com/kulshekhar/ts-jest) to have type checking support.

## Directory structure

New tests MUST be placed in a `tests/e2e` directory, in the root path. The files will be named as the flow that they will be testing, that is, if the e2e tests file will be testing the `Collection Publication` flow, the name of the file MUST be `collection-publication.spec.cy.ts`.

## How frequent they will run

Scheduled via GitHub Actions. Frequency TBD.

## What to test

* Most relevant user interactions in the dApps (Items Publications, NFTs Purchases, etc.)

## How to test

All of our tests MUST follow the semi-structured style of **Given-When-Then** (GWT).

The following example:

1. **Given** a user visits `https://example.cypress.io`
2. **When** they click the link labeled `type`
3. And they type "<fake@email.com>" into the `[data-testid="action-email"]` input
4. **Then** the URL should include `/commands/actions`
5. And the `[data-testid="action-email"]` input has "<fake@email.com>" as its value

Should be written as:

```jsx
describe('Given a user visits https://example.cypress.io', () => {
  beforeEach(() => {
    cy.visit('https://example.cypress.io')
  })

  describe('when clicks the link labeled type', () => {
    beforeEach(() => {
      cy.contains('type').click()
    })

    describe('and type an email into the action-email input', () => {
      beforeEach(() => {
        // Get an input, type into it
        cy.get('.action-email').type('fake@email.com')
      })

      it('Then the url should include /commands/actions', () => {
        // Should be on a new URL which
        // includes '/commands/actions'
        cy.url().should('include', '/commands/actions')
      })

      it('and the action-email input value should contain the typed email', () => {
        //  Verify that the value has been updated
        cy.get('.action-email').should('have.value', 'fake@email.com')
      })
    })
  })
})
```

## Testing contracts

For testing smart contracts, refer to the Solidity Standards documentation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decentraland.org/contributor/contributor-guides/testing-standards/testing-e2e.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.