| || |
Missed Front End Build !
Recently in a patch release when the sprint was over, patch moved to UAT for a regression test. At the end of regression test, its found that Front End deployment was failed when moved to UAT.
Now that has been corrected and complete patch is moved?
What level of regression needs to be executed again?
Depends mainly on how controlled your deployment process is, and how well your code merging process is.
For example, if your deployment requires manual file copying. Full regression is needed to make sure each change makes it. If you use packaged deploy, then you just need to verify the piece of code made it by verifying just a few touch points.
On the topic of code merging. This is complicated. You'll have look at the following..
1. Is the code change isolated? -- if it's merged with some other code changes, you'll need to also test around those boundaries as well.
2. Is the code change exactly the same? Was the patch applied not the same as the production version of that same code?
3. Was the patch applied to a rebase or a merge? A rebase is safer, however you have to retest around the patch. If it's a merge, you'll have to retest everything done from the branch point to when the branch is merged.