chore(data-context): update runSpec mutation to support absolute spec path

[jordanpowell88]

Additional details

While working through the implementation on this issue I ran into a limitation with the current runSpec mutation that was implemented in this ticket. We need the mutation to work by passing in an absolute specPath. This PR adds support for this

Steps to test

Launch the app using yarn dev and open GraphQL. Run the following mutation using an absolute specPath:

runSpec (specPath: "/Users/blah/Desktop/application/cypress/e2e/1-getting-started/todo.cy.js") {
    __typename
    ... on RunSpecResponse {
      testingType
      browser {
        id
        name
      }
      spec {
        id
        name
      }
    }
    ... on RunSpecError {
      code
      detailMessage
    }
  }

How has the user experience changed?

n/a

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[cypress]

5 flaky tests on run #47529 ↗︎

0

5193

77

0

5

Details:

Merge branch 'develop' into jordanpowell88/update-runSpec-mutation
Project: cypress	Commit: d297c64a7f
Status: Passed	Duration: 13:44 💡
Started: Jun 13, 2023 6:19 AM	Ended: Jun 13, 2023 6:33 AM

  commands/net_stubbing.cy.ts • 2 flaky tests • 5x-driver-electron

View Output Video

Test		Artifacts
network stubbing > intercepting request > can delay and throttle a StaticResponse		Output Video
... > stops waiting when an fetch request is canceled		Output Video

  cypress/cypress.cy.js • 3 flaky tests • 5x-driver-electron

View Output Video

Test		Artifacts
... > correctly returns currentRetry		Output Video
... > correctly returns currentRetry		Output Video
... > correctly returns currentRetry		Output Video

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[lmiller1990]

Looks good - testing it now, one question about how we get the path.

[lmiller1990]

I think we can just use path.relative here.

// eg...
path.relative("/a/b", "/a/b/c/d.js") //=> 'c/d.js'

So in this case it'd be:

path.relative(this.ctx.currentProject,specPath)

This way, you won't need to do the calculations to get the correct characters etc.

Quick test:

> curr
'/Users/lachlanmiller/code/work/cypress2/packages/launchpad'
> spec
'/Users/lachlanmiller/code/work/cypress2/packages/launchpad/src/setup/LaunchpadHeader.vue'
>
> path.relative(curr, spec)
'src/setup/LaunchpadHeader.vue'

[jordanpowell88]

Ahhh, yes this was what I was trying to do. Still learning some of these node best practices. Thanks!

[astone123]

Can we update the description of the GraphQL argument for the mutation to say that we're expecting an absolute path?

cypress/packages/graphql/src/schemaTypes/objectTypes/gql-Mutation.ts

Lines 640 to 642 in 45f4b2f

	specPath: nonNull(stringArg({
	description: 'Relative path of spec to run from Cypress project root - must match e2e or component specPattern',
	})),

[astone123]

Looks good 👍🏻

[lmiller1990]

Tested it out, works as expected 💯

[cypress-bot]

Released in 12.15.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v12.15.0, please open a new issue.