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
context('when editing or creating an issue',()=>{context('when the user is logged out',()=>{context('when editing the issue',()=>{it('tells the user they must log in',()=>{// test goes here})})})})
Logs printed to file partially identify the test being run, showing the name of the test but not the names of any containing context() blocks:
tests/e2e/integration/issue_form_spec.js:
tells the user they must log in
cy:request (K): http://backend:3000/api/v1/rails/reset_db
Status: 200
Response body: {
"errors": []
}
But logs printed to console don't give any identification at all:
This makes it difficult to find which test a log relates to, unless every test starts with a cy.log() statement giving its name, which clutters the test files unnecessarily. Would it be possible to have the name of the test output to console as well as to file, and context names output as well as test names in both cases?
(Now that I think about it, it may be a difference between onFail and always rather than logging to console vs logging to file… I've also just noticed that the tick emoji has been changed to a K when outputting to file — is that intentional?)
The text was updated successfully, but these errors were encountered:
I'm using cypress-terminal-report 2.4.0 with Cypress 5.6.0 in GitLab CI, using this config:
and this test:
Logs printed to file partially identify the test being run, showing the name of the test but not the names of any containing
context()
blocks:But logs printed to console don't give any identification at all:
This makes it difficult to find which test a log relates to, unless every test starts with a
cy.log()
statement giving its name, which clutters the test files unnecessarily. Would it be possible to have the name of the test output to console as well as to file, and context names output as well as test names in both cases?(Now that I think about it, it may be a difference between
onFail
andalways
rather than logging to console vs logging to file… I've also just noticed that the tick emoji has been changed to a K when outputting to file — is that intentional?)The text was updated successfully, but these errors were encountered: