Basics

Importance of testing

Types of Testing

Manual and Automation Testing

Software Testing Introduction

JavaScript Conventions

Comments

File Naming Conventions

Function arguments conventions

JavaScript and File Naming Conventions

What is Cypress

Features of Cypress

Introduction to Cypress

Understanding the Cypress directory structure

Running Cypress tests on a neeto project

Running Cypress tests

Use tags to selectively run spec files

How to skip test cases

Selectively run test cases

Test Suite

Test Case

Conventions for describe and it block

Test Suite and Test Case

before() Hook

beforeEach() Hook

afterEach() Hook

after() Hook

Using hooks in Cypress

Reasons to keep all the scenarios in a single test case

Writing a test case in cypress

List of Commands

Nature of Cypress commands

Commonly used Cypress commands

Conventions for adding data-cy

data-cy conventions

Custom Commands in Cypress

Commands vs Utility Functions

Utility Functions in Cypress

Intercept

How to wait for API response

Fixtures in Cypress

Avoid adding empty line after each statement

Avoid writing comments

Importing external files before internal files

Avoiding Repetitive Code

Maintaining API paths

Add files that we don't want to commit or track in .gitignore

Use webpack aliases

Importing fakers from fixtures

Use `within()` for narrowing the scope of cypress

Group variables based on the context

Organizing and maintaining Cypress tests

Selectors

Texts

Importing selectors and texts variables

Aliases

Usage

Selectors and texts

What are flaky tests

Causes of flaky tests

Flaky Tests

Login programmatically

Use proper selectors

Don’t assign command’s return values

Don't test external sites

Make every test independent of each other

Avoid single assertion tests

Don’t clean state using `after` or `afterEach` hooks

Don't use wait for arbitrary time period

Start Web Servers prior to running cypress

Set a global baseUrl

Avoid `{ force: true }`

Avoid chaining of array elements with `.eq()`, `.first()` etc. in the test case

Avoid unsafe chaining of commands

Use `scrollIntoView()` to detect partially visible elements

No need of common assertions for actionable elements before performing actions

Custom commands should be purely functional and should not have code pertaining to verifications

Enable retries

GitHub related

Cypress Best Practices

Cypress configuration

Browser

Retries

Timeouts

Viewport

E2E Options

Project settings on cypress dashboard

Project Settings

Setup

Test body

Testing Create tag function

Testing Edit tag function

Testing the delete function

Teardown

Point to remember

Additional resources

Writing Tests

Session Command

How does it work?

How was it used?

How is it used now?

What is request?

What is required for a request?

HTTP Method (method)

Headers

Body / Payload

Status

Response Headers

cy.request command

/learn-qa-automation-using-cypress/software-testing-introduction

Automation using Cypress

BigBinary Academy