As a business begins ramping up their governance model for proving “accuracy” and “completeness” as part of production deployment…
…it is important that one maintains ones sanity!
Has anyone thought about creating a package to automate the collection of this visual evidence and documentation, while a process is running?
There are many components to governance documentation, so this is specific to “accuracy” and “completeness” for UAT (and QA too).
What ideas do you have to automate this, if any?
Should this be one workflow that triggers your process and in parallel can somehow detect when to provide the visual evidence, maybe through various arguments?
Or, should this be many small components which you place in key locations in your process… maybe this is a more tedious approach?
I’m thinking the more challenging part is collecting the visuals and proof. Then, once everything is collected, just generate the documents to comply with your governance model.
— template or config of governance model to provide versatility
— store transactions which were tested
— get Robot name, Env name, and timestamps of job runs (for QA)
— trigger on additional robots which have not been tested on yet (for QA)
— show results of job runs either by screenshot or from logs somehow (for QA)
— get manual proof of same transactions (can the robot screenshot itself or has to be manual?)
— get results data
— organize manual proof with automated results so a comparison can be made easily
— generate email for approval from business user
Testing Logs are something that needs constant attention when patches or process changes are made, and this can get repetitive. It’s also human nature to take the path of least resistance, so accuracy and compliance is not sustained as well as it should be.
So, please share any other features that could be useful for this idea… or if something like this has been created which could be referenced.
Thank you for taking the time to read and discuss. You know, at some point, we need to get some savings from ourselves the developers and governance engineers…