EMERGING TRENDS IN SOFTWARE ENGINEERING
DEVOPS
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
CreateOc, Deploy Dev, Smoke Test
|
|
|
CreateOC, Deploy, Smoke Test, User Validation, Rollback Dev
|
|
|
CreateOC, Deploy, Smoke Test, User Validation, Rollback
|
|
|
CreateOC, Deploy, Smoke Test, User Validation, Rollback, HotFix
|
Detailed explanation-1: -Configuration smoke test-validates the configuration before deployment. Some basic sanity checks can prevent the application from starting with the wrong settings. Infrastructure smoke test-checks various elements that can disrupt the deployment or prevent the application from starting up once deployed.
Detailed explanation-2: -As we have said earlier, smoke testing should be done immediately after a new deployment is made while ensuring consistent runs at perfect intervals. If you have a well-defined CI infrastructure or build procedure in place, the initial implementation for smoke testing is easy to pursue.
Detailed explanation-3: -Select Test Cases. The first thing you want to do is identify the test cases that you want to analyze. Build Smoke Tests. Once you identify the smoke tests you want to run, the next step is to write test scripts. Run Smoke Tests. Make Changes. 25-Apr-2022