Tagged Questions

Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.

My boss and i had a meeting today and the topic was concerned with downtime for dev or QA. We currently work in an Agile environment. My boss wants to start working on dev for the next cycle while QA ...

I'm trying to figure out how to provide an easy-to-manage requirements-to-code (and vice-versa) traceability to some projects which use SCRUM and JIRA. The projects use unit testing.
So I'm splitting ...

On one hand, it may take a while (or a long time) to create and run tests with TDD. The worst case scenario is when the test cases fail and the entire program fails. Refactoring may take longer than ...

Our organisation and clients expects us to give a sort of test "certificate" for each release.
Each release consists of a couple of three/four weeks sprints, including testing efforts as:
Automated ...

Currently most of the industries are using Agile based software development methodologies. And in Agile based development, we already have test cases in hand before development work starts. So, can ...

We would like to start using scrum in our distributed development team. Until know we used a "home-grown" methodology, but we would like to switch to something more defined and mature. Scrum would be ...

I was recently promoted to QA lead on an agile team working with offshore testers and an onshore development team. What kind of things should I expect? Any helpful tips for how to be awesome at this? ...

I'm a new QS tester in a company in an Agile environment. During the sprint commit I was told that one of my tasks was going to be testing user stories? How exactly do you test something like that. If ...

In an agile environment, for sprints for small updates, what approaches to testing are recommended? Do we just do exploratory testing after the SUT has been built before releasing it or do we do both ...

I am aware of the fact that agile testing is an ongoing process and should happen in parallel to development. But how is that actually achieved? Is it even possible to fix all found issues in the same ...