The online community for software testing & quality assurance professionals
 
 
Calendar   Today's Topics
Sponsors:




Lost Password?

Home
BetaSoft
Blogs
Jobs
Training
News
Links
Downloads



Quality Engineering >> Defect Tracking

Pages: 1
mayathampi
Newbie


Reged: 10/29/08
Posts: 14
Mapping test case with a defect
      #541735 - 01/06/09 06:42 AM

If you have executed 100 test cases ,every test case passed but apart from these test case you found some defect for which test case is not prepared,then how you can report the bug?Also the test case has been reviewed already by the TL.So can we add a new test case related to the new bug?

Post Extras: Print Post   Remind Me!   Notify Moderator  
Joe Strazzere
Moderator


Reged: 05/15/00
Posts: 12344
Loc: Massachusetts, USA
Re: Mapping test case with a defect [Re: mayathampi]
      #541748 - 01/06/09 07:12 AM

Quote:

If you have executed 100 test cases ,every test case passed but apart from these test case you found some defect for which test case is not prepared,then how you can report the bug?




In my shop, you just report it.

In your company, are you prevented from reporting bugs which were found outside of the formal test cases? If so, I think that is unfortunate.

--------------------
- Joe
Visit AllThingsQuality.com to learn more about quality, testing, and QA!

I speak only for me. I do not speak for my employer, nor for anyone else.


Post Extras: Print Post   Remind Me!   Notify Moderator  
JCTreb
Active Member


Reged: 08/16/01
Posts: 789
Loc: Minneapolis, MN
Re: Mapping test case with a defect [Re: Joe Strazzere]
      #541800 - 01/06/09 10:02 AM

Like Joe states, report the defect...then build the test case for validating the resolution of the defect as well as for regression testing in the future.

--------------------
Jason Trebilcock

"The single biggest problem in communication is the illusion that it has taken place."

-George Bernard Shaw, Irish playwright and Nobel Prize winner, 1856-1950


Post Extras: Print Post   Remind Me!   Notify Moderator  
priyank1985
Member


Reged: 08/31/07
Posts: 56
Re: Mapping test case with a defect [Re: mayathampi]
      #542091 - 01/07/09 09:54 PM

Hi,

As per my understanding, Defect you found is not but you can say your test case. When you design test case , it happens that you may have consider all positive flow of application and made test cases. but when you will really test application at that time , you surly get bugs for that test case is not prepared.

As far as I know, test case must be updated as per some frequency. it may be end of your regression cycle, may be when change request comes, or when you map bug with test case. At that time you should add test case into your bank. In this way , your test case bank will also become rich and your test cases will match with your application even.

Let me know your views on this.

--------------------
Thanx,
Priyank Shah


Post Extras: Print Post   Remind Me!   Notify Moderator  
mayathampi
Newbie


Reged: 10/29/08
Posts: 14
Re: Mapping test case with a defect [Re: priyank1985]
      #542104 - 01/07/09 10:58 PM

Thank you all for your views.

Regards,
Maya


Post Extras: Print Post   Remind Me!   Notify Moderator  
QATester1982
Newbie


Reged: 01/06/09
Posts: 23
Re: Mapping test case with a defect [Re: mayathampi]
      #543135 - 01/14/09 03:17 AM

Yes you can add a new test case related to a bug, mention type of testing as "Exploartory Testing". These test cases are very important for the next regression cycle of the application.

Post Extras: Print Post   Remind Me!   Notify Moderator  
Gaurav_Pandey
Member


Reged: 06/18/08
Posts: 216
Loc: The Land of Snake Charmers
Re: Mapping test case with a defect [Re: QATester1982]
      #554795 - 03/05/09 10:36 AM

I would recommend that you should report these defects.
However, there is a possibility that you might be asked some "uncomfortable" questions on why the test cases were not able to uncover these defects.

I attempt to come up with reasons on the following lines

- The requirement was not specific
- The requirement had a design flaw
- The scope of testing was to test feature A, however during test Feature A, you observed that Feature B was impacted. Feature B was not in the scope of the testing phase - however you observed that feature B was impacted due to coding done on Feature B.

The last answer I would like to give is - The requirement anaylsis and test design was not "upto to the mark"


Post Extras: Print Post   Remind Me!   Notify Moderator  
Pages: 1



Extra information
0 registered and 6 anonymous users are browsing this forum.

Moderator:  AJ, Daniel_S, swt88 

Print Topic

Forum Permissions
      You cannot start new topics
      You cannot reply to topics
      HTML is disabled
      UBBCode is enabled

Rating:
Topic views: 4727

Rate this topic

Jump to

Contact Us | Privacy statement SQAForums

Powered by UBB.threads™ 6.5.5