I think, I will convince my project manager to allot few
more days to execute the test cases. In the mean time try
to execute all priority1 and priority2 test cases.. I know
it not possible to execute all the test case within this
time..if i cud do it, then its well and gud..but if i
cudn't as i said earlier i will try to convince my project
manager or project leader, anyway as a test engineer i can
not compromise on quality.
Hi All,
I didn't understand the answers. How do u knw which test
case is show stopper testcase? How we will give severity
and priority for a test case.
can anybody give me the brief answer the actual question ??
Its simply impossible to execute 2000 test cases in 2 days
so i will categorize them according to functionality based
on priority so execute them from customers point of view
them execute the rest
I will categorize the testcases according to functionality
based on High priority & Functionality Coverage (customers
point of view) then start executing the test
or
Go for adhoc or random testing(Can be done by an
experianced person who is having about the Application)
1.Execute the test case which has high priority test case.
2.Execute the test case which has major functionality.
3.Execute the tests in adhoc or exploratory testing
Murali
dharanmu@yahoo.com
1. We can go for ADhoc/monkey testing.
2. Go to automation testing.
3. we can give first preference for the high priority
cases , then if time is left over we can go for low
priority also.
Go for "exploratory testing" and that will test cases which
are among those 2000 test cases and simultaneously u will
know what is critical and high priority.
Hi Neelu and Mayee,
Will you be able to write ur automation suit in less than a
day or 2 to cover all the 2000 Test cases and execute the
same? The reason is one needs to put effor for Automation
as well ... RITE? so were would that effor go? Is it going
to be out of the 2 days given/provided to you? If NO then
its not going to be easy to go for automation.. your
options are RULED OUT.
I dont want to say Best but the BETTER thing would be , as
few answered, to got for Test cases that COVER major
functionalty.
Again here a problem is weather the QA personal executing
the test cases New/Very New/experienced.
If its case of New/Very New : It becomes difficult to
execute in given time. For this the Management is
responsible for not planning properly.
In case of Experieced too: If the test case complexcity is
too much and planning is improper, its difficult to execute.
Let me know if this makes any sence?
-Srinivas.
i will go for the monkey testing, i will test basic
functionality related test cases.
how will you automate the test cases if the test cases are
for different modules you cant even record the script for
thousands of test cases if there are few test cases and
multiple test data is there then its ok.
I will go for automation if possible...if its not possible
then i will check its priority and severity....if it is also
not possible then i will randomly take the test cases and
check for the expected and actual results.
If U have Test Cases already prepared and u have to just
excute those test cases in a very short time then how will
U decide which test cases has to be excuted first. Is there
any technique ?