done

Did something change in Cypress 12 with regards to how cy.request works? I'm trying to upgrade to v12 now and noticed that a majority (maybe all) of my usages of cy.request have a green non-filled circle in the test runner command log. According to the docs this implies that the request was mocked by using cy.intercept. But I don't think we have a single use of cy.intercept in any of our tests.

Hmm, I went back to v10 to compare. It seems to also show cy.requests as empty circles. Maybe this "empty circle implies intercept" only applies to normal requests the browser makes when interacting with the page?

https://docs.cypress.io/api/commands/request#Command-Log This page shows a blue circle for cy.request though. That's not what I see. Is this screen shot outdated?

Cypress is not showing the code line number and snippet on error in command log anymore. How can I enable it

As I understand it, when you use cy.request() to make an HTTP request, Cypress actually uses an instance of XMLHttpRequest under the hood to make the request. And when Cypress detects that an instance of XMLHttpRequest has been created by cy.request(), it intercepts that instance of XMLHttpRequest and modifies it. so that it can track the request and response, and display it in the Cypress test runner. This is why you see the "green non-filled circle" in the test runner when using cy.request(), even though you have not explicitly used cy.intercept().

Thanks for the explanation. I did notice that my problem was unrelated to the use of cy.request.

How can I group cypress results by folder in the command line?

Hi, you can use flag --group in CLI: https://docs.cypress.io/guides/guides/command-line#cypress-run-group-lt-name-gt

Is anyone here working on projects for/with organizations or companies that address climate change?

if you are, and need any personal / individual / private cypress testing support, I will do it for free for you

How to enable IntelliSense in visual studio when we download cypress, not from NPM?

GoodDay everyone! I am cofounder of QA Tech tribe**(QA Community Hub https://pk.linkedin.com/company/qa-tech-tribe)** we are planning meetups and online sessions for our Pakistan🇵🇰 community . I need some volunteer speakers for our community who can train online and share knowledge for automation testing tools and also manual testing training for freshers. kindly email me if anyone of you want to collaborate for training and meetup sessions at qatechtribe@gmail.com or umaranjum2018@gmail.com Looking forward

@everyone

Thanks Gleb, I heard back from an organization that is interested. I will connect you once I receive confirmation.

Why do I have the "New Member" role? I've been here for a hot minute now. Any way to remove that? Are there other, cooler roles I should by trying to earn?

Also what is the 🎉 role?!?

Gone! Good question, The role serves 2 purposes: 1. it give members more context on the community journey of other. 2. helps our team identify who may still be "learning the ropes"

No, I know what the "New Member" role is for. I'm asking about the other role I have which is just the party emoji.

ohh got it, it indicates that you use Cypress cloud. that tag can't be applied to users anymore. removed it from onboarding question

Hello! What is your approach when you create new tests? Let's say that you have 50 tests so far, and you want to create a new one. Do you code/debug the test case in a different file, or do you use comments to stop the execution of the already made tests, or maybe another way?

Hi guys, is anybody have problem with GitHub action? I have problem that execution of my tests takes longer using GitHub action than execution inside VisualStudio code. For paralelization I'm using this script: name: Parallel Cypress Tests on: push: branches: - 'main' schedule: - cron: '30 7 * * *' jobs: test: name: CS Cypress tests runs-on: ubuntu-latest strategy: fail-fast: false matrix: # run 5 copies of the current job in parallel machine: [1, 2, 3, 4, 5] steps: - name: Checkout uses: actions/checkout@v2 - name: Add hosts to /etc/hosts run: | URLOFMYCOMPANY - name: Cypress run uses: cypress-io/github-action@v4 with: command: npm run run:dev

Hi @powerful-journalist-49461 I don't think it will make any difference to the speed, but I notice you're not using the latest version of cypress-io/github-action@v4. The latest version is v5. Also you will be getting deprecation warnings from actions/checkout@v2 until you move to v3. Which version of Cypress are you using?

It sounds like you are comparing the speed of running on a GitHub-hosted runner compared to running on your local machine. Is that correct?

can anyone recommend cycpress course for freshers

Hi Mike, I'm using "cypress": "^12.5.1", no I'm comparing speed of running inside of my Visual Studio terminal (cypress run) with speed of running on GitHub action

your actions are running on a VM smaller than your local machine

sorry gleb I'm not sure that I understood you, if you think on this I just changed it actions/checkout@v3 github-action@v5