Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "Cypress performs most of its API tests via the cy.request() method, which serves as a GET command to the web server being tested."

A block of code is set as follows:

cy
  .get('list')
  .first(); // "select first item in the list "
cy
  .get('list')
  .last(); // "select last item in the list "
cy
  .get('list')
  .eq(2); // "select 2nd item in the list
"

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

describe("Docket Post Test 2", () => {
    it("Should create a Todo item", () => {
        cy.request({
            method: "POST",
            url:
             "https://docket-test.herokuapp.com/api/Todo/",
            headers: {
                token: "YOUR TOKEN ID",
            },
            body: {
                Body: "Barclays Demo",
            },
        })

Any command-line input or output is written as follows:

npm install axe-puppeteer

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: "Upon any test launch from the GUI, users will have the ability to click on the Add New Test button."

Tips or Important Notes

Appear like this.