Tag Info

Hot answers tagged

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 ...


3

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, ...


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

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

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

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

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 ...


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, ...


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 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

The metrics can be divided so that there is reportable status. 1) List of test conditions (i.e., test cases). Do you believe that you have a complete list written down? If so there is one metric (identification of the test conditions). 2) From the list of test cases, how many are completely fleshed out as far as what needs to be done to run the test? ...


1

Sometimes you will find non-technical project managers and to make the matters worse they work against metrics rather than common sense. However, his question is legitimate to some extent. Given a feature, you could always come up with N number of tests (after applying equivalence class partitioning, pairwise etc) and then you can group them as functional ...


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