Answer / pramod

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.

Answer / lakshmi v

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.

Answer / vishwa

Risk based approach for testing sounds more meaningful in these situations. As its(Risks) the one which we test for. Identify the Risky areas from Buisness perspective, user perspective, application perspective.

Answer / madhukar9823

If we doesn't have enough time for testing then it is
completely based on risk management factor, we have to
select the module which is having more priority, by based on
the priority for the module we have to finish our testing
process

Answer / chaitanya deshpande

Hi everyone,
All the above answer seems very correct. But,carrying out any kind of testing (Smoke, Sanity, Risk Base) wont be enough if we miss any crucial functionality.
Testing process has some steps and formal documentation like Test plan, test cases, Reviews of those documents.
So I think if time to complete the testing is less we can skip these formalities of test plan, reviews,approvals and all and directly jump on test case preparation and its execution.
Different approach can be taken while authoring and executing the test cases. It might be Smoke, Sanity or risk based.

Suggestions are welcome.

Answer / aishwary mishra

If there is no sufficient time the we need to keep some
scenario while testing the application-
1-Check all the major functionality
2-Check all the functionality which is most visible to user
or user is going to use most frequently
3-make scenarios based upon business requirement and execute
them.
4-Do smoke testing
5-check UI properly

Answer / bizz

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.

Answer / murali

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

Answer / govind

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

Answer / rafi

at this situation we have to perform adhoc testing

how u do database testing

4 Answers   Polaris,

do a new defect is required to log for slight variation in steps on defect retest or the defect can be re open

1 Answers  

What is bug release?

0 Answers  

when u involved in uat suppose if u find one defect then do u intmate it or not

3 Answers  

As a test Engineer what are all the challenges you faced in your project? It takes more time to answer this question but i said wrong... Could anybody answer atleast 4 or 5 answers

2 Answers   Hexaware, Sreeven Infocom,

what does a test plan contains and is a tester allowed to see the entire test plan or only the scheduling part of the test plan

1 Answers  

How smoke testing is done with example??

7 Answers   Virtusa,

Can any tell me how a clinical data management system is tested? what are the test scenarios? what are the test cases? work flow.

0 Answers  

Any one can send the Test Plan Tempelate to this id raj_kan1979@yahoo.co.in

1 Answers   Photon,

oracle table A havng one million records. write 10 test cases to test data?

1 Answers   IBM,

Enlist some bug status along with its description?

0 Answers  

what is port testing and mutation testing?

3 Answers