Simple, ask ur manager to provide more resource(members) to 
help u to complete the task or tell him that u cannot 
finish the task. Its as simple as saying no when u r asked 
to run 30 kms in 10 minutes, which is humanly not possible.

We should always work according to the time u got.
If you think the time is less than we can check the main 
things in application  like :-

1. whether the application's all funtions are working fine 
or not .
2. Do the positive testing only and after that if u get the 
time you can do the negitive testing otherwise just check 
whether the application is working fine in a positive 
enviorment or not.

Please make me correct if I ma wrong anywhere :)
Rekha Rajora

Very true , very rightly written in answer 2 . Thanx to her 
for to excellently writing.

Why becoz. We normally dont get the resources as they are 
stuck in some or other projects / products . Testing 
stratergy derived above is exccellent and the same we do in 
out testing habits.

Testing a software should be thorough testing. You must 
convey the client that it will require 30 days for complete 
testing of software and you can confirm it to be Quality 
software as an QA professional. To get a good quality 
software it can be done in two phases.

1st Phase: Make it launchable-

1. Directly go without with bug reports(without any test 
cases). 
2. Test for the functionality and system crash bugs only.

2nd Phase: 
Thorough testing of software to make it bug free and 
reliable.

Before you begin to Test you need to do the estimation and 

convey it to the client that the testing will take Nman days

after the Client Approves you should proceed yo Test the 

Product , This is the usual procedure.

I AM NOT AGREE WTH MS. REKHA RAJORA

At this situation we generally use "Risk Analysis " 
Approach.
1.check those functionalities which are more close to 
project perpose,2.check more secure code,3.check more 
dependent modules,4.check code which is so complex n create 
lot of errors,5.check mostly usable functions etc.

The best thing to do in less time is go for Automation
Testing. It is meant for these only i.e in less time more
function can tested with both positive and negative testing.
i.e by using Data Driven testing. The feature of Automation
testing are : 
1] Functional Testing and Regression Testing.
2] testing the application with more speed in less time.

Most of u r correct if we have not sufficient time 
for testing at this situation follow
"Risk Anaysis" Approach means Test High risk area first.
1.check those functionalities of application those r very
close to project perpose.
2.check those functionalities of application which are very
important in security point of view.
3.check those functionalities of application which are 
easily visible to the user.
4.check code which is so complex n u think that it will 
very harmful for others
5.Do Ad hoc testing.
6.check those areas which is changing.
In this way u perform testing on Risk basis.
Thankx.
Regards.

Guys the question is not testing, it is about completing a 
task which could be fixing a bug or developing new 
functionalities.  My answer is simply do not accept 
otherwise you will end up in risk of not completing the 
task as per schedule.

John,

I think u are strogly disagree with my point.Please justify 
your answer.

Rekha Rajora