When QA teams receive a software build, how do they normally test? Given is the random list of test techniques.... arrange them in order:
- Smoke testing
- Regression testing
- Sanity testing
- Functional testing
Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It only takes a minute to sign up.Sign up to join this community
There are too many factors to be taken into account before selecting the correct testing sequence and sometime not all of the tests you have listed are really needed.
Anyhow, let's imagine the worst case when your QA team receives a new build ready to be tested, I would follow the sequence below:
I think the following link could help you to clarify your doubt: http://www.guru99.com/smoke-sanity-testing.html
Know your product.
Do you have a lot of regression problems? Do regression first. Do you have frequent technical break-ups? Do smoke testing first. It's the opposite : your application is very stable, so it's important to focus on the new features : Do Functional testing first.
The rationale is to go for the low-hanging fruit, which is different on each tree. Minimize your effort for finding the maximum of bugs as early as possible.
1.Always start with Smoke testing it will helpful to determine your new software build is fit to go for next level of testing.
2.Continue with Sanity testing it will helpful to covers the bugs which raised in smoke testing.