Quality Testing

Quality is delighting customers

What should be done if there is a new build and there is not much time left to test?

Hi to all,

What should be done if there is a new build and there is not much time left to test? Any one reply to this question.


Views: 94

Reply to This

Replies to This Discussion

The best solution is to perform a quick Exploratory Smoke Test.
Your aim here is double:
1. Try to find, if they are there, an important number of showstopper bugs that will prompt the project team to stop the project and give you more time to test.
2. Run a quick end-to-end sanity of the product and determine that as much as possible it is ready to move along your process.

In any case, you need to perform a quick risk analysis and make sure not to waste your time by performing tests that go too deep into the functionality.

At least that's what I would do...
Joel, thanks for your quick reply.
Hi Ruchi,

I agree with Mohan.And adding few

1.Testing the blocking issues if any.
2.Rechecking the major bugs.
3.Test the newly added features in the new build.

Best Regards,
Hi Ruchi,

Risk based testing is the best answer but if we need to think anything other than this then as soon as the new build has come we can do a smoke test first if things are fine its better to perform adhoc test but should be done by th testers having good knowledge of the application or in others words should understand the business behind the application.

Hi Ruchi,

I would present myslef this way,

NOT MUCH TIME LEFT TO TEST, assuming minimum of 0 mins and max of 1 day.

0 Mins : Reject the build, speak to your mgr about your in sufficient time to test

1 day : Perform a rigorous Smoke test with a decisive strategy, in context to the current situation.

We have to go for Adhoc Testing
In this case we can,
- Do Ad hoc Testing
- Test only critical areas of the system where there are more chances of getting bugs/errors
I feel that ad hoc wont be a right approach! here we are talking about testing entire build within short time, ad hoc is best to use for testing a functionality and not the entire application.

Considering the less time factor; smoke testing is the better option to look for; also for some of the functionalities we can test it by adhoc testing (but in the end).otherwise ad hc does not guarantee bug catching!


TTWT Magazine





© 2019   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service