Tag Info

New answers tagged

0

Basic flaw in your process is that your process creates adversarial relationship between developers and testers: it does create bad feeling with the developers, who understandably feel their fix has not "failed", and can even end up being disciplined by the company for items taking longer to develop than originally estimated, or the number of times ...


0

There is always wiggle-room with these sorts of points, but I would say you are correct in thinking that the first and third issues should be treated as new issues (bug and feature request respectively). Including logically separate issues in one JIRA issue is only a good idea if they are so tightly bound that neither one can reasonably be fixed without ...


1

The second and third bullet points are arguably not bugs at all. They're new feature requests. Invent a list where anyone -- testers, programmers, marketing, subject matter experts -- can suggest a new feature. Sticky notes on a wall will do. That new request gets prioritized like any other request. (By contrast, a policy might be that regression bugs must ...


1

We can't tell you how to fix your process because it depends on your own circumstances. That said, this does not sound like a hard problem solve. It sounds as if your Jira configuration is not expressive enough for your workflow. If it were me, I would do start by getting agreement on which workflow problems need fixing. It sounds as if you already have ...


0

One of our software suppliers operates in this manor but we still found 39 bugs when testing their latest delivery. Mark Smith.


0

It sounds like they might be looking for more of a Test Analyst. You have the expertise to know what tests should be performed even if you aren't performing writing the tests yourself, and crucially you should know what tests cannot or should not be automated.


5

The short version: regardless of the development methodology, your role is to provide information about the overall quality of the application. You do that via testing anything that isn't included in the developer-maintained automation, and reviewing the developer-maintained automation. The long version: This question and its answers is a good starting ...



Top 50 recent answers are included