Tag Info

Hot answers tagged

15

I work as a Manual tester on a big project. My project follows Agile methodology. I test a Web-based application. I sometimes ask my self , that am i giving any value to the stakeholders? So, the value that you are giving to stakeholders is the reduction in the amount of defects that go to production. The cost of fixing a defect drastically increases ...


10

You've got a pretty good grasp of the defect life cycle, however the terminology and even the flow can change from project to project and team to team. Most likely, "Open" is the same as "New". More important than what term to use is ensuring that the team are all using the same terms.


9

In our organization, there's one defect (2nd one opened is a duplicate), but there are two test cases which fail.


6

Unless you are certain that the root cause is identical and fixing one will always fix the other, I would make it two defects. The developers can mark one as a duplicate later if that turns out to be the case. What you don't want is to consider it a duplicate, the developers fix one thing, then the other error turns out to have a different cause or another ...


4

You need to meet your project manager half-way. Using an unrealistic metric does not help either of you, and you are right to be concerned about that. At the same time, you need to avoid describing your problem in so much detail that your project manager will not understand it. Given what you wrote, I think I would tell the project manager something like, ...


4

Yes, Selenium is an active project (see commit history on GitHub). Then why are there so many unresolved open issues? It's open source. We can't expect the team members to fix bugs on a daily basis, because they are just enthusiasts and all have real-life jobs. The developer in charge of a particular area may not have time to deal with it right away, even ...


3

Determining who introduced a bug is without analyzing the code is: Extremely time-consuming if you want to install previous versions of software, you need to also accordingly change data structures, or have a copy of your databases for every database change keep switching between different versions which might have different behavior and you still have ...


3

Some time ago, Gregory Pope published even a longer list of root causes of bugs together with an extensive list of techniques to either detect or prevent those problems. All the material has been presented during ALM 2011 Keynote and recorded, together with slides, if you have less time, but I really recommend listening to the recorded presentation because ...


3

Answers above are correct, let me make just a small re-phrasing of above answers. Depending on a bug/issue tracker software, there are several attributes of Issue. Status and Openness may be combined or separated. The common reason for having Openness separated is the consideration that an issue should be closed by the same user who has opened it. I ...


3

Many shops would have an additional outcome to your step 2. Now the defect will be evaluated by dev team manager: i.If the defect is not valid then STATUS = Rejected ii.If defect is out of scope then STATUS = Deferred iii. If defect is a duplicate then STATUS = Duplicate iv. If the defect is none of these, then STATUS = Open (Some shops mark a defect ...


3

Tester is just a label on an employee. Testing provides value. It is virtually impossible to write bug-free software, and so software that has not been tested is virtually guaranteed to be buggy. Someone needs to test it. Who tests depends on the circumstances. Some people are good at testing, and some are not. You probably want the person who tests to ...


3

Yup, when I extracted data on reported bugs (or defects in QC/ALM), the BUG table is where I ran my queries on. Just to check, you can preview your query results when using the Query Builder, or just go right on ahead and generate the report. Then you can compare the content of the BUG table against what you're finding in the Defects module.


2

I would focus on the specific integration features that you need, and then come up with specific reasons as to why this info is useful and how will it increase productivity or reduce costs. Personally I find that many integration features to be bells and whistles. I know this doesn't exactly answer your question but I felt it important highlight. You ...


2

In my company there were around 63 integrations methods I needed wanted - I'll write down some important ones here: Support Request to Feature Email to Bug/Feature/Enhancement Commit(s) to Code Review Feature Request to Requirement Forum Thread to Feature Request There are many of them - but you gotta begin with whats most important for your ...


2

Yes, it is possible to do this. Within the Analysis View, go to "New Excel Report". Excel reports are the most flexible feature of the Analysis View, because they allow you to write SQL queries against the ALM database to extract any detail you want, at any level of summary. You can then use Microsoft Excel itself to generate charts (if you desire) or pivot ...


2

Phil is right with how customizable it is. After a quick search, I found a couple of export/import plugins. A more important question may be however, why are the testers using a separate instance from the developers? Doing a constant export/import is just going to create additional overhead. It's all fine and well if you update once, but, wouldn't the ...


2

Check out the test heuristics cheat sheet: http://testobsessed.com/wp-content/uploads/2011/04/testheuristicscheatsheetv1.pdf This will give you some ideas of what types of things to look for when testing a given type of system. For example, when testing something with an input, do boundary testing (test the limits: what happens when you input nothing? what ...


2

I know that Bugzilla can add whatever custom fields you feel like. Perhaps you could have it auto-populate?


2

It depends on your environment and the circumstances. Some rules of thumb I use: WHEN IF I have an automated regression suite and distinct builds AND the bug breaks the regression suite, THEN I can give a "last known good" build as well as a "first known broken" build. IF I have been working on something and I am reasonably sure it worked two days ago ...


2

Whenever I see something like this I start to think "it depends" on many things. What are your expectations for the migration? What are your coworkers expectations? Do they mesh? What is your intent going forward? It's hard to really say what the best practice is, without really know what you hope to achieve with this. My experience in this area has ...


2

TL;DR: The way you and your team handles it depends on personal preferences and organizational influences. In my experience, most of the time similar behavior (same functionality) different execution paths tend to be duplicates. Car Example Scenario 1 Test Case 1: You get in and turn on the lights. Result: Nothing happens. Test Case 2: You get in, ...


2

As for the debate, I think the code defect is the root cause, which may result into one or more behavioral defects. And I am fine having one ticket per defect, and the TCs cover the behavioral parts (as mentioned by Jean). If you are using a tool like JIRA to track the bugs, which allows you to link different tickets, an option may be to consider one ...


1

I don't have a good answer about best practices, but can share some experience- An in house bug tracker was replaced by another in house bug tracker. the new tool was totally redesigned from the floor up. During the transition we made an effort to close most of the old bugs, the important once were migrated and the less important once were left at the old ...


1

Instead of arguing over the definition of the word "defect", it may be more productive to decide what should happen when someone finds a different root cause for the same symptom. There is no universal answer -- you need to figure that our to yourselves.


1

IMO development team, instead of marking one of the bugs as duplicate, simply could: Open a bug in your issue tracking system for the actual code defect they found. Designate both bugs corresponding to failed tests as blocked by that code defect. Then situation would naturally resolve itself.


1

The question is interesting. The main thing is to be checked in the above scenario is the execution path. As the path is different, the problem may lies in the execution path. If testing is done for those execution paths then the defect can be easily found out.


1

The definition of duplicate is: a copy exactly like an original. anything corresponding in all respects to something else. Cards. a duplicate game. Purely by definition a duplicate has to be an exact copy or anything corresponding in ALL respects to something else. A true duplicate bug, a copy of another or one that corresponds in ALL respects to ...


1

I've used Basecamp and Jira separately, and Zapier seems to integrate both of those. They also have a free subscription here Fairly straightforward information here: Integrate Basecamp with JIRA If you find that your team is growing, or you need to integrate more issues you can always just subscribe to a higher tier. +1 for Zapier


1

Mantis is totally customisable so you could probably get someone to code a solution up - the database is open and the code is there for you to do whatever you want. It does mean coding in php though...


1

Well, on the one hand the benefits of a wholly integrated SDLC tooling solution are many. It's a beautiful world when all your tools work together. However, to achieve this you MUST have a full time employee whose primary responsibility is to engineer that integration. That means you're in for at least $75k per year to enjoy the pleasures of tool ...



Only top voted, non community-wiki answers of a minimum length are eligible