Regression testing in GRC

nishanth_chinthala2 — Sun, 25 Jul 2021 12:32:31 GMT

How to create Test scripts for regression testing in GRC

Re: Regression testing in GRC

amontella96 — Sun, 25 Jul 2021 17:54:43 GMT

nishanth.chinthala2 man of few words hun?

reading in my crystal ball didn't help, so i paste here some interpretation of your question:

- the concepts https://blogs.sap.com/2014/05/28/regression-testing/

- the how to with coolest automation https://blogs.sap.com/2019/07/04/robotic-test-automation-brings-ends-to-scripting/

- the how to with SolMan automation https://help.sap.com/viewer/fbc7b5ecf5094fe0b6a2eb966160008f/7.2.06/en-US/fb9bf93de5534a43862558adf678e5bc.html

cheers!A

Re: Regression testing in GRC

Colleen — Sun, 25 Jul 2021 23:23:32 GMT

I would first look at any existing test scripts that you have

Regression testing is effectively verifying that you haven't broken what was already working. When putting together regression tests you need to consider (and probably a heap more)

Full scope of functionality that is currently in user - i.e. this is the maximum scope of regression testing
What is being changed - what are you doing? Support Packs, Upgrade, new configuration, etc? Help you determine how much regression testing. E.g. if it's support packs then I would test it all. If it was a new request type in user provisioning, I would look at testing access request module but less inclined to test risk analysis, business roles management, and emergency access management
The criticality of your solution and processes - testing takes time. You may need to prioritize certain testing over others. E.g. high volume of user requests versus weekly compliance checks. Both need to be regression tested but you have a user provisioning issue on day 1 then you will have a look of incidents to respond whilst weekly compliance checks give you more time to resolve.

If test scripts exist (with dedicated test users limited to their security authorisation) then you need to focus on the scope of test - do you test all, most, some, or key items only. If you have no existing scripts then I would look at converting any end user manuals and procedures into scripts and look at positive/negative tests.

Again, focus is performing tests to confirm the change did not break what was already confirmed to be working

Good luck with it all! If you want more assistance, it would help that you provide more information.

Cheers

Colleen

topic Regression testing in GRC in Application Development and Automation Discussions

Regression testing in GRC

Re: Regression testing in GRC

Re: Regression testing in GRC