When QA teams receive a software build, how do they normally test? Given is the random list of test techniques.... arrange them in order:

  1. Re-testing
  2. Smoke testing
  3. Regression testing
  4. Sanity testing
  5. Functional testing
  • You should take a look at your papers...
    – bish
    Commented Dec 4, 2015 at 7:13
  • 2
    sounds like a homework/class assignment Commented Dec 4, 2015 at 16:14

3 Answers 3


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:

  1. Smoke testing
  2. Sanity testing (to be skipped when the software is not stable enough)
  3. Regression testing
  4. Functional testing

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.

  1. Do Functional testing and regression testing

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.