Assign the Severity and Priority for Validation Bugs.
one important Question is which testing is done first from sanity and smoke testing. Explain this in brief.
Assign the Severity and Priority for Validation Bugs.
one important Question is which testing is done first from sanity and smoke testing. Explain this in brief.
Hi,
The answer to the question would entirely depend on the nature / type of validaiton bugs.
Incase the functionality is working properly but a validation of a business rule is missed, it would considered as a functional bug with High Severity and High priority as it impacts Business.
Incase we are dealing with field level validations, we would still decide on basis of validation importance. For instance -
1) In a Banking Application, If it is a validation check to ensure that Interest Rates should be auto-fetched from MasterData which does not happen, it would be a bug with Medium Severity and Medium Priority
2) Incase we are dealing with Alphanumeric / Numeric character entry validations, we would consider that as Medium Priority / Low severity.
Difference between Smoke and Sanity Testing.
Most of the companies consider using the terms interchangably with almost similar meanings - Testing an application build to ensure whether it is stable enough to be considered for further testing. But there are a very few minute lines on which we can differentiate them -
Answer to your question is - Smoke test is carried out first. I have tried explaining the actual process of both below.
Smoke Test: .
When a build is received, a smoke test is run to ascertain if the build is stable and it can be considered for further testing.
Smoke testing can be done for testing the stability of any interim build.
Sanity Test.
Once a new build is obtained with minor revisions, instead of doing a thorough regression, a sanity is performed so as to ascertain the build has indeed rectified the issues and no further issue has been introduced by the fixes. Its generally a subset of regression testing testcases.
Mostly smoke tests are scripted / Automated but Sanity tests are not.
A smoke test is not in depth and only esnures that all specified functionalities are working properly in overview.
A sanity test is generally done in depth and is kind of a narrow Regression test.
Cheers...
HI,
Both the Sanity and Smoke test are done only by the Tester not by the developer.
Sanity testing will be done when the build is deployed first time into the testing after the coding part. While doing sanity test, both the negative and postive test scenarios are carried out.
Smoke testing is done for the subsequent releases of the build. Here the major functionalities are tested inorder to validate the stability of the build being deployed.
Both of them are done only at the Tester's end. Only Unit testing is done at the developers end.
Regards,
Ganesan
Hi,
Smoke Testing is an initial level of testing just to make sure if the system is stable and can be considered for further level of testing or not
Sanity Testing is a subset of regression testing and usually done after the build is received,just to make sure if already raised defects are closed or not.One can apply simple sanity checks at different points and test.
Thanks
Regards,
Brijesh Jain
---------------------------------------------------------
Connect with me on Skype: jainbrijesh
Google Plus : jainbrijeshji
Hi,
Smoke testing may also be done by the developer before the build is deployed to the QA Team for testing. But after the build is deployed the formal testing kicks off only with the smoke test done by the testing team.
Regards,
Ganesan