How to use getComponentDisplayName method in Cypress

You might need to use .then instead of should and the request should resolve inside promise. It is writing a file for me inside the fixture folder. But in the answer I left as the same path as given in your question.

it('Query Endpoint', () => {
        cy.request(
            {
                method: 'POST',
                url: '/api/service', 
                auth: {
                    username: Cypress.env('username'),
                    password: Cypress.env('password')
                },
                headers: {
                    'Content-Type': 'application/json',
                },
                body: {}
            })
            .then((request) => {
                const someRequest =  JSON.stringify(request);
                cy.writeFile('cypress/fixtures/api-service.json', someRequest)
                //...rest of the code 
          })

    })

To force an arbitrary loop, I create an array with the indices I want, and then call cy.wrap

var genArr = Array.from({length:15},(v,k)=>k+1)
cy.wrap(genArr).each((index) => {
    cy.get("#button-" + index).click()
})

I got exactly same problem and after hours of research I found a workaround that solves this. It is not a real fix but it solves your issue and mine. Here are the steps I did:

Create a 4th spec file, call it main.spec.ts, inside this file do an import for the 3 spec files you have:

import './fillform.spec.js'
import './uploadphoto.spec.js'
import './result.spec.js'

In cypress.json file, add the following entry to allow to run only the main spec file:

"testFiles": ["main.spec.js"],

Now cypress run will work exactly as cypress open and all specs will run without closing the browser in between:

npx cypress run --headed --browser chrome

This is a pretty broad topic but I have some things that I think would be helpful to you. Comment on this answer if you would like me to clarify or add something.

Identify repeating words and consolidate
One example would be "cart". If that word is repeated at the beginning of every test spec, then create a directory called cart and put all the cart test specs in there. Nesting various things in this fashion can be helpful. If the file is located in a directory called "cart", you can remove it from the name.

Don't over/under nest
Trying to over organize can leave you more confused. Those Matryoshka_dolls come to mind(https://en.wikipedia.org/wiki/Matryoshka_doll). Nest things as you need to. The same is true for abstracting things into page objects. Over or under abstracting can make things more confusing.

Avoiding cascading failures
Be careful not to write you test in a way that if one it fails, the following its will fail. You also won't get proper retires if you don't respect potential cascading failures. This is a double edged sword as well. If you only have one it per spec, test execution times will grow. If you have made good decisions with how you break apart your test specs and still need to improve execution time, look into parallelization: https://docs.cypress.io/guides/guides/parallelization.html#Splitting-up-your-test-suite

Shared/Common methods
You can use Page Object Modeling(acceptable to use but sometimes referred to as an unnecessary abstraction/anti-pattern) to make your code reusable. Basically you have external files that you pull in(as an instance to allow for parallelization) and reference those methods in your test specs so that your test can remain DRY(Don't Repeat Yourself). Your fellow developers will respect your effort to follow the Object Oriented Programing Principals. DRY is one of them.

Cucumber for ease of reuse and readability
Consider using Cucumber syntax/testrunner if you have a ton of repeating test logic with different permutations. Each "step" or Given/When/Then is backed by code. You can use regex to allow for parametrization.

Hope this helps! Organization is something you will continually revist and refactor your code. Each team will have different needs. Approach this in a very collaborative fashion with all interested parties providing feedback. Godspeed!

You probably just want to make a .type() variation

Cypress.Commands.add('typeIfNotEmpty', { prevSubject: true }, (subject, textToType) => {
  if (textToType) {
   cy.wrap(subject).type(textToType)
  }
  return subject  // allow further chaining
})

cy.get('#username')
  .typeIfNotEmpty(username)
  .should(...)               // some assertion on '#username' element

Not a cucumber user, but in plain Cypress tests you can only access this by making the callback a function not an arrow function

Given("I check data", function() {
  console.log("this", this.data.user);
});

I think you might have to alias the data as well

before(() => {
  cy.fixture('example')
    .then(function (data) {
      console.log("this", data.user)
    })
    .as('data');
}

Note that Cypress clears aliases in between tests, so you would need to use beforeEach() instead of before().

To find all <select> elements with a name equal to "timeentry_lov1" in the page, use a CSS selector that filters on the name attribute, like this:

cy.get('select[name="timeentry_lov1"]')

To select only the second <select> tag, you can use :nth-of-type(2) to select only the second element that is found:

cy.get('select[name="timeentry_lov1"]:nth-of-type(2)')

Now, to actually select the element, just use cy.select() with the value of the <option> you want to select:

cy.get('select[name="timeentry_lov1"]:nth-of-type(2)')
.select('NB-860')

That should accomplish what you're trying to do.

Tip: you can use Cypress's Selector Playground to help you find good CSS selectors to use in your tests. Check out the docs for a video on how it works.

The snowflake-sdk is a NodeJs package, so in Cypress you need to interact with it via a task.

Here's a basic connection task taken from the Snowflake docs.

cypress.config.js

const { defineConfig } = require("cypress");
var snowflake = require("snowflake-sdk");

let connectionId;

module.exports = defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      on("task", {
        snowflake: () => {
          var connection = snowflake.createConnection({
            account: "account",
            username: "user",
            password: "password",
            application: "application",
          });

          connection.connect(function (err, conn) {
            if (err) {
              console.error("Unable to connect: " + err.message);
            } else {
              console.log("Successfully connected to Snowflake.");
              // Optional: store the connection ID.
              connectionId = conn.getId();
            }
          })
          return null
        },
      });
    },
  },
})

Test

it('Connect to snowflake', () => {
  cy.task('snowflake')
})

Without proper credentials, it produces a connection error but proves the package is working.

Unable to connect: Request to Snowflake failed.

HTTP_PROXY was added and Cypress.io should be able to work with your proxy with that set. I however still can't get our HTTPS to work, so its not totally working