28

As a developer, not a QAist, I have a responsibility to provide software that meets the specs, with as few errors as possible. From my perspective, QA has the responsibility to inform me of any errors that I have made. I place them in extremely high regard for that. When QA tells me that "they found a bug" they found that bug in a particular commit. The ...


20

I see several possible problems here: There are reported bugs that the test team can apparently reproduce but the development team has trouble finding/fixing. This suggests that there is insufficient information in the bug report. In situations like this, it can be helpful to provide an exact set of reproduction instructions. If you are testing a standalone ...


13

It depends What matters is that you are able to effectively communicate the current state of the software in test to your leads and management. How you communicate that information will depend on your workplace culture and any regulatory requirements your employer needs to meet. The biggest potential issue I see with the way you are currently communicating ...


8

I will answer this question with Agile iterations in mind. (An iteration could be a full Sprint or a single-user-story-cycle if you do Kanban or swarming.) The QA department is understaffed when: Not every cross-functional Agile team has a someone with QA knowledge The ratio defects versus released features is getting out of control Test automation is not ...


7

I have been telling them that 100% tested and bug free product is a myth. It might be the way you are telling it. Probably it is true, but having an attitude "it is not my problem" is not the right one. As a business I would like to see someone who cares. Your reaction should be something like: "Damn! Let me figure out how we can prevent this the next ...


7

Most issue trackers have a closed reason of "obsolete". This kind of situation is exactly what that status is for: the bug was reproducible, but no longer is, and you don't know exactly when or how it was fixed. This shouldn't happen often, but you can expect it to occur when competent developers are cleaning up a project that is poorly structured. Tight ...


5

James Bach says, "Testing is the process of evaluating a product by learning about it through exploration and experimentation, which includes some degree: questioning, study, modeling, observation, inference, etc." I would use "re-run a ... test" as a synonym to "looking to learn something in a new context". "if they did do a lot of changes" This ...


5

Although the question portraits it as a problem, and the answers imply to immature processes or procedures, my experience is somewhat different. For some bugs it's simply difficult to come up with consistent "steps to reproduce", and the the few occasions where the bug was observed required complex execution environments, special conditions or simply "a ...


4

In the ideal world you as a tester should say "The actual behavior of the application under test corresponds to the given requirements". However to make that ideal situation having the place you at lease need those "requirements" which have to be comprehensive enough and unambiguous. This is quite hard to achieve in the real world especially in "agile" ...


4

From your explanation I get the feeling you are not working Agile, or not very effectively? It sounds as if the core issue here is the (testing) process. Firstly, quality is the responsibility of the entire team. See also the whole-team approach. In this sort of team spirit, your developer should not feel offended. Secondly, in your phrasing you should ...


4

Programming is complex. Stop for a minute and imagine how complex it is. No, it's ten times as complex as that. No, you just underestimated it again, it's another ten times more complex than that! Every feature adds complexity and can cause unforeseen interactions and side-effects, some of which are bugs (some are happy accidents). Why would a programmer "...


3

What I can see from your case is a poor coding discipline of your dev team. I am not sure what methodology you are using for your product development but I would talk to a person who is responsible for both your teams (qa and dev) results. If you have a sort of efficiency indicators (for example some use defect rejection ratio as the measure of how ...


3

It depends, mainly on the current skill gaps of the team. I would map them, before you make an decision. You could try the Agile Skills Project as it covers all needed skills for a software engineering team. Technical skills are becoming more important for Testers. I believe we can teach technical skills to everyone who is smart, but not everyone enjoys ...


3

In my point of view, the communication skill is more important than technical skills, if a person has a lot of technical knowledge but does not know how to express or communicate with others is merely waste. Because he doesn't know how to express his thoughts or how to enable others to understand his thoughts and the person who has communication skills can ...


3

It depends who you are looking for, what skills your team needs. In my experience soft skills are much harder to learn then technical skills. Especially if you start to learn those later in your career. One of prominent example Linus Torvalds. I always choose people who are willing to learn new things(I test it) and who know difference between good and bad....


3

You did not say what in particular the developer objected to about your assessment, so it is hard to advise you on how you might have improved your writing. That said, the best feedback focuses on repeatable, measurable specifics: measurable specifics because they are less subject to interpretation, repeatable because anyone with the same data can reproduce ...


3

Documenting everything in Jira is a possible waste. Everyone in the team should already understand what is expected to get the user story DoneDone, this includes all testing. If you do not know what and how to test I would question your current proces, not the level of documentation. Agilish teams should focus on testing before or in parallel and not at the ...


2

In the response ideally we should verify below details: Defect status: Resolved/Rejected/Won't Fix/Ready To Test Comments[ of Developer]: What he/she has exactly fixed/changed and if particular condition he/she wants to specify to test thoroughly Version: Commit version[Fixed under] Then you can easily proceed to bake new build & use to test !


2

Our company provides wide range of software testing services which includes mobile testing, functional testing, automation testing and many more. We analyze the requirements and plan for the resources accordingly. Various factors contribute to make proper resource plans such as project estimates, release cycles, scope of testing i.e web functional,mobile ...


2

There's so much testing documentation you could produce, your audience will vary massively... test plans, strategies, summaries, risk assessments, defect reports, etc. Not everyone needs to see everything. Define your project team and ask them how much information they want, or how much they need. For example, at my current client, only the Project ...


2

Production defects are always the metric of a tester's performance (or some other variations like ratio of prod issues to the ones detected on testing phase weighted by their severity for example). So what you can do is being aware of how the metric is defined try to manipulate that metric using the factors you have the impact to. Here are the couple of ...


2

An understaffed QA department is one where a tester is not able to effectively test the work of those that are producing surface area (code, content, documentation) for her to test. The ratio of producers to testers can be used as an initial rule of thumb for how close to properly staffed you are. The worst case scenario I've had in my career was 17 ...


2

When they are not able to prove the value they add In my last position I wanted to improve front end error messages for invalid data in html web forms. My pleas fell on deaf ears. The company is focused on profit and costs. Then I used AB testing to show that better error reporting could earn the company millions of dollars a year. Next request for more ...


2

If there is adequate documentation of the work the dev team has done in a another tool, then I would try to get access to that tool and work off of that. However, if you still aren't able to gain the needed information, you should standardize what is included when a task is moved to Ready to Test. This could be a note in the Jira, link to notes from ...


2

First reaction should be, buy some time to investigate the issue and co-ordinate to fix the issue. Then let them know "we would investigate why the issue has been leaked from our testing". then, 1.Analyse why the bug has been missed, could be variety of reasons * Business use case wouldn't have been properly defined or not captured properly 2. Bug ...


2

"Working fine" and "seems to be working fine" will be interpreted identically, it's obviously based on your personal observations when it's you saying it. If you want to improve report quality, say "X thing did Y, as expected". Then developers know if your concept of "fine" is the same as theirs.


2

The point of testing is to provide feedback Generally, the quicker the feedback the better (shift-left) Pair with your developers until you get to the point that they can run the tests. Separating development and testing is anti-agile in my experience. Development and QA involvement is a two-way street at the end of the day. dev needs to make code testable ...


1

Actually it depends on the roles and responsibilities of the post you are hiring for. However, if a person is passionate, dedicated and quick learner, he will improve on the area in which he lacks(technical or communication). But you also have to keep in mind that any of the above skills will take some amount of time, so if it is feasible then you can make ...


1

I was a lead of an Agile-ish dev team for a couple years. The environment was pretty informal, and for me I would understand either of the statements you're giving as the same thing. What communications did arise regarded the following: If a tester says, "It looks fine," do they mean "It looks fine so far but I'm still testing" or "I finished all test ...


1

I think that your reaction should, in part, depend on the quantity and severity of defects being found in production. If they are finding minor issues, like misspelling a link name or similar, then I would acknowledge it, get it fixed and let them know how I will change the process to reduce the likelihood of it occurring again. If they are finding many of ...


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