Assertions run outside of a test should be handled properly in Cypress (not throw internal errors)

[jennifer-shehane]

Current behavior:

When you write assertions outside of a test (failing & passing), Cypress throws an error "cannot read 'id' of undefined"

This is being thrown when attempting to create the logs for a test when the runnable is undefined.

Furthermore, Cypress attempts to iterate over the stylesheets of the current document. Since there is no document, this throws an error that it "cannot read 'stylesheets' of undefined"

Desired behavior:

When you write assertions outside of a test (failing & passing), Cypress should handles these correctly.

• Passing assertions should pass
• Failing assertions should warn that you have a failure outside of a proper test - that you should probably write a test to put your assertions into.

Steps to reproduce: (app code and test code)

1. Create a specfile within cypress/integration
2. Write expect(true).to.be.true to test the passing behavior.
3. Write expect(true).to.be.false to test the failing behavior.

Versions

Cypress 3.2.0

[cypress-bot]

The code for this is done in cypress-io/cypress#3927, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 3.3.0.