[Request] Add pretty formatter plugin #810
Comments
|
No such plans exist, albeit it'd be nice to have. I however don't have time to work on this. Furhermore, I reckon it'd be pretty major work, as one can't simply just integrate cucumber-js reporters into cypress, it'd more likely require a complete re-implementation. |
Messages are no longer lingering in the runtime, but passed along to the backend using tasks immediately. This is a prerequisite for the following issues: - 810 [1] - 824 [2] - 944 [3] This is not to say that these will be fixed shortly or even at all, but at least now it will be remotely possible. Furthermore, this removes any doubt regarding whether reports work in interactive mode. The experimental flag simply turns out to be too broken [4-5]. Interactive mode is now detected and reports turned off. Lastly, detecting interactive mode is a somewhat broken feature [6]. The workaround (using `isTextTerminal`) is only available in Cypress v10 and beyond. Thus is Cypress v9 now unsupported. [1] #810 [2] #824 [3] #944 [4] cypress-io/cypress#18955 [5] cypress-io/cypress#26634 [6] cypress-io/cypress#20789
Messages are no longer lingering in the runtime, but passed along to the backend using tasks immediately. This is a prerequisite for the following issues: - 810 [1] - 824 [2] - 944 [3] This is not to say that these will be fixed shortly or even at all, but at least now it will be remotely possible. Furthermore, this removes any doubt regarding whether reports work in interactive mode. The experimental flag simply turns out to be too broken [4-5]. Interactive mode is now detected and reports turned off. Lastly, detecting interactive mode is a somewhat broken feature [6]. The workaround (using `isTextTerminal`) is only available in Cypress v10 and beyond. Thus is Cypress v9 now unsupported. [1] #810 [2] #824 [3] #944 [4] cypress-io/cypress#18955 [5] cypress-io/cypress#26634 [6] cypress-io/cypress#20789
Messages are no longer lingering in the runtime, but passed along to the backend using tasks immediately. This is a prerequisite for the following issues: - 810 [1] - 824 [2] - 944 [3] This is not to say that these will be fixed shortly or even at all, but at least now it will be remotely possible. Furthermore, this removes any doubt regarding whether reports work in interactive mode. The experimental flag simply turns out to be too broken [4-5]. Interactive mode is now detected and reports turned off. Lastly, detecting interactive mode is a somewhat broken feature [6]. The workaround (using `isTextTerminal`) is only available in Cypress v10 and beyond. Thus is Cypress v9 now unsupported. [1] #810 [2] #824 [3] #944 [4] cypress-io/cypress#18955 [5] cypress-io/cypress#26634 [6] cypress-io/cypress#20789
Messages are no longer lingering in the runtime, but passed along to the backend using tasks immediately. This is a prerequisite for the following issues: - 810 [1] - 824 [2] - 944 [3] This is not to say that these will be fixed shortly or even at all, but at least now it will be remotely possible. Furthermore, this removes any doubt regarding whether reports work in interactive mode. The experimental flag simply turns out to be too broken [4-5]. Interactive mode is now detected and reports turned off. Lastly, detecting interactive mode is a somewhat broken feature [6]. The workaround (using `isTextTerminal`) is only available in Cypress v10 and beyond. Thus is Cypress v9 now unsupported. [1] #810 [2] #824 [3] #944 [4] cypress-io/cypress#18955 [5] cypress-io/cypress#26634 [6] cypress-io/cypress#20789
|
I'm happy to announce that this is implemented in v18.0.0. Read the docs for information on how to enable it. This is still fairly experimental and feedback is welcome. |
|
Is it possible to use this if running on version below Node 18? - that is could this be a package you could install in isolation - or is it only supported on versions > Node 18 - we are currently tied to Node 16 but would like to use this if possible. If not I suppose we need to upgrade to Node 18 which might facilitate this move |
The v18-requirement comes from use of |
Do you have any plans to add the pretty plugin to this processor according to the below package? It would be nice to monitor the scenario steps via the CLI.
https://github.com/cucumber/cucumber-js-pretty-formatter
The text was updated successfully, but these errors were encountered: