I am setting it up inside of my cypress plugin file

can you open an issue with details? Did you add the plugin to the support file? https://github.com/bahmutov/cypress-grep#install-and-use

guys, i have tag with message, how can i disable the JS and assert this massage

i am trying this now

it("Checking for an informative message when the JavaScript is disabled", () => { cy.visit("/", { script: false }); cy.get("noscript") .should("contain", "We're sorry but todo doesn't work properly without JavaScript enabled. Please enable it to continue." ) });

or with cy.get("body noscript strong") but the JS is still working and i cant assert the massage

Hey Gleb! I can for sure, I just followed the documentation. 1 - add

require('cypress-grep')()

to support/index.js 2 - add

require('cypress-grep/src/plugin')(config)

in module.exports from plugins/index.js 3 - add

describe('test name', { tags: 'fast' }, () => {

in a single test as example 4 - run

npx cypress run --env grepTags=@fast

for the example the output said: found 93 tests (that's all tests)

does @cypress/snapshot not run in node? it's using a module that requires a lot of process variables

ohh, I see - the describe blocks still don't work 🙂 because it is ambiguous how to check the individual tests vs suites of tests, see https://github.com/bahmutov/cypress-grep#test-suites You can skip the entire suite, but not

.only

it

Ah, thanks for telling me that! At work we have an internal tool that provides cypress test reports. I wonder if there is a way to get metadata out of the tests to identify whether they are part of certain tag or not

Hi everyone, I'm rather new to Cypress as a young QA testor. I was wondering if there is any way to get real time informations such as today's date or current time for example to use them within my Cypress tests. I search the net for articles but couldn't find anything. Thanks in advance ! 🙂

Hi Everyone, I need some help I am trying to automate a scenario using cypress where I need to signup for new user using my Web-app and verify the user by visiting verification link sent to my email. But the moment i visit the link it changes the url from https://app.example.com/#/activate/hash= to https://app.example.com/document. I am able to fetch the signing link from email using Gmail tester library Cypress, but the moment I visit link it doesn't load anything in the application window neither it changes to url to new one . How to handle such scenario?

@User what's your specific use-case? Can you use a

Date

object? e.g.

const now = new Date()

?

@User so basically, I have a time object that gets the date and time of last upload of a dataset and it changes everytime the dataset is uploaded. I'm trying to find a way to verify the date and time is the same as the actual date and time. And I'm kinda new to Cypress, so I'm not sure what your e.g. would permit me to do ?

@User I would usually just not test that.

Seriously. Unless it's VERY important that that feature works, and that it has broken in the past, I wouldn't test something like that.

Well, to be honest, it's not really that important. It used to not work properly before, that's why I wanted to make sure it's working

I'm trying to run the Cypress's Dashboard on a single specific file from the terminal locally. I ran the command

npx cypress run --record --key <key-goes-here>

, however this runs the entire suite. I tried

npx cypress run --record --key <key-goes-here> --CYPRESS.spec="cypress/integration/path/to/file/*.spec.js"

but I dont' get it to work. Any ideas what I am doing wrong?

I figured it out. I needed to change

--CYPRESS.spec="cypress/integration/path/to/file/*.spec.js"

to

--spec="cypress/integration/path/to/file/*.spec.js"

Hi all. I'm having a difficult time debugging node code that exists in the context of a cy.task. Any breakpoint set there is unbound. Any ideas on how to overcome this problem would sure be appreciated. (breakpoint) = a real breakpoint in the code Here is an example of code in /plugins/index.js module.exports = (on, config) => { on('task', { async 'seed'({database}) { (breakpoint) dataset = await dbSeed(); (breakpoint) return dataset; }, ... Here is an example of code that would call it from a spec. describe('Some Suite', () => { before(() => { cy.task('seed', {database}) }) }) So, the problem is that the breakpoints are a hollow circle in VSCode and shown as not bound when executing the code.

This is a hard problem you are having here. Because the chrome/node debugger tools get lost often with async code. Additionally cypress tends to have a hard time with any async/await since it is using Bluebird in a lot of places. Could you try and rewrite the same code using callback functions in promises?

in this case, it would look like

dbSeed().then(dataset => {do something with your dataset})

Hello, I'm in the process of setting up azure ci pipeline to run cypress tests on azure agent with multiple docker containers parallelly. Are there any working examples of yaml for docker parallell ?

Hi. I refactored the code similar to what you suggested but no luck. Breakpoints are still unbound. Any other ideas? I think that it may be because the source maps are missing or that VSCode cannot find them but I am not certain how to verify.

Hi 👋 Anybody knows how to force an alias to replay instead of keeping the previous element that it got (because it got updated since)

ts
    cy.get('button').contains('ADD TO CART').click()

    cy.get('#state').invoke('text').then(JSON.parse).as('state')
    cy.get('@state').then((cartState) => {
      const expectedCartState: TCartItem[] = [{ ...order, quantity: 1 }]
      expect(cartState).to.deep.eq(expectedCartState)
    })

    cy.get('button').contains('ADD TO CART').click()

    cy.get('@state').then((cartState) => {
      const expectedCartState: TCartItem[] = [{ ...order, quantity: 2 }]
      expect(cartState).to.deep.eq(expectedCartState)
    })

It does not have to be alias - it's just because I think it's a bit too much to do

cy.get('#state').invoke('text').then(JSON.parse).then(..assertion)

on every assertion

@User you can simply make it a function

or add it to Cypress's commands. That's usually what I do to group commands

I did try that..

const assertState = (assertion) => cy.get('#state').invoke('text').then(JSON.parse).then(assertion())

It did not work