Kiran

• Mar 16th, 2006

 

At this moment I prefer random testing and ensure that changes made in the code was not effected in not changed code.

jyotsnasai

 Profile Answers by jyotsnasai 

• Mar 22nd, 2006

 

Hi,When there is only minimum amout of time left,then it is best to go with adhoc testing and check whether the changed feature has affected functioning of the existing features.

satya.k

• Mar 27th, 2006

 

Hi ,

    In that case we can test the main part of the application, we can found 80% of errors in that main functionality only, for that only we can mainly concentrate on main functionality...

i thk tis answer this some help...

Bye

Satya

      

vishali

• Apr 22nd, 2006

 

we have to do the Ad-Hoc testing

Anand

• May 15th, 2006

 

Hi,

at that time i willcheck that features using equilance partitionaing and boundary values (both positive and negativve), then i will check other related pages for which this feature works.

raghuramsuravarapu

 Profile Answers by raghuramsuravarapu Questions by raghuramsuravarapu

• Jun 20th, 2006

 

In this situation i will prefer to consult the client and request him to extend the date of release for another 1 week,for thorough testing and fix the defects that are found,so that the quality product can be released.

Because it took 6 days to complete the coding part.Only 1 day for testing is remaining.Why are we testing?to find the hidden defects.So if you start testing the major functionalities in that single day left,found any defects.Than what is the situation?We cannot release the product,because there are defects in the major functionalities.So extending the date is the best possible way in this situation.Releasing a quality product is also as important as releasing the product on time.Client will be happy if there are no serious issues with the product,though you have took extra 1 week to release the product.

--Raghu

sumit

• Jul 5th, 2006

 

I think Mr. Raghu gave the best reply, that is ultimate answer.

vinod

• Aug 6th, 2006

 

I am impressed very much by Mr Raghu's

pradeep.r

 Profile Answers by pradeep.r 

• Nov 14th, 2006

 

When the Time is very less we have to prioritize the New Changes, and Concentrate on the High priority things and test throughlly for that areas. For all other changes we can take risk and test only for the correct implementation of the changes.

Thanks,

Pradeep R

jainbrijesh

 Profile Answers by jainbrijesh Questions by jainbrijesh

• Nov 16th, 2006

 

First check where changes have made. then do regression on fast track.

Edward

• Jan 27th, 2007

 

Hi,
Since everything is being planned and you already have got the specifications like what are the modifications that are to be done. I think the best way is to concentrate on the functionality where the chances of the user/customer hits the max and give a detailed list of the functions that are not beings tested so that even the customer is aware of things he is not suppose to hit.

Edward

v.deshmukh

 Profile Answers by v.deshmukh Questions by v.deshmukh

• Jan 29th, 2007

 

Hi,The question is that it is deadline of the project in any condition.so i think that it will be better to talk with developer.

a23_prasanna

 Profile Answers by a23_prasanna 

• Aug 26th, 2008

 

If you have run out of time you have to do risk analysis and according to that you have test. Here are some aspects for the test
1. Testcase which covers multiple functionality
2. Find which aspect of the application are most important to the customer
3. Test most important function
4. Which aspect of the application is most visble to the user.

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• May 28th, 2009

 

Extending the days is the best solution for this situation. To keep the Quality, need to be test atleast 4 more days, bug fixing, retesting, regression which needs 3 more days. So extending the days with proper approval from client is the best way.

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Nov 26th, 2009

 

HI

  First i will intimate this to my TL or PM, and i will request for extra time, if they have given then the problem will be solved, if they are not in a position to give, even by asking the client, then i will contact my client directly and explained the current situation.

  I feel 99.99% of the cliends will give the time in this situation as no one wants the poor quality software, but we are maintaining the schedule using project plan, if at all any deviations in the plan, then we will update immediately, and shared with client so that he will know what we are doing here.


CNU

preetchana

 Profile Answers by preetchana 

• May 12th, 2010

 

While the developers are busy doing coding, and in those 6 days.
Tester should be realy with the following:
1. Test Cases of the new requirement.
2. Plan out the way to test the application.
3. Can have detailed study, that with the new changes/enhancement, which modules will have possibility that they will be affected, so that we can plan out for regression testing for the same.
4. And at the last day:
   a. Execute the test cases for the new functionality
   b. Test the application that has higher risk of bugs (with complex coding)
   c. Test the area, which is mostly used by Customer/User.
   d. Your testing task will be divided among testers (so that all the major modules can be tested).

hvputteti

 Profile Answers by hvputteti 

• Nov 4th, 2010

 

First I will check the high risk areas and which functionality is it  important to customer and basing on high priory risks will test first. 

Mr.Maduraikaran

 Profile Answers by Mr.Maduraikaran 

• Jun 15th, 2011

 

We need to get the build ready in 3 days, because if the developer will take 6 days to code and he gives to test for only one day, and if we find any bug at the end of the day, what will happen?

So for testing, enough time is mandatory. At Least the minimum time is required for adhoc.

If we are going for adhoc, we will test the major feature alone, what if the other features are not working? What if the application crashes after doing some transactions/actions in the application ?

For your question I will talk to the customer and will ask for time, and cover up the existing functionality + then test the newly added feature. Because the existing functionality should not be changed due to the added feature.


-Mr.Maduraikaran (The K).

Sailaja Vegiraju

 Profile Answers by Sailaja Vegiraju 

• Jun 16th, 2011

 

during the 6days i won't sit idle,i will study the changes that the client is asking for and identify the areas in current application which are effected due to the new changes.now on the last day i test the new test cases and all dependent test cases for the change means i perform regression testing for new requirements.

Mr.Maduraikaran

 Profile Answers by Mr.Maduraikaran 

• Jun 16th, 2011

 

Hi Sailaja, I agree that we can complete the testing in just one day. But what if the condition is like this: You are testing on the seventh day by end of the day, you found a bug. Now the developer fixes and gives the new build. Now you have only one hour remaining to deliver the product. Now it is not possible to test (regression) within one hour.

There may be bug fixes and new builds. So we need minimum number of days to execute. Hope I've cleared why we need at least 3 days.


-Mr.Maduraikaran (The K).

naresh

• Jul 18th, 2011

 

What the TL/Manager do till the sixth day, they will track the status of the new requirement every day, they will be knowing the status they should be more aggressive in taking decision in such cases, and we can follow any of the case above mentioned. It depends on your client acceptance and your company policies.

If we give first priority to quality there is no other option except requesting for additional time.