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

On which basis u'll prepare the test cases.

6 Answers   Semantic Space,

What r the roles and responsibilities of a TestLead?

1 Answers  

Please explain test matrices

2 Answers   Persistent,

explain sdlc?

2 Answers   SAP Labs, STC, TCS, Thirdware,

How do you scope, organize, and execute a test project?

1 Answers   Wipro,

What is the difference between QA and QC in testing activity.

3 Answers  

how to test manually from date and todate selection from calender

3 Answers  

What is the different between QA&QC? Please give answer with examples?

3 Answers   Nedbank,

Can anyone explain Boundary value Analysis and equavelance partition with real time example

10 Answers   Accenture,

what are the testing methodologies?

6 Answers   GE, Infosys, Patni, Wipro,

After few months, I'll be having 2 years of experience only in Manual Testing.I want to know which type of questions I'll be asked in Interview if I'll appear for any.

0 Answers  

what is database testing?

1 Answers