it is not headless, if you believe it

Hello All, What is the command to execute the scripts based on tag in Cypress with cucumber ? For ex. tag is @regression

Have we serial mode in cypress like in playwright?

No, and Cypress avoids test inter-dependence. Playwright's serial mode (https://playwright.dev/docs/test-retries#serial-mode) would probably be considered a code smell in the Cypress world where tests are intended to be fully independent from each other. The closest thing you'd have is a setup hook like a

beforeEach

.

tests being dependent on each other has been a code smell in QA automation for as long as I've been doing it. Why playwright offers it is strange to me

I haven’t tried out Playwright yet myself, but I may at some point. I’m curious why people like it so much.

I gave it a shot a few months back. I liked that it isn't as opinionated as Cypress is. From that perspective, it's much closer to Selenium. What I didn't like is that many of the helpers that Cypress supplies arent' there. All in, we decided to stay with Cypress because of ease of use. I will say that playwright dealt much more smoothly with iframes and cross domain testing than Cypress does, and that is why we were exploring playwright in the first place. Cross domain testing in Cypress feels an awful lot like it is something they threw together as a "we don't want to do this, but enough customers complained, so here's something". Iframes are similar, but in that case, Cypress relies on a plugin that works, but really should be native, since so many websites use them.

I am planning a course showing both tools and how they are different and how it reflects on the types of tests https://cypress.tips/courses/

were you able to solve the problem? there are few bunch of questions I have for this.. firstly IMHO as best practice I believe describe defines a test suite. You should only have one top-level test suite per file, and only one domain per test. I would just change those describes to contexts and wrap the contexts in a single describe. Correct me if I am wrong if I misunderstood your problem but as you probably know cypress more than me but as soon as cypress starts the tests it tries to get the number of tests in the spec and the

data

object defined initially is taken and thus the element

el

takes the value from that. However if you

cy.log(data);

in your first it() you will see that you are getting the correct data after before. So I believe it is working as designed So basically your object should be finalized before cypress test execution starts if you want your data.forEach to get the final changes, having it in before probably wont work try moving the object assignment outside of before() directly to describe that should work

Am I restricted to these versions of Chrome (currently latest being 107) if I need to use a Cypress provided Chrome image? https://github.com/cypress-io/cypress-docker-images/tree/master/browsers

Ok, I tried running with the cypress/included container... but since we are using docker to run our DB the tests can't run because cypress/included doesn't have its own nested docker.

I guess the assumption is that you must use "containerized services" for your DB?

This feels like big pile of shit hoops to jump through just because Cypress can't allow two different Chrome versions

@swift-megabyte-13324 See https://hub.docker.com/r/cypress/browsers/tags/ for Chrome 113 and https://github.com/cypress-io/cypress-docker-images/issues/889 for the documentation issue. Also answered in https://github.com/cypress-io/github-action/issues/602#issuecomment-1543291385.

Thanks @many-airline-45402 . However, do I have an easy way to run docker inside of this container. Or would that mean I need to use GH's "containerized services" to run the db if I use: container: cypress/included:12.12.0?

@swift-megabyte-13324 I'm not sure I understand your question. You can find an example using a Docker container from Cypress with

github-action

and a database in https://github.com/cypress-io/cypress-realworld-app/blob/develop/.github/workflows/main.yml for Ubuntu recording into Cypress Cloud.

Does that part include running the actual DB inside the GH runner?

@swift-megabyte-13324 > Does that part include running the actual DB inside the GH runner? Correct. You can clone the demo repo and try it out for yourself.

Which command runs the DB?

It is quite complex. You'll need to take a look yourself if you want to understand it. Start at the https://github.com/cypress-io/cypress-realworld-app/blob/develop/README.md file.

Ah so this is seems to be using something called lowdb? But it seems it's more of a way to manage a .json file than a "real" database? Then you won't need to worry about how to run anything in Docker.

Now I am forced to waste a whole day on zero-value work and mess up our existing CI configuration because of this...

That must be very frustrating, but don't shoot the messenger. I'm just a community volunteer here. 🙂

Calling a tool you don't know how to use "sh*t" and complaining how you spend an entire day NOT learning is pretty bad form. Please review resources in #763097415896268840 and #1024063123579224124

I think you misunderstood. I didn't make a judgement about any tools. I just felt like I was being forced to do wasteful work for no good reason.

Then you expressed it really badly. Again, with this open source tool no one forces you to do any work. You can read extensive CI documentation, extensive Docker examples, study a course, etc. before you start coding. The only person doing wasteful work for no good reason is "Samu" here. Ok I am out.

Not sure what you mean by "spending an entire day NOT learning" refers to either. In the end I could make it work. But I had to spend a lot of time for no concrete benefit.

Sorry. I wasn't implying this as an insult to you. You have been tremendously helpful today. Thank you again.

Besides aren't you basically agreeing with my conclusion by saying this on Github: > Hehehe they won’t stop rolling new versions. It is up to cypress to not freak out when chrome updates from 111 to 112 as if it is the end of the world

Well it might be an open source tool. But we are also paying customers.