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
Currently cucumber-js emits testCase messages right before each test case will be run. The CCK defines that they should be emitted together at the start of the test run.
(We're temporarily reordering the envelopes in our CCK test instrumentation at the moment.)
The text was updated successfully, but these errors were encountered:
Consensus from wider group on this was that the ordering around these messages is not important - other implementatons also reorder their messaged to match CCK
Formatters that want to understand the progress of the test run are best served by emitting testCase messages all upfront, and with pickleAccepted and pickleRejected gone we also need it to solve #1579 nicely.
Currently cucumber-js emits
testCase
messages right before each test case will be run. The CCK defines that they should be emitted together at the start of the test run.(We're temporarily reordering the envelopes in our CCK test instrumentation at the moment.)
The text was updated successfully, but these errors were encountered: