Search Results

I have to admit when I read this my first thought was "I didn't know you worked for my employer" I'm facing similar difficulties as one of a team of six testers working with about two dozen developer …

Why don't test engineers write unit tests? There are several reasons developers are usually tasked with creating unit tests: Developers are intimately familiar with the code they are writing. They …

The role of a software tester in an agile environment - as with any other environment - is whatever it needs to be for that specific project. Sometimes there'll be a lot of close-up work with design a …

Ideally there should be a regression or "hardening" sprint before the project ends, and in the dream world, a hardening sprint every few cycles. I'd suggest that automated tests of the steel thread …

I'm with Joe on this one. When there's a reward only for the "best" - no matter how that "best" is determined, there's an immediate temptation to game the system and an incentive to undermine teamwork …

This is the exact problem that bedevils the environment where I work, and have yet to find a strategy that works well and consistently. Some of the strategies and techniques that help are: The test …

As Suchit said, it depends a lot on the nature of the update. I've seen a one-line code change trigger a full regression because that one line happened to be in one of the core calculation engines. M …

It depends on the fix. If the fix is something that hits low lying functionality used by the entire system, then the entire system needs to be regression tested. If the fix involves the functionali …

It depends. Unit tests are probably not the best way to test software localization because there is typically a single function that retrieves the proper text from the application resource dictionary …

What you need here is to maintain linkage between your AC, your user stories, and the features - there are a number of test management tools to do this, which you can integrate with your issue trackin …

Ideally, the DoD for each user story should mean all tests for that user story are passing, and all automation is completed, running as part of the overall automation (as opposed to on one person's ma …

I'm going to go with my favorite answer here - it depends. Here's why: often testing is black-box, and testing tasks can have little relationship to programming tasks within the same user story, par …

It sounds rather like you have the typical "agile-but..." implementation going. There are ways around it that avoid the overhead and issues that go along with GUI-based automation (which can be done …

I second (third?) the congratulations! While I'm nowhere near as experienced as Joe or Bruce, I can offer a few tips from experience: Communication is critical - you absolutely must have at least …

In my opinion, there aren't any extra skills need to test a stable system. What tends to happen once the system is stable and not under continuous development is that the proportion of time spent on e …