I can send a screenshot

probably. NPM module api is nice

you can do so much with network intercepts, I have an entire 60 lesson course on it https://cypress.tips/courses

Hey Folks, last week I shared an issue with component tests in #755921564108587038(https://discord.com/channels/755913899261296641/755921564108587038/986621350196178945) and I have also created issue on github (https://github.com/cypress-io/cypress/issues/22353). Any help is much appreciated, since it seems we will have to rollback to v9 because of these performance issues.

You won't get a reply from any of the Cypress team today. The office is closed for a holiday. Are you on one of their paid Dashboard plans? You'll probably get more traction in resolving this via email support

When I'm attempting to execute the default cypress example test with example e2e support file, when the "cypress-testing" module is being used by user project, cypress says it doesn't find the support file, while when running the same exact scenario from the main module, it works, any idea ?

hey everyone! is someone else having issues downloading cypress binaries? I'm getting that cloudflare error 524 page trying to open https://download.cypress.io/desktop/10.1.0?platform=linux&arch=x64

Ok, so I can conclude that I feel Cypress is not built to serve complex automation infrastructure projects that want to wrap and separate between the Browser control, Test runner, Assert library and tools, In one way it's great as serving all in one at the tested project, in the other it's giving me hard time to try and create from it manageable project that will be inherited by multiple development teams while zero config will required by Dev and the DevEx will be in charge of it, I don't want to go back to Selenium as i've used it for too long and its way of interacting the browser through drivers is a quite old fashioned (although some will argue with that), so the middle man here is Playwright that allow to use them as standalone Library to control the browser and customize everything around it

hey anyone know how to utilize the faker.js dependancy to generate user data

i'm having issues

Suggest any YouTube tutorials for learn cypress hindi language prefer if tutorial are best then no problem in English

suggest

faker is deprecated, use chance.js, also moment.js is deprecated too, i'd suggest dayjs, i'm pretty sure you know them from postman, like i did and had troubles with them

Hey @average-market-67864, we use it that way. It is private repo so I cannot show you, but imagine that your have one repository with whole configuration. Other Projects will just install the package with npm and use it like this:

// cypress.config.ts
import sharedConfig from 'your-package/configs/cypress/cypress.config'
import { defineConfig } from 'cypress'

export default defineConfig({
  ...sharedConfig,
  // any custom settings that are needed per project
  // for example, we use happo for only some projects
  component: {
    ...sharedConfig.component,
    setupNodeEvents: (on, config) => {
      sharedConfig.component.setupNodeEvents(on, config)
      happoTask.register(on)

      return config
    }
  }
})

? that's a weird statement. That's your choice of course, but I feel you have decided to overcomplicate things from the start, while having a minimum of Cypress experience. One thing that might help you is to look at the presentation https://slides.com/bahmutov/testing-large-org and look at my presentation at FrontEnd Test Fest this Thursday, I think it will be useful https://applitools.com/front-endtestfest/#event-agenda

why can't I use

a js method

in my cypress suite

How do I fix CORS error

Cypress commands like

cy.get

return jQuery object, so you can invoke its

html()

method to get it,

cy.get(....).invoke('html')

Anyone know how to use cypress with passwordless login built using nextauth.js?

Thanks Tomas for the example! I don't want the sub-projects to install Cypress at all, I want them to inherit it from the main project, for example, if a version update will occur, one project will affect all of the sub-projects without any required action from the development teams to touch anything, I don't want to control only the configuration, i want to control the browser interaction library so all the development teams won't be coupled too much to a specific library, but rather to infrastructure wrapping library

You are not mistaken, my practice is to build infrastructure projects in a way that they are not dependent on the browser controlling library they are using, so once the market change in the years to come, it will be easy to switch between library to another without too many efforts, that ensures the longevity of the project in the company without having future technical depths, because technology changes all the time and I don't want to be coupled with a specific library does it make any sense to you ?

and I hope I don't hurt the cypress community's feelings here, it's not my meaning, my approach is trying to be as much as coupled-less for every type of browser controlling library

I doubt you've hurt anyone's feelings, tbh. I think Gleb was just saying that you have reached that conclusion very quickly. I have a decoupled library that handles a lot of the tasks that are common for our JS testing frameworks. It's a double-edged sword. While it does mean we're not overly tied to one tool, it has caused some weird behaviours in Cypress and a lot of duplication of things Cypress can do out of the box (eg having to make api calls using functions wrapped in

cy.task()

rather than just being able to use

cy.request()

) Given that I spend a lot of time debugging weird issues related to this tool-agnostic library, I don't think it's been much of a time-saver. So I'm tempted to remove the decoupled framework. Then I can play to Cypress' strengths. If a new tool comes along that is better, I can adopt that and play to its strengths But ultimately it's your choice and you should go with what's best for you and your project. I don't think anyone is going to go out of their way to convince you one way or the other 🙂

Thanks a lot Liam, great discussion 🙂 really appreciate your opinion your description of pros and cons sounds very accurate

if you want to decouple, check out https://codecept.io/

I'd like to ask suggestion about one use case we have, We're currently managing a modular monolith application, with a shared ownership of pages, features, libs, etc... We have a programmatic way of checking the ownership of a given test, what we would like to do is to have a way to group them inside cypress dashboard. Something like Tags, but we currently run ALL tests in a parallelised fashion (having 20+ machines). What do you suggest doing so we can in run time, flag that a test belongs to a given team, so when they fail (for instance) we can easily see that info

@average-market-67864 one way to help decoupling is to only use descriptive function names in your it blocks, like so. I define the functions further down the page.

js
describe('register page', () => {
  it('behaves correctly', () => {
    visitRegisterPage()
    shouldSeePasswordResetLink()
    submitEmptyForm()
    shouldSeeValidationErrors()
    submitFormWithExistingEmail()
    shouldSeeErrorForInvalidEmail()
    shouldSeeSignInLinkInError()
    shouldSeePasswordResetLinkInError()
    submitFormWithWrongConfirmEmail()
    shouldDisplayErrorForEmailMismatch()
    submitFormProperly()
    modalShouldAppear()
    dashboardValuesShouldBeCorrect()
  })
})

What I would like to see more of with test tools (including Cypress) is a good way to keep track of written tests and the requirement coverage they represent. I'm not interested in BDD per say, just a way to better organize things.