Wait for step to complete execution before jumping into next step

[avinashk14]

Hello,

I've been trying for one step definition to complete its execution (along with all its back-end calls) before jumping into the next step definition and executing its line, any help is greatly appreciated.

Example Scenario:

Scenario: Test scenario
    Given I create a resource
    Then I should have the resource

Step definitions:

Given('I create a resource', function() {
  setTimeout(() => {
    console.log("I create a resource");
  }, 1000);
})

Then('I should have the resource', function() {
  console.log('I should have the resource')
})

What I am looking for is for the step 'I create a resource' to wait for all its lines executed and then the next step 'I should have the resource' executes.
From the console log, I expect to see: "I create a resource", " I should have the resource"; what I actually see: "I should have the resource", "I create a resource".

Is there a way for the step definition to wait? - Reason for asking is because we have a lot of scenarios where resource creation/fetch is the first step and the subsequent steps check on the resource, but they fail because the create/fetch step doesn't wait for the back-end call to finish.
(I'm at cypress v12.17.4 and cypress-cucumber-preprocessor v18.0.4)

[badeball]

Use Cypress commands for resource creation. IE. cy.request(..) and you'll see that steps are executed consecutively. Alternatively you can wrap your code in promises, https://docs.cypress.io/api/utilities/promise.

[badeball]

Your example passes as far as I can see.

[badeball]

You also don't need a wrapper-promise in this case, the following is fine.

When('I create a resource', function() {
  cy.request({
    method: 'POST',
    url: 'https://19lq5.wiremockapi.cloud/test_post'
  }).then((res) => {
    cy.wrap(res.body.message).as('message')
  })
})

Then('I should have the resource', function() {
  expect(this.message).to.eq('Created')
})

[avinashk14]

Thanks, I will try to work around your suggestion.

[avinashk14]

To note: the runable example mentioned above passes on Chrome v115, but fails on Electron v106 and Firefox v116, not very sure why it behaves differently on different browsers.

[badeball]

Remove async from your function, it's not really asynchronous in the traditional sense.