How to use projectCt.initializeConfig method in Cypress

By default, Cypress plugins file is run in the Node that's bundled alongside with Cypress's Electron app.

Youcan work around this in two ways:

1. Auto-compile files imported into the plugins file, by using @babel/register plugin. Remember, this workaround won't work for the plugins file itself.

   First, install it:

   npm install -D @babel/register @babel/plugin-proposal-object-rest-spread
   

   Then, on top of your plugins/index.js, do (babel@7):

   require("@babel/register")({
       plugins: [ "@babel/plugin-proposal-object-rest-spread" ]
   });
   

   https://babeljs.io/docs/en/next/babel-register.html

2. Run the plugins file using your system's Node executable.

   Cypress allows you to set nodeVersion configuration, which controls this behavior.

   E.g., set in cypress.json:

   {
       "nodeVersion": "system"
   }
   

   Note: this of course works only if your system's Node already supports that feature.

Cypress modifies chai.expect but does not seem to add a way to turn off logging.

If you import from node_modules you can run the original and avoid the log.

const chai = require('chai');

it('expects witout log', () => {
  chai.expect(USER).to.be.a('string').and.to.not.be.empty;  // no logging happening
})

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

Try to use another way to clear localStorage. For example, I'm using these commands to save, restore and clear storage and is working perfect. I'm using these for log in/log out things.

let LOCAL_STORAGE_MEMORY = {};

Cypress.Commands.add("saveLocalStorage", () => {
  Object.keys(localStorage).forEach(key => {
    LOCAL_STORAGE_MEMORY[key] = localStorage[key];
  });
});

Cypress.Commands.add("restoreLocalStorage", () => {
  Object.keys(LOCAL_STORAGE_MEMORY).forEach(key => {
    localStorage.setItem(key, LOCAL_STORAGE_MEMORY[key]);
  });
});

Cypress.Commands.add("clearLocalStorageCache", () => {
  localStorage.clear();
  LOCAL_STORAGE_MEMORY = {};
});

As Fody mentioned, there are node.js functions present inside simple-ssh so a task is needed.

This is the basic configuration.

It's a direct translation of what you have, but you would want to return something from the task. As it is, the console.log() goes to the terminal console not the browser console.

cypress.config.js

const { defineConfig } = require('cypress')
const fs = require('fs')
const SSH = require('simple-ssh');

module.exports = defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      on('task', {
        ssh() {
          const sshConfig = config.ssh
          sshConfig.key = fs.readFileSync('path/to/key/file')
 
          const ssh = new SSH(sshConfig)      
          ssh.exec('echo', {
            args: ['$PATH'],
            out: function(stdout) {
              console.log(stdout);
            }
          }).start();

          return null
        },
      })
    }
  }
})

test

Cypress.Commands.add('ssh', () => {
  cy.task('ssh')
})

cy.ssh()

You can achieve this with a custom command. You said you tried one and it didn't work, but I am doing something similar successfully in my tests.

Cypress.Commands.add("check403", () => {
  cy.get('[data-qa="http-error.section"]')
    .should('exist')
    .should('contain', '403'); // I changed this - you didn't mention that it
      // didn't work, but it would have been returning an element, not asserting
});

Cypress code is executed asynchronously. It will execute at a different time than your synchronous (read: regular JS) code. The expect from Chai is a synchronous command, so it is executed sequentially after updating your selected variable.

To avoid sync/async issues, you could include your synchronous JS code in the Cypress chain.

let last_selected; // removing from the iterations to avoid any sync/async issues
for (let i = 0; i < 4; i++) {
  cy.wrap(i).then(() => {
    selected.push(i);
    last_selected = selected[selected.length - 1];
  })... // rest of your Cypress commands.
}

The method you are using is not recommended by cypress and is considered an anti-pattern. https://docs.cypress.io/guides/references/best-practices.html#Assigning-Return-Values

Cypress recommends that you add custom commands. https://docs.cypress.io/api/cypress-api/custom-commands.html#Syntax

In the initially created folder structure, the commands.js file can be found under the support folder. Here you are able to create a command that wraps up the logic you wish to reuse. Based on the console.log portion of your code I assume this is run on the command line. There are custom commands for the console as well as for use in the UI.

for that portion you may have to add this custom command

// not a super useful custom command
// but demonstrates how subject is passed
// and how the arguments are shifted
Cypress.Commands.add('console', {
  prevSubject: true
}, (subject, method) => {
  // the previous subject is automatically received
  // and the commands arguments are shifted

  // allow us to change the console method used
  method = method || 'log'

  // log the subject to the console
  console[method]('The subject is', subject)

  // whatever we return becomes the new subject
  //
  // we don't want to change the subject so
  // we return whatever was passed in
  return subject
})

For the other functionality creating commands is pretty simple, the basic pattern is:

Cypress.Commands.add(name, callbackFn)

so you can potentially create something like

Cypress.Commands.add(allNameBeforeInput, (options, options) => {
 //custom logic goes here

})

Then you can use it by calling cy.allNameBeforeInput(options, options).

For instance, I was struggling with login and all my tests had login functions to log in through the UI but I wanted to start my tests on the correct page instead of the the log in page. I added this to the command.js file in the support folder:

Cypress.Commands.add('login',(username="notsharingmyusernam@stackexchange.com", 
password="somesecurepasswordshhh") => {
 cy.request({
   method: "POST",
   url: "/api/public/login",
   body: `{:person/email "${username}", :person/password "${password}"}`,
   headers: {
     "Accept": "application/edn",
     "Content-Type": "application/edn"
   }
 })
})

And now I can add the cy.login and a beforeEach function at the beginning of my tests. The before each to make the request to the server and wait for the request for login and the cy.login custom command to ensure that I can use that bundled up logic with just one cy command.

describe('Test suite for page traverse', () => {
    beforeEach(() => {
        cy.server()
        cy.route("POST","/api/graphql").as("graphql")
        Cypress.Cookies.preserveOnce("company_jwt_qa") 
    })

     it('traverses all subnav items', () => {
        cy.login()
            cy.visit('/index.html')
            cy.wait("@graphql")
        cy.get('[data-tag-component="subnav-group"]')
            cy.get('[data-tag-component="subnav-title"]').eq(1).click()


    })
 })

I might try this:

cy.get(".ibxudA").find('.WildnessText-kRKTej').should('have.text',"Wildness")

or

cy.get(".ibxudA").find('.WildnessText-kRKTej').invoke('text').then((text) => {
    expect(text.trim()).equal('Wildness')
});

This might be a similar question: How do you check the equality of the inner text of a element using cypress?