Comments on: What if there isn’t enough time for thorough testing

By: Sandy

Sandy — Thu, 17 Nov 2011 17:56:27 +0000

Our company is on an On Demand Application and has not control over fixes (service packs) and releases. For Service Packs the vendor actually loads our test AND production systems and we have literally no time to test those beofre our European Users sign on. Even if we find a bug, we can only submit an SR as it is already in Production. A Servcie Pack is typically 30 to 60 bug fixes that are usually minor. While we rarley, never? have catastrophic failures and SP will often cause minor problems. We have talked about doing “regression testing” for this before we test the actual changes that impact our system. It seems to me that is overkill and Regression should be done after we test the specific changes. Perhaps we need some kind of Smoke / Build Verifcation Testing as soon as we get the Servcie Pack but again, we are not sure to what level detail. Perhaps only test things that we have actually changed from the vanilla system?

Your thoughts

By: pavan kumar

pavan kumar — Fri, 23 Sep 2011 14:00:05 +0000

can you tell me what’s the meant of elapsed time and it’s related topics

By: mayuri

mayuri — Fri, 08 Jul 2011 19:25:43 +0000

HI!!!!
I am looking job in QA .I am Brainbench certified,but doesnt have real time experience.I saw and study your post.Thanks for such important information.
I want to know within 1 project how many test cases we have to write?
Simply,If I want to justify my 1 year of experience in HOME INSURANCE company on 1 project,so how can I put points,or justify my experience?
I will have to give some scenario or anything i am damn confuse.Can you please help me out by giving any example in HOME INSURANCE application.
Thank you!!!
mail id-mayuri.s2010@gmail.com

By: LAST 5 Software Testing TIPS | ISEB/ISTQB Software Testing Training Courses UK

Mon, 20 Jun 2011 13:18:13 +0000

[...] Don’t run out of time to do high priority testing tasks. Prioritize your testing work from high to low priority and plan [...]

By: Indu Sharma

Indu Sharma — Wed, 25 Aug 2010 12:18:09 +0000

Effort estimation is very simple:

>>1st u have to find out all the possible scenarios in all features.
>>Then Make a traceability matrix i.e. for each requirements how many test cases are required.
>>Suppose if u have 100 testcases, then calculate how many test cases one person can execute in a day(here u have to consider difficult and easy both types of test cases)
>>If one person can do 5 test cases in a day then in 20 days all test can be executed.i.e effort=20PD or 4PW.
>> Now u have to add following facters:
1. What if 30% Testcases failed in Run1, then u have to rerun all those test cases. So u have to consider 35 testcases failure i.e 7PD or 1.4 PW
2. What if say 10% testcases failed in Run2 then i have to re-run 10 testcases again. so its 2PD or 0.4 PW

Now, Total effort= 4PW+1.4PW+0.4PW=5.8PW(Person week)

This is just a example i gave… u can add if there are any opther variants which impact ur execution.

regards,
Indu

By: krishna

krishna — Tue, 24 Aug 2010 13:58:13 +0000

can you please tell me and send the documents on how to calculate test estimation

By: Indu Sharma

Indu Sharma — Sat, 21 Nov 2009 21:55:51 +0000

Its good ..i enjoyed reading this. I will try to incorporate this in my testing….:)

By: G.Mallikarjun

G.Mallikarjun — Tue, 25 Aug 2009 11:02:41 +0000

Shivali, plz read this article to get ur answer.
Use risk analysis to determine where testing should be focused.
Since it’s rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include:
• Which functionality is most important to the project’s intended purpose?
• Which functionality is most visible to the user?
• Which functionality has the largest safety impact?
• Which functionality has the largest financial impact on users?
• Which aspects of the application are most important to the customer?
• Which aspects of the application can be tested early in the development cycle?
• Which parts of the code are most complex, and thus most subject to errors?
• Which parts of the application were developed in rush or panic mode?
• Which aspects of similar/related previous projects caused problems?
• Which aspects of similar/related previous projects had large maintenance expenses?
• Which parts of the requirements and design are unclear or poorly thought out?
• What do the developers think are the highest-risk aspects of the application?
• What kinds of problems would cause the worst publicity?
• What kinds of problems would cause the most customer service complaints?
• What kinds of tests could easily cover multiple functionalities?
• Which tests will have the best high-risk-coverage to time-required ratio?

By: shivali

shivali — Tue, 25 Aug 2009 08:57:19 +0000

Can you please tell me if i can get some projects of software testing which i can do at home?

By: Jagdish R

Jagdish R — Tue, 18 Aug 2009 05:41:16 +0000

Hi SHivali….

When to stop testing?depends on the below:

1. When all the test cases are exected successfully
2. When the budjet allocation is over
3. When the time/scheduled for testing is met
4.When the delivery date is met to deliver the application