cypress-io / cypress

Fast, easy and reliable testing for anything that runs in a browser.

Home Page:https://cypress.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Issue With Skipping Tests Resurfaced in 13.8.1

wakeboardfit opened this issue · comments

Current behavior

We run in an Azure pipeline and after upgrading to 13.8.1, we are experiencing that many tests are just being skipped. This did not happen before and the code did not change outside of a few locator updates and whatnot.
image

When running in 13.6.4, our executions would look like
image

You can see the drop off where we upgraded versions
image

I saw there was an issue that was closed regarding something similar back in version 10.

Desired behavior

Cypress should not just skip tests for not reason.

Test code to reproduce

Everything runs locally so this seems only on Azure. We are running "windows-latest" agent.

Cypress Version

13.8.1

Node version

18.18.2

Operating System

Windows-latest Azure Pipeline

Debug Logs

I will have to get this setup in our pipeline and will add when I can.

Other

No response

@wakeboardfit Are you recording to the Cloud? Could you link to a URL of the run if so?

Could you provide the command you use to run Cypress?

I'm not familiar with anything that would cause this. This is very strange. Can you link to the old issue?

Old issue: #22276

Command: npx cypress run --spec cypress/e2e//**/.feature --config video=true,screenshotOnRunFailure=true --env username=$(USERNAME),insurerUser=$(INSUREDNAME),password=$env:MAPPED_PASS,ls_api_username=$(USERNAME),ls_api_password=$env:MAPPED_PASS,tags=@admitted

We are not using the cypress cloud. I am still trying to figure out how to set the Debug flag in Azure pipeline as it says you need to run in command line (not powershell) and I need to see if I can make that run as admin.

Unless you guys have another way, I am not seeing a way to run Command Line as and Admin in Azure without self hosted agents. I put the debug command in our Power Shell step but I don't believe it did anything and your documentation pretty specifically says not Power Shell.