I am completely new to cypress...and struggling to figure out how to get started with Cypress Cloud

Do I still need to install it locally?

To be clear, 'Cypress' and 'Cypress Cloud' are not the same thing. If you are not sure how to get started with Cypress then check out this: https://docs.cypress.io/guides/getting-started/installing-cypress It needs to be installed via npm (install node package manager first: https://nodejs.org/en/) Once you install Cypress then you can start figuring out how to create tests, this is a fantastic starting point: https://docs.cypress.io/guides/end-to-end-testing/writing-your-first-end-to-end-test Regarding Cypress Cloud, it is a feature-rich dashboard for stats regarding your test executions. It used to be called Cypress Dashboard which I think was a clearer name tbh, but anyway it got renamed 🙂 Be sure to read all the documentation under cypress guides, it explains a lot of stuff and also introduces many best-practices which are super important.

OK so Cy Cloud is simply an extension of the local app and not a replacement. The tests are still supposed to be written locally and run locally. Cloud is just a dashboard.... is that right?

If that is the case, then agree that Cy Cloud is a misnomer. I will go through the guides. Thx

tests are not supposed to be run locally, they are developed locally, but are supposed to be run in a pipeline on a server machine. You can create your own reporting tool, at least for the beginning, but later on the cloud provides insights and information that helps a lot with properly setup the whole process

In fact, it was recently renamed from Cypress Dashboard to Cypress Cloud! https://www.cypress.io/blog/2022/11/01/cypress-dashboard-will-soon-become-cypress-cloud/

Ok this sounds much better.... I would like it to be run on cloud along with all the stats.... this is so much better.... especially if it can be integrated with bitbucket (on every check in of the code)

Yes, for example I use GitLab's CI/CD pipelines as my test runner, using the cypress docker images available to pull and execute on a dedicated machine we have, you can use any CI/CD solution you like

yup, same here, i've even created custom discord integration to report failed tests with steps and pictures directly in a discord channel

But now days I asked the company to buy the dashboard because the tests are too many and i need more info

Yeah the Cloud Dashboard is a very good info point, super quick feedback and access to failure screenshots and videos instantly saves a lot of time. We've got the Slack integration going directly from the Cloud Dashboard as well 🙂

We just had to be careful which jobs ran through the Dashboard keys, as many small runs on live smoke were ruining our test run quota lol

hi all, i have a question, there is some plugin in chrome to user the finder of cypress to find elements but in chrome ?

There is a Cypress Recorder plugin for Chrome where you can enable it, use the website like a user would, then it spits out a bunch of Cypress code from what you did. Although it's very bad practice and makes horrible messy code, but it could let you find what some elements are called. Not sure why you wouldn't just use the Cypress timetravel GUI though.

When using Cypress (v10) in interactive mode, I'm able to play around with the application after the test have finished and the runner is idling, because the cookies are preserved. This however isn't the case if the last test is a skipped test. Anyone else seen this?

And v12 appears to clear the page if the last test is a skipped test

Anyone seen this?

And v12 appears to clear the page if the

Newbie here, what's the point of running the tests in a pipeline? Just wondering

This question is easily answered if you google what's the point of CI/CD. If you work with a team or in a company, you must have your tests in a pipeline

I googled it but I didn't get the clear picture. What's the point of running the tests 24/7, you can run the test locally when a new module is integrated and check for bugs. 😦

You aren't running them 24/7, u can either schedule them or set up a job that executes them on push/merge, thats not the only benefit, there are too many benefits of pipeline execution to list here. I am currently working on the parallelization of my test suites, i've already cut my time from 3h to >50 mins and can go even faster. Something I cant do locally

i see, i will look into it. Thank you. Appreciate your time and wisdom

No problem, we all have to start from somewhere, glad i'm here to share my experience 🙂

Hey guys, I have an interesting topic to discuss

Would you consider the devlopment of Cypress as a part of QA or not?

On the one hand, some might argue that the development of automation frameworks for testing, like Cypress, is a specialized skill that is essential for ensuring the overall quality of software products and is in fact coupled with QA, and it matters a lot that you should have some knowledge and understanding on how QA works for that. On the other hand, others might say it is a normal product development like any other product. In other words, developing testing tools like Cypress isn't QA, and the only relation to QA is simply in marketing and target audience, and you don't need to have much experience or knowledge about QA beyond that to ensure the proper development of such software.

What is your take on this?