When I have less time to test the Product then I will take
these following steps---
1) Sanity or smoke testing
2) Usabilty Testing
3) Formal Functionaltyand GUI Testing
4) Walkthrough with the Prduct
etc......

I will do the following testings
1. Sanity testing
2. Adhoc testing for functional, Integration & system 
testing
3. UAT

At that time you can prefer Adhoc testing (Testing the 
product of system without any documents)

This is very know fact that Testing has always a time 
constrain. But its always sufficient to complete before 
time provided u work little harder. If in some situation 
when time is really not enough to run all the Testcases 
then we can execute Smoke Testing. Smoke testing the 
execution of the basic testcases of the application.

at this situation we have to perform adhoc testing

If I had very less time for testing the application I will
do adhoc testing,exploratory testing,sanity and UAT .This
will be enough for testing,
pls correct me I am wrong
Muralidharan 
dharanmu@yahoo.com

Murali u r absolutely wrong b'caz when u have time to do 
those many types of testings then istead of that u can do 
normal testing only ... think over it

Regards,
Surya

I that case the smoke testing would be best practice. 
Sanity testing also does not make any sense as it involves 
through validation testing. 
Exploratory is done when there is no documents for the 
system based on which you can prepare prepare your test 
cases.  

Suggestions are welcome

Regards

i think better option is to do "Risk Analysis", so that we 
can complete testing in lesser time

For more details contact me

Hary

There should be enough and sufficient time tio carry any 
kind of testing ,if there is no such time constraint we can 
check functionality and Usability testing as we do in War 
room having only the basic feature of the fuctionlity

In this type of situations we have to analyse the major 
functionalities in that application as per the client .
Then we have to go for adhoc testing or exploratory testing

Best one is sanity testing

1. List out areas/functionality to be tested and not to be tested from user perspective. 
2. Set priorities for test cases to be executed.
3. Perform  UAT.

When you has less time to do testing,you can do your 
testing if you have all test case ready with you.Just 
execute all test cases(Automated testing)you will get 
results.

Specically for manual testing you should do smoke testing 
to check all links.After which whichever module or 
functionality you want to release check it as per the 
requirement specification instead of going in detail 
scenario,if it works the enough.

Ad-hoc testing and exploratory testing are best ways to test
effectively when there is less time. Automated tests could
be used in parallel with the above mentioned tests to save time.