How to use setResponseFromFixture method in Cypress

First, you need to add the env variables as empty strings on cypress.json:

{

  "env": {
    "userId": "1",
    "environment": "production",
    "baseUrl": "base URL",
    "username": "",
    "password": ""
  }
}

In main.yml file, you need to add the CYPRESS_ prefix to the variables:

env:
  CYPRESS_username: ${{secrets.CYPRESS_USERNAME}}
  CYPRESS_password: ${{secrets.CYPRESS_PASSWORD}}

Also, you should use the setup that can be found on cypress docs (https://docs.cypress.io/guides/continuous-integration/github-actions#Basic-Setup), example:

name: Cypress Tests

on: [push]

jobs:
  cypress-run:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      # Install NPM dependencies, cache them correctly
      # and run all Cypress tests
      - name: Cypress run
        uses: cypress-io/github-action@v2
        with:
          build: npm run build
          start: npm start
        env:
          CYPRESS_username: ${{secrets.CYPRESS_USERNAME}}
          CYPRESS_password: ${{secrets.CYPRESS_PASSWORD}}

You should also read this article: https://glebbahmutov.com/blog/keep-passwords-secret-in-e2e-tests/

From cypress.d.ts

interface Cypress {
  /**
   * Returns specific environment variable or undefined
   * @see https://on.cypress.io/env
   * @example
   *    // cypress.json
   *    { "env": { "foo": "bar" } }
   *    Cypress.env("foo") // => bar
  */
  env(key: string): any
}

so you can extend it with

declare namespace Cypress {
  interface Cypress {
    env(key: "example"): string
  }
}

which gives intellisense (method) Cypress.Cypress.env(key: "example"): string (+6 overloads)

You can use contains to select elements by textual content, like this:

cy.get('a').contains('CONTENT').click();

Note that the used href attribute value is invalid, protocol and quotes are missing, should be something like this:

<a href="https://example.com/">CONTENT</a>

Documentation can be found here: https://docs.cypress.io/api/commands/contains

If I understand correctly, you are looking for

cy.get('a[href="..."]')

Similarly

cy.get('img[src="..."]')

where you should add the appropriate text instead of ...

Of course, follow with .should('be.visible').

If you want to use a partial match, you can use

cy.get('img[src$="bottle.png"]')  // NOTE src$= 

You can access an array item (in your case it's the object) using the index position (in your case it's zero)

cy.get(".gLFyf").type(this.lead.result.records[0].Id)

1. add @istanbuljs/nyc-config-typescript to your devDependencies

2. babel.config.js

module.exports = {
  presets: ['@vue/cli-plugin-babel/preset'],
  plugins: [
    ['babel-plugin-istanbul', {
      extends: '@istanbuljs/nyc-config-typescript',
      extension: ['.ts', '.tsx', '.js', '.vue']
    }]
  ]
}

3. delete the nyc.config.js file

4. delete node_modules/.cache

5. restart your server

Try this:

cy.get('select option:contains(C)').should('not.exist')

I think one difference could be found here: https://github.com/testing-library/cypress-testing-library#differences-from-dom-testing-library

find* commands will fail if more than one element is found that matches the criteria which is not how built-in Cypress commands work, but is provided for closer compatibility to other Testing Libraries.

That's not how contains() works. From the docs: https://docs.cypress.io/api/commands/contains.html#Single-Element

Only the first matched element will be returned

contains() also works with preferences, e.g. contains() yields <button> element even if it's higher in the tree when the deeper element is e.g. <span>. So it prefers <button> elements over deeper elements if you don't pass a selector argument the command. There're other examples in the docs for this command.

So it seems to me now that find* commands in the Cypress Testing Library more closely resemble the behaviour of other testing libraries as it's said in the docs. With contains(), you perhaps need more knowledge about how it works so you get elements you want and not some other ones because e.g. you don't understand how this preference logic works.

I am facing a similar issue. I wonder if this may have resolve the problem:

6.2.1 6 months ago

"multipart/form-data is no longer wrongly encoded when using cy.intercept(). This should prevent Unexpected end of multipart data errors on the back end service where the request was pointing to. Fixes #9359."

https://openbase.com/js/cypress/versions