WHAT IS SMOKE, SANITY AND REGRESSION TESTING? HOW TO CI/CD WITH THEM?
WHAT IS SMOKE TESTING? IT IS A TESTING METHOD THAT VERIFIES WHETHER A DEPLOYED SOFTWARE BUILD IS STABLE OR NOT. IT MAKES SURE THAT THE KEY FUNCTIONALITIES OF AN APPLICATION ARE WORKING FINE. QA TEAM GETS THE NECESSARY CONFIRMATION THROUGH THIS TESTING METHOD IN ORDER TO PROCEED WITH FURTHER ROUNDS OF TESTING. ON EACH BUILD, A MINIMAL SET OF TESTS ARE RUN IN ORDER TO TEST THE SOFTWARE FUNCTIONALITIES.
WHAT IS SANITY TESTING? AFTER THE SOFTWARE BUILD IS RECEIVED, SANITY TESTING IS PERFORMED TO MAKE SURE THAT THE CODE CHANGES THAT HAVE BEEN INTRODUCED ARE WORKING AS PER THE REQUIRED EXPECTATIONS. THE APPLICATION’S FUNCTIONALITY IS VALIDATED. WHEN THERE IS AN IMMEDIATE REQUIREMENT OF PRODUCTION DEPLOYMENT FOR A CRUCIAL BUG THAT NEEDS TO BE FIXED, THEN SANITY TESTING IS PERFORMED ON THAT BUILD.
WHAT IS REGRESSION TESTING? IT IS A TESTING METHOD THAT MAKES SURE THAT ANY CHANGES OR UPDATES DONE TO THE CODE DO NOT ALTER OR MODIFY THE EXISTING FUNCTIONALITIES OF AN APPLICATION. IT IS GENERALLY PERFORMED WHENEVER THERE ARE CHANGES BEING MADE TO THE CODE. PARTIAL OR FULL SELECTION OF TEST CASES THAT ARE ALREADY EXECUTED IS RE-EXECUTED TO MAKE SURE THAT THE EXISTING FUNCTIONALITIES ARE WORKING AS EXPECTED.
LEVERAGING CI/CD THROUGH THE IMPLEMENTATION OF SMOKE, SANITY AND REGRESSION TESTING: TWO JENKIN JOBS NEED TO BE CREATED. ONE IS TO RUN AUTOMATION CODE AND THE OTHER ONE IS FOR CODE DEPLOYMENT. THE AUTOMATION JENKINS JOB NEEDS TO BE MADE A DOWNSTREAM JOB. NOW, WHEN THE CODE IS BEING DEPLOYED, THE TEST SUITE WILL AUTOMATICALLY RUN AND THUS SMOKE, SANITY AND REGRESSION TESTS WILL RUN AUTOMATICALLY.