07-25-2021 1:32 PM
07-25-2021 6:54 PM
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/fb9bf93de5534a43862558adf6...
cheers!A
07-26-2021 12:23 AM
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)
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