When the application is ready for testing ?

When the application is ready for testing but there no time as customer needs the application very soon, what is the solution for testing

Questions by lakshmip.yaganti

Showing Answers 1 - 8 of 8 Answers


  • Aug 11th, 2014

When all manual testing process in place as per expected result and tested twice manually. The application build should be stable.

  Was this answer useful?  Yes


  • Aug 25th, 2014

once the developer completed the coding , the developer do the one round of testing called WBT, & then it is given to test engineers for testing,

For testing we need to have
1) application
2)customer requirements
3) modules should be assigned


  • Aug 28th, 2014

Once the development is done and pushed into the build ,the testers will be notified that it is ready for testing.
Before that from testing side :

1)Test environment should be ready.
2) Test cases should be ready.
3)Test data should be ready for use.

  Was this answer useful?  Yes


  • Nov 14th, 2014

Development is completed and done wit Unit Testing

  Was this answer useful?  Yes


  • Dec 4th, 2014

Hi Girish, Need to make your answer clarified. I shall explain: For every Phase of Testing to be executed in STLC, there will be Entry Criteria an Exit Criteria as per the Test Approach / Plan you follow it:

So, in order conduct the very first Testing Type from the QA plate (default to any Project / Product) is Smoke / Sanity (How ever you take it). Now coming to Sanity testing execution: Entry Criteria is: 80% of Unit / Integration Test Cases conducted by Dev Team should be Passed.

Otherwise, as per the process, the build will not be accepted by the QA Team. Setting up the Test Environment, Test Cases, Test Data comes next. You can make these as Pre-conditions but not the immediate source. After execution of Smoke testing, the exit criteria should be 80% atleast to start next phase of Testing, say (Functional Testing). Hope you had a clear understanding now.

  Was this answer useful?  Yes


  • Dec 16th, 2014

According to company . first the tester goes to the developer environment conduct initial test(B.V.T or B.A.T) ,smoke test he will check whether the build is stable or not. then testers conduct sanity test and check the functionality the build is designed according to the customer requirements or not,by executing the test cases.

  Was this answer useful?  Yes

Sachin Kumar

  • Feb 2nd, 2015

once Application is Ready But customer needs the application soon .... then we need to go for Ad-hoc Testing...

  Was this answer useful?  Yes


  • Jul 7th, 2015

For every Project All test cases are prioritized into P1, P2, P3....based on differnet factors like KBFs(Key business Flows), Complex areas, High Risk Areas, Frequent defect causing areas etc...so when ever we wont have extra time we try to cover P1 and P2 first and if time permits will go for P3 as P3 max contains static stuff, less complex functionality, and similar functionality that is covered in P1 and P2s, etc...

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.


Related Answered Questions


Related Open Questions