Adam Wójcik
> Looks good to me 👍 Thanks, let's wait a bit and if it will not get any traction I will take it
@lhdeveloper we've just done a patch release that should solve this issue. If possible, please double-check with the latest CLI for Microsoft 365 version (v7.8.1) and let us know if...
@mkm17 awesome suggestion: - I am also fine in adding those as additional/new options. We already have commands with a looot of options like [spo site set](https://pnp.github.io/cli-microsoft365/cmd/spo/site/site-set) - what should...
yes that would work. A specific `responses.json` for the test scenario and `config.json` for it as well. This would also mean the `--failure-rate` option will need to respect the mock...
BTW I forgot to mention that if one of those ideas will get approved I am willing to help out and work on those.
> That's a very good question. > > I think that constraining mock response rating to error responses makes sense. > > @Adam-it I'd like to hear your thoughts on...
> Thanks for the additional information, @Adam-it! It helps a lot. In your scenario of QA folks testing apps for API failures, if the mocked response has only 20% chance...
not actually sure what is the default default as I already changed it.🤔 But if it is indeed a browser then yes, it is useless 🙂