Be able to run a single test by interacting with it in the Browser

Current behavior:

When you want to run only one spec/context, you must supply .only in code

Desired behavior:

Each test and context should have a deep link which would be interpreted by cypress as the “only”. This way, code changes do not need to be made to demonstrate the running of many tests (as currently all tests cannot be run at once). This is how we have used similar test suites, like jasmine, to run a specific suite/spec in the browser without code modifications.

[G1itcher]

100% putting my vote behind being able to run a single test. If I’m trying to edit a single test, it doesn’t make sense to run all of the tests in that spec

[jaredtmartin]

It would simply be faster and more convenient to be able to click on a single test and have it run. That’s what one expects to happen intuitively.

On Dec 26, 2018, at 5:44 PM, Gleb Bahmutov [e-mail] wrote:

There is eslint plugin that checks “only” and a stand alone utility I wrote called “stop-only” that can catch stray only left in the source code

Sent from my iPhone

On Dec 26, 2018, at 18:03, sendittokeith [e-mail] wrote:

That is a better work around, but not a solution since you could risk forgetting to remove the .only - but thanks, at least that work around is better 😃

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cypress-io/cypress/issues/925#issuecomment-450042085, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYGCvB-mqWYvA8IrkpzsPVbQOJy6tAWks5u9An1gaJpZM4QhfgB.