Add input capture for allure reporting #135
Conversation
Signed-off-by: PatStLouis <[email protected]>
As long as #134 goes in first. 😁 @PatStLouis is Allure already configured for the weekly report runs? What happens if Allure is turned off or not configured (or goes missing / is down)? |
|
@tminard there is a section about running allure, you just need to initialize the tests with The rest is automagical, just need to browse the report and the payload will be attached to their associated tests. |
|
@BigBlueHat currently this is all configured to be run locally, no standing allure server is setup. I can set one up if we want to explore this further. The way its currently implemented, a user runs the test locally and runs the allure server from the command line The report will be available from the local host. |
| export async function addJsonAttachment(fileName, content) { | ||
| try { | ||
| // Temporarily disable the console log to avoid unnecessary info logs. | ||
| const consoleLog = console.log; |
There was a problem hiding this comment.
@PatStLouis so not sure if we're all 100% agreeing on how to solve this, but do you think this will work:
- create a separate command for allure reports
- that separate command can turn off the consoleLog if needed
LMK if that will work.
This will capture requests and response sent to the issuer/verifier for every call made, useful for debugging.
To avoid this creating unnecessary noise when running with the db reporter, the console logging is disabled when calling the attachment function.