Tag Info

New answers tagged

0

To me an Agile Tester is someone who does not work in a phase. The goal of the Agile framework is cohesion among the team. Everyone is involved in communication and tackle problems as they arise. Example the QA analyst finds a bug, notifies a dev member of the issue, if the bug is not verified as previously existing they work together to implement a ...


1

Janet Gregory most famously known for writing one of the go to books of our time on Agile Testing, Agile Testing: A Practical Guide for Testers and Agile Teams, Defined the Agile Testing process in a presentation i recently watched found here on skills matter. Project Initiation: Get an understanding of the project(business) Release/Project Planning: ...


4

I'd suggest you start by taking a look at some of the related questions and their answers, particularly this one and this one. Also, if you don't have Crispin and Gregory's Agile Testing, get it. Some things that I've found helpful include: Test plans will still happen - but they tend to be much more lightweight and built as you test. Some tools support ...


2

Agile testing generally means the practice of testing software within the context of an agile workflow. When testing in an Agile way, there are few, if any, rigid adherence's to requirements documents and checklists. The goal, instead, is to simply do whatever is necessary at any moment to satisfy a customer’s requests, replacing documentation with ...


2

Is Exploratory Testing a core part of Agile Methodology? or it has no link with Agile process. Kindly explain in detail! Let's look at what each one of these things is and then see how they might go together. Exploratory testing is an approach to testing. You can use any test technique in an exploratory or scripted way but the important thing about ...


2

I think exploratory testing is one of the (agile) skills you can use in an Agile team to increase quality, but it is not an essential part of the Agile workflow. Though I think its slowly becoming a industry standard. Revised books like the Art of Agile and newer books Agile testing are giving it their own chapter. This clearly means its a technique worth ...


-1

Following are the ones that immediately comes to my mind when I think of Agile Methodology. SCRUM Good Automation coverage Follow Sprint model. Pair Programming Mandatory Code Review by peers. Well defined Acceptance Criteria CI / CD Model to take care of continuous integration / deployment One push deployment Exploratory Testing being a purely ...


1

In addition to the other responses: There is always a "specification" in the form of the software itself. Even if there are no user stories or other formal documents, there is a piece of software that does something. From that and the knowledge (however vague) of what the users of the software want it to do - the goal - it's possible to build a test ...


2

I've never heard of "reactive testing" so I'm not sure what exactly that means. Any idea? A blended strategy in the sense of using different test techniques and approaches can be a powerful idea but you (and your fellow testers) need to understand when to use them and when not to. Always make the strategic decision based on the context of your test project ...


0

In my view, this approach can be used only for less formal projects. Normally, test cases are required to exist to verify the functionality and to form a regression pack. This cannot be done without requirement-based strategy. With the suggested blended strategy, testers do not prepare test cases ahead and on most projects, you cannot afford to leave ...


0

That's exactly what we do. Using our own best guest, we evaluate risk of stories coming through the pipeline, test manually what is most important or we get feedback, or test cases as identified in requirements. In "plentiful spare time" we are building a suite of automated regression tests to cover core functionality. It is just common sense. What other ...



Top 50 recent answers are included