Tag Info

I feel like certain teams or people are in need of tough love when it comes to this. When there is a quality issue, point out that it could have been prevented by the rest of the team following some best practices. For example, if there are frequently broken builds, broken deploys or entire features that are blocked or not functional due to bugs you can ...

Part of this starts at the top. Among other things, the team's performance should be judged in terms of quality. You need to choose your quality metrics carefully so that the team's goal is to improve quality rather than just improving the metrics. For example, if you measure the team by bug count, people will stop logging bugs. Organizations go through ...

One way could be to get them to do end time with the end users and customers so they are aware of the impact of their work and don't just interact with a keyboard and screen. The company has to have a culture of it as well and it has to come from the top with managers leading by example A quick google for 'culture of quality' will bring up lots, e.g., ...

As with all positions the title means whatever the hiring company wants it to mean, nothing more. The term "QA Engineer" might mean "Tester", "Standards Enforcer", "Auditor", "part-time Developer/Analyst", all of these, or none of these. I've seen them all. In my company, the team used to consist of "QA Engineers", until we were purchased by a larger ...

The two obvious steps that you seem to have missed out: Perform the tests. Much may be done auto-magically, but manual testing is still a key aspect at integration and system test levels. Report the results. Whilst automated tests may generate a results file, you'll need to interpret and present the results in a format that is appropriate to the ...

INHO the testers' responsability is the sameone that all other roles' responsibility: to contribute as much as possible to the success of the project. That is, keep an eye on the ROI of every one of your activities. Keep a balance between the cost and benefit the project (and the whole team) will get for those activities. Keep aligned with the project and ...

Thank you for the opportunity for me to delve into the theory of testing and Quality Assurance. As you seem to be mostly interested in the role of a test specialist in software realization projects, I will keep the scope of my answer in that general area. Please keep in mind that most here is written from my opinion and experience and less based on books. ...

The term itself is kind of subjective without more context. In your link you refer to Live Mesh and since someone felt the need to explain (although not very clearly) what a platform experience is it might be an indication how subjective it is. Wikipedia has a definition to the term experience design which may be a new or more prominent consideration in ...

In the section "Where to draw the line?" of "How to Make your Bugs Lonely: Tips on Bug Isolation" the author says: There is no clear dividing line between the bug isolation and reporting that the tester does and the debugging that the programmer does. The authors lists then: factors in favor of having testers put significant effort into isolating ...

TL;DR Developer = Let's make something! Tester = Let's blow it up! When I took my first job in QA, I would describe what I did to people this way: I have a hammer and screwdriver and someone has just pointed me at a grandfather clock with instructions to tear it apart to find out how it works and, and...(this is the best part) I don't have to put it back ...