CypressError: Cypress test was stopped while running this command

[giovanihoff]

Hi. Please, considering the following example code:

export const create = async function(arg) {
    return new Cypress.Promise((resolve) => {
        cy.request({
            method: 'POST',
            url: Cypress.env('URI'),
            headers: {
                'Authorization': 'Bearer ' + arg.access_token,
                'Content-Type': 'application/json',
                'X-Brand': arg.x_brand,
                'X-key-id': arg.x_key_id,
            },
            body: {
                associateIdentify: {
                    id: arg.id,
                    user: arg.user
                },
                retry: false
            },
            failOnStatusCode: false,
        }).then( (response) => {
            resolve(response)
        })
    })
}

import * as request from '../requests'

describe('Test - Example', () => {

    beforeEach(() => {
        cy.fixture('mobile_token_activation_data').then(function (data) {
            this.data = data
        })
    })

    afterEach(function() {
        if (this.currentTest.state === 'failed') {
          Cypress.runner.stop()
        }
    })

    it('Test - Creating', async function() {
        let arg = this.data
        let response = await request.create(arg)
        expect(response).to.have.property('protocol')
        cy.wrap(response.protocol).as("protocol")
    })

})

Executing by the command "npx cypress open", it runs successfully. But, executing by the command "npx cypress run" (CI), returns "CypressError: Cypress test was stopped while running this command.". Why can't we have call repurpose with Cypress? Why can't we have code reuse in this case? Please, how can we have synchronous execution in this case?

[BrunoReisOliveira]

I am facing the same problem. This is very important to resolve. I would like to say thank you for any help!

[giovanihoff]

Resolved using https://docs.cypress.io/api/cypress-api/custom-commands. Please, can you close the issue. Thank you.

[woochica]

@giovanihoff can you help me understand why did it resolve your problem?

[prostko]

I am facing an issue where headless mode fails with the ambiguous error above, Cypress DEBUG shows no issues. Cypress simply stops running.

[vladttt1123]

facing the same error, after migrating form cypress 10.2 to 13.2

[DarienYang]

same error here, is there anyone have a solution for this? cypress version: 12.17.1

[DarienYang]

I end up with a solution without async/await.
Following are psudo code (may not run successful directly) leveraging origin post.

export const create = function(arg) {
    return cy.request({
            method: 'POST',
            url: Cypress.env('URI'),
            headers: {
                'Authorization': 'Bearer ' + arg.access_token,
                'Content-Type': 'application/json',
                'X-Brand': arg.x_brand,
                'X-key-id': arg.x_key_id,
            },
            body: {
                associateIdentify: {
                    id: arg.id,
                    user: arg.user
                },
                retry: false
            },
            failOnStatusCode: false,
        }).then( (response) => {
            expect(response).to.have.property('protocol')
        })

describe('Test - Example', () => {

    beforeEach(() => {
        cy.fixture('mobile_token_activation_data').then(function (data) {
            this.data = data
        })
    })

    afterEach(function() {
        if (this.currentTest.state === 'failed') {
          Cypress.runner.stop()
        }
    })

    it('Test - Creating', function() {
        let protocol
        let arg = this.data
        request.create(arg).as('response')
        cy.get("@response").then((response) =>{
            protocol = response['protocol']
        })
    })
})

if you need to make sure a request completed then execute next command you could do something like:

request.something()
cy.then(() => {
    put whatever you need after the request.
})

It might not the best solution but it's the way I resolved the problem.

[shyambi]

I am also facing the same issue.
Cypress community, can you please help us here? This is critical issue and a blocker for us.

[itsalaidbacklife]

I stumbled upon this issue after hitting the same error and in my case it was a problem where my application was making a request that hung. I think it might be a timeout? Or an issue where cypress forcibly stops commands that return promises that won't resolve?