Brian Mann

I just looked it up and apparently there is already a `document.evaluate` which will take an `xpath`. You should already be able to do this with Cypress with a custom...

@bryantabaird went back through to review comments. Per my comment here: you can use `cy.contains()` rather than xpath if you want to select an element or a parent element by...

What I'm saying is that with Cypress **you already have** native DOM access to your window/document. Just use the code you wrote just now and put it in a custom...

This should be possible to do, but it's not immediately obvious or easy. **Thoughts / Concerns** - To date we haven't built in any specific API's that only work with...

In [`0.20.0`](https://docs.cypress.io/guides/references/changelog.html#0-20-0) this became: ```javascript Cypress.on('fail', () => { Cypress.stop() }) ```

I didn't try it, but `Cypress.stop()` does do more things than aborting just the runner. Try this: ```javascript Cypress.runner.stop() ``` That's where the abort code moved to, but even this...

Nope. PR's are welcome.

Yes we've waited to implement this feature due to how aborting is much more complex now. We likely need to allow for multiple abort strategies ```js abortStrategy: 'spec' | 'run'...

Good point. I think perhaps instead of mixing these API's - and dealing with the consequences of SingleChooser having a chooseNone but not a chooseAll - I think I should...

Yes, this makes sense. I should override the model's sync and slice the chosen attribute out so it's not sent to the backend.