upon running the terminal command

if i run from dashboard it works fine

I'm going to have to see some screenshots to make sense of this

Sounds to me like it's something you've defined in your commands in

package.json

and forgot to update

@wooden-megabyte-23794 can i see your definition for the

cypress-tags

command?

This is my package.json file

When i run from terminal , this is referring the cypress.json file which doesnt exists , am i missing any config here?

@fresh-doctor-14925 : Please let me know if any details are needed

Please add the latest cypress-tags to your project

You are now using a cached version of cypress-tags

Because you do npx cypress tags. If it's not in your project it will look for one in your machine

Also look at this GitHub issue. https://github.com/infosum/cypress-tags/issues/220

You need to have cypress tags as preprocessor

Good morning. I am trying to assert a text that contains an apostrophe but keep getting an error. Does anyone know a way around it?

You could try escaping a character with backslash or using backticks around your whole string (same keyboard key as ~)

Thanks for your response. Error still persists

@adorable-smartphone-87280 I used backticks

It's kinda weird to me that you're getting the element with

cy.contains()

and a string, and then asserting on that with

should()

. If it's not there,

contains()

will fail anyhow

Oh I didn’t even notice that. That’s true this is an anti-pattern.

I changed it to cy.get('h1') but still getting the same error. Any thing I can do differently?

When you say error, what is that error ?

Detached from DOM maybe?

Try wrapping it all in a .then() block?

Can you @adorable-smartphone-87280 please give a sample code of how to go about that?

Bro you gotta learn to read the docs at some point. https://docs.cypress.io/api/commands/then#Syntax

Can you remove the should part. First see if your selector works.

And you can also change the should to have.text instead of contain

Hi everybody! I have a series of test specs for a web app, all of which require a logged in user. I'm doing the login via API and I have a custom command wrapped in cy.session, all of which works within each test--that is, I only need to log in once per spec file. The problem is that I want the login session to persist across specs, cacheAcrossSpecs=true but all specs after the first fail. It's proprietary code, so I can't show it, but I'm also certain that this is me just not fully understanding it, so if I could get a quick walkthrough w/r/t caching sessions across specs, that'd be great. And no, I DON'T want to use preserveCookies since that's going away (that's where I came from anyway lol)

Hi everyone. I have setup eslint + cypress + husky in my react project. I run pre-commit hook(npm run lint:check && npm run test -- --watchAll=false && npm run test:e2e) from 'pre-commit' file present in .husky folder before each commit. Everything works fine when I try to commit with vscode's integrated terminal. But when I try to commit from vscode's source control, eslint and unit tests runs fine but I get an error while running the e2e cypress test(npx cypress run) in the vscode terminal. Find the screenshot of the issue. Any help would be appreciated. Thanks in advance.

Hi All, Is it possible within cypress to be able to automate a googlepay payment test. Currently when using cypress no popup appears when i click the button to proced to the next step. I have searched online and have not found much help. Is the only way to do this via API if so how would i begin creating it Thanks