You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using npx find-cypress-specs --tagged @foo, the passed in tag is ignored and the entire list of specs is returned.
npx find-cypress-specs --tags returns the expected # of tests in the output for @foo
npx find-cypress-specs --names --tagged @foo returns the expected list of specs with the test names
But I'm only interested in building a list of spec files themselves, not the test names associated with the tags. It would be really helpful to be able to build a list of spec files, based on a tag, to pass into Jenkins.
The text was updated successfully, but these errors were encountered:
Hmm does sound like a bugSent from my iPhoneOn Jan 20, 2023, at 09:46, gricid ***@***.***> wrote:
When using npx find-cypress-specs --tagged @foo, the passed in tag is ignored and the entire list of specs is returned.
`npx find-cypress-specs --tags' returns the expected # of tests in the output for @foo
npx find-cypress-specs --names --tagged @foo returns the expected list of specs with the test names
But I'm only interested in building a list of spec files themselves, not the test names associated with the tags. It would be really helpful to be able to build a list of spec files, based on a tag, to pass into Jenkins.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
When using
npx find-cypress-specs --tagged @foo
, the passed in tag is ignored and the entire list of specs is returned.npx find-cypress-specs --tags
returns the expected # of tests in the output for @foonpx find-cypress-specs --names --tagged @foo
returns the expected list of specs with the test namesBut I'm only interested in building a list of spec files themselves, not the test names associated with the tags. It would be really helpful to be able to build a list of spec files, based on a tag, to pass into Jenkins.
The text was updated successfully, but these errors were encountered: