Comment

Comment by Bala Viknesh on October 30, 2012 at 11:04am

Defect Management Process:

We are a team of more than 50 + ppl split across different locations in India.  We are really facing a trouble with most of the times, the defects are getting Duplicated. Either it was raised by someone in other location and the same defect raised by someone else from other location. 

Need to eliminate this duplicate defects raising. 

Options tried:  

1. Triggering a mail from the Defect Management Server, to everyone in the team notifying about the defect 

 Issue :  No one reads the mail (Of course we know, this is people issue) and they just go ahead. 

2. Once a defect is raised by any team member, they have to send a mail to the team informing why was that defect raised. 

 Issue : Same as above

3. Update in the Repository 

 Issues:  With stringent timelines, we are not able to accommodate time, to update another tracker. 

Risks:

Metrics gets screwed up, with more duplicated defects on which we are not happy with. 

Need Suggestion

We need an alternative solution other than  above three. It would be really good, if you guys suggest me a working solution implemented in your project.

Comment by Subrahmanyeswara Rao P on April 16, 2012 at 1:16pm

Hi All, I want to share some thing regarding this Forum. "I have seen somany request's like I am fresher/exp in testing and looking for a job.........."  these type of wall posts can be done in some job portals, which can help you actually. Sorry to say these words, please use this forum to discuss regarding software testing. Ask doubts in new trends in testing, ask doubts in testing process, ask doubts in different kinds of testing etc....... so that we can help this testing community. If I am hash to anybody, please excuse me.

Comment by vivek on April 15, 2012 at 6:45pm

@ ruby which Institute u have done course

Comment by vivek on April 15, 2012 at 12:43am

@ Rubi , which Institute you have done course, mention name other people will not join & not cheated by Institute.

Comment by Hare Ram on February 21, 2012 at 9:11pm

i am a 2011 batch passout having the knowledge of manual testing,QC QTP and selenium...if there are any openings then plzzz inform me...my mail id is harryicfai@gmail.com

Comment by sasikala on December 6, 2011 at 3:58pm

Hi

am a manual tester having 3.5 yrs exp. Am looking for the better opportunity,

If there is any opening pls do mail me at dsasi_06@yahoo.com

Comment by omkar saste on August 5, 2011 at 10:57am

i am new to join this group.hope all can you share with me about manual testing

Comment by NaliniReddy on June 30, 2011 at 10:10am

hiii  i hav  just joined in this group please give me some basic information about Manual testing

Comment by Indhirakumar on April 12, 2011 at 12:09pm

hai every one i am new to this group.hope all can share with me about manual testing.thanx bye..

Comment by Ratna Prabhu on March 29, 2011 at 3:25pm

The purpose of sanity testing is to ensure that released build is stable to test in deep.

Briefly Tester should Test all the Basic features are working fine and application or system didn’t crashed or got hung while Testing Basic needs/ features

• ‹ Previous
• 1
• 2
• 3
• …
• 7
• Next ›
• Page