cypress-terminal-report

cypress-terminal-report copied to clipboard

https://github.com/archfz/cypress-terminal-report/blob/78dfd0f7a9801c3146731b7a82328e80d6802f18/src/installLogsPrinter.d.ts#L106 Considering it's marked with a `@default` JSDoc annotation, and all of the other fields on the `PluginOptions` object are optional, it seems like this field should also be optional.

spiltcoffee

Not working when cypress run

9

When we use `outputTarget: cypress-log.json` the file is being created but it overwrites it in between every test. If we use `outputTarget: cypress-log|json` the file is not being created We...

andrewaldasoro

Cannot see GraphQL request/responses in log

3

Hi there! The app that I'm working on uses GraphQL as its main integration. I've enabled the options to print requests and headers for XHR, but still don't see any...

RadomirNowak

Increased flakiness when using plugin

4

Hello! In our application we have several frontend tests using cypress: some end-to-end ones but the majority are component tests. We also use msw to mock all the server requests....

lidiagc

cy.api request as cy:request logs and not cy:command

1

Using cy.request():  I can see cy:request logs on terminal:  But if I use [cypress API plugin](https://www.npmjs.com/package/cypress-plugin-api) (very useful for debug):  I see the request has a cy:command:...

marcrecor

Option to always log response body for cy:fetch

4

If I understand correctly, "cy:request" logs the response body in all cases, but "cy:fetch" only logs the response body if the fetch failed. It would be good to have the...

jeremybeard

Hi there! Love the project and just started investigating using it on our CI. I noticed that when logging to a file, it doesn't log every attempt. I think this...

parkuman

Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3. Commits 74b2db2 3.0.3 88f1429 update eslint. lint, fix unit tests. 415d660 Snyk js braces 6838727 (#40) 190510f fix tests, skip 1 test in test/braces.expand...

dependabot[bot]

Support patterns in outPath for NestedOutputProcessorDecorator

2

Hey there! I tried to minimize changes to implement patterns in output filenames for custom output: `outputTarget: { '*|[relpath]/[basename]/[yyyy][mm][dd]/[basename].[HH][MM][SS].txt': function (allMessages) {..} }` `outputTarget: { '*|[relpath]/[basename].txt': function () {..} }`...

JohannesMunk