srinivasreddy

 Profile Answers by srinivasreddy 

• Dec 14th, 2005

 

If we have very short period for testing the application,tester will follow adhohoc methods(his own methods ) to test that application.

ie   Without using test plan and without preparing  test case document he will tests that application by focusing on major functionalities.

Tester will use his own knowledge and experience to cover maximum coverage.

raghava786_jack

 Profile Answers by raghava786_jack 

• Dec 15th, 2005

 

we can use monkey testing method as well as the adhoc testing methods and by adhoc testing  and validate the testing process through (TACT)tester acepted testing method  when the duration  is decreased . 

Muthu

• Dec 15th, 2005

 

Yes. Also this type of testing is called "Exploratory Testing".

Th1nkD1fferent

 Profile Answers by Th1nkD1fferent 

• Dec 18th, 2005

 

In case you were lucky to get any form of documentation upfront then your life is a bit easier.You should try and use different methodologies to achive your goal of "enough" testing to give your boss the "go-ahead" confidence. In this regard the testing approaches you could use are:- Use the Requirement/Use-Case document to drive your testing effort- Identify & Test all major functional areas/features of your product- Identify & Test all major risk-areas (things you can't let go wrong) of your product- Use Exploratory/Ad-Hoc/Monkey type testing which would be more like hitting in the dark and hoping you hit jack-pot- If time permits and have a code coverage tool available, go all out and try to test whatever possibleRemember, testing team ALWAYS has less time than what is required so, you need to be ready with a plan at all times to "squeeze-in" whatever possible in available time.Hope this helps.

Anand

• May 4th, 2007

 

We will do risk analysis, we concentrate on the major fuctionalities.

sandeep kumar

• Oct 4th, 2007

 

Dinesh. If you do Adhoc testing you will miss the some functionality and quality of the project is not good bcoz it doesnt have any procedure
About Monkey Testing, You dont know What type of input you have given, so my suggestion is test the application which is really important concentrate on more and rest of them Adhoc testing. From this, Quality of the project will increase and customer will be happy.

jaysmika

• Oct 12th, 2007

 

In case the testing time period available has been greatly reduced and the test plan/cases have not been completed then use the functional requirements doc as the base line for beginning the testing. In case the test cases are already available then confirm with the users whether they are planning to use all the new functionalities immediately after the new system (version) is available or not. If not then identify those which would be immediately used and start testing those. If yes then try to consolidate the test steps for various similar scenarios and execute the test.

jainneha81

 Profile Answers by jainneha81 

• Nov 30th, 2007

 

In such case you need to prioritize your test. All the critical, major,high and medium priority bugs should be tested and fixed first.
In such case risk driven technique is also used that helps to evaluate the risk impacted areas with there priorities. so that they can be fixed first.

Tests are also conducted keeping in mind the client's or users most frequently used functionalities

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 15th, 2009

 

In any case, I would reach consensus with customer as to how testing will be performed and what the exit criteria will be.

OPTION 1

1) Conduct exploratory testing immediately while authoring test cases to save time
2) Review requirements to see if anything was missed
3) If something was missed, then test that too
4) Let customer know what was tested and what has not been tested


OPTION 2

1) Review requirements and create test cases
2) Prioritize test cases
3) Run cases from highest to lowest priority
4) Inform customer as to what was not tested