Delve into front-end testing principles, learn best practices for writing enduring tests, and discover strategies for E2E testing and integration into CI pipelines. Gain actionable testing insights.

React Testing 101 Component, Integration, and End-to-end Testing_1.png

tarball.tar.gz

jest

jest_describe

jest_onlytest

skiptest

aftereach

headless

foo2

opening

first_test

custom

final_job

foo_final

This course will provide you with important information, principles, and experience-based advice, to enter the world of testing methodologies. 

Here, you will learn the best practices to follow to write useful and lasting tests, how to test different user flows without a working back-end, how to write effective end-to-end tests (E2E), and how to integrate tests into development and Continuous Integration pipelines.

At the end of the course, you will be able to apply the fundamental principles of the test methodologies to understand what and how to test effectively.

Front-end Testing 101: Integration and End-to-end Testing

## Solution
> Note: You can see the Cypress UI better by opening the link next to **Your app can be found at:**

context('Typing the username', () => {
  it('Should fill the username input field', () => {
    cy.visit('/register')
    cy.get('.form-control').then(($els) => {
      cy.get($els[0]).type('Admin')
    })
  })
})

Java - Swing

Python - tkinter

## Explanation:
- **Line 3** We visit the `register` page of the `conduit` app.
- **Line 4** `cy.get(".form-control").then($els => ...`  is necessary because almost every Cypress command must be leveraged asynchronously. This will be explained in more detail in the [Cypress Waitings and Execution Order](https://www.educative.io/courses/front-end-testing-integration/cypress-waitings-and-execution-order) lesson.
`$els`, like every jQuery selector, is an array containing all the DOM elements that respond to the given selector (`.form-control`).
- **Line 5** We fill `username($els[0])` with the word `admin`.



# Solution
> Note: You can see the Cypress UI better by opening the link next to **Your app can be found at:**

# Explanation:
- **Line 3** We visit the `register` page of the `conduit` app.
- **Line 4** `cy.get(".form-control").then($els => ...`  is necessary because almost every Cypress command must be leveraged asynchronously. This will be explained in more detail in the [Cypress Waitings and Execution Order](https://www.educative.io/courses/front-end-testing-integration/cypress-waitings-and-execution-order) lesson.
`$els`, like every jQuery selector, is an array containing all the DOM elements that respond to the given selector (`.form-control`).
- **Line 5** We fill `username($els[0])` with the word `admin`.



# Explanation:
- **Line 3** We visit the `register` page of the `conduit` app.
- **Line 4** `cy.get(".form-control").then(＄els => ...`  is necessary because almost every Cypress command must be leveraged asynchronously. This will be explained in more detail in the [Cypress Waitings and Execution Order](https://www.educative.io/courses/front-end-testing-integration/cypress-waitings-and-execution-order) lesson.
`＄els`, like every jQuery selector, is an array containing all the DOM elements that respond to the given selector (`.form-control`).
- **Line 5** We fill `username(＄els[0])` with the word `admin`.



This review provides an explanation to solve the 'Fill Input Field' challenge.


Solution Review: Fill Input Field

This review provides an explanation to solve the 'Fill Input Field' challenge.

Introduction

E2E Testing

The First E2E Test

Polishing the E2E test

Ajax Requests

Custom Commands

UI Integration Tests

Other Best Practices

Bonus Section

Conclusion

Appendix

Solution Review: Fill Input Field

Solution

Explanation: