Tag Info

Hot answers tagged

6

The short version: regardless of the development methodology, your role is to provide information about the overall quality of the application. You do that via testing anything that isn't included in the developer-maintained automation, and reviewing the developer-maintained automation. The long version: This question and its answers is a good starting ...


6

Latent Bug : A latent bug is a bug which is present in the system from previous iterations or release (in your scenario Sprint 1). They are either low priority bugs, which either went undetected or were not reported. Here is a good description : What is a latent bug? Golden Bug : If a bug happens to appear, in every iteration or release, affecting the ...


5

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 ...


4

Point of testing units and components before whole system is to localize bugs BEFORE they damaged some unrelated part of the system, causing confusing red herring error. If you mock the surroundings of a component, you eliminated moving parts - and localized the bug. Of course you need to weight the effort to mock: because it is code, it will have bugs and ...


3

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 ...


3

As Agile teams need to be cross-functional, its handy if the team members itself are also cross-functional in their Agile skills including testing. One thing you want to prevent is having a mini-waterfall within a sprint. This leads to all the testing to be pushed into the end of the sprint, which could in turn bring your sprint commitments in danger. ...


2

I don't have time to do all the documentation, test cases, strategy, test plan, etc. I almost always recommend producing the minimum necessary documentation. Call it lean documentation, minimum viable documentation, whatever. You want just enough that helps plan and guide the testing you need to do. Anything more starts to lose value very quickly. ...


2

Actually, we're doing this exact thing you mention. Testing in the same three weeks as development is nefarious for testing time and quality overall, as you seem to have experienced. So, we're testing for two or three weeks after the development sprint has finished. By delaying testing for a few weeks, you'll be working on a fully delivered sprint ...


2

You seem to be focused on the technical aspects of doing software QA. I would say your background is good for doing test automation and finding bugs that are results of technical obstacles. However, it takes a strong will to put up with the amount of animosity you may have to control. I find troubling is that no one is bringing up the intense social ...


2

You have a very good background to apply, depending of the company maybe you have to learn something more than you know but just like everything in this life, nobody's born knowing everything. As Nike says Just do it! Finally want to share a very interesting article about QA role in agile teams ...


2

I was given this webpage to read, by my QA Manager: tips for quality testing. It really tells you what testers need to do to be a good tester. A few pointers I have learnt from reading such material, is: Find quality bugs and not quantity of bugs Prepare your documents early, as in create your documents / test scripts early before you start actual testing ...


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

Testing is not an individual function on a scrum team. The concept that developers develop and testers test (I coded it I am done, you test it) is a waterfall practice. The team is responsible for a feature getting into a "done" state. Testers with SQA experience or as their professional discipline bring value in their understanding of how to test and how ...


2

The best advice I can give you is to ask the other team what information they need to be successful. I've been in the opposite position where I'm supposed to automate tests others have made. Aside from this being a bad practice, creating too detailed documents or creating the wrong details will only waste both of your teams time. Send over what you have ...


2

Anybody can be the Scrum Master, just make sure the Scrum Master has no other conflict of interest roles as Product Owner, Manager or Stakeholder. Personally I think testers have the potential to be great Scrum Masters, because: Testers discover problems/defects, but often do not demand a certain solution. Its up-to the owners of the issue to find the ...


1

First, I want to echo milinpatel17 's answer. If they are not cooperating NOW, at the start of the process when people should be psyched about it (see http://www.1000advices.com/guru/project_mgmt_7phases.html ), how would they be a few month into the project? Specifically to your question: If you give them the scripts you now run manually, you will get an ...


1

You think it's impossible! Not really. Here is how to accomplish this. Short and sweet. QAs are involved in pointing the stories. You decide in sprint planning/refinement if any automation needs to be done on the story. Everyone including QAs know the effort it's going to take. So, you point them keeping that in mind. And, you mention that as an acceptance ...


1

You need to redefine what the definition of "done" is for a ticket. A ticket is not complete until manual testing, documentation, and automation are done. Project Managers might get upset at first but it's not hard to win an argument when you tell them the increase quality means.


1

If your management is so focused on short time returns that it will not invest in increasing your skills to improve your productivity - you should do it anyway in your own free time. All tools and documentation are free, you just invest your time. Of course your progress would be slower, but after some time you should be able to show some results, proving ...


1

In all of the agile projects I have participated in, we have used the same mechanism to track defects as we did stories. In many, but not all of the agile projects I worked in, we did not track defects for stories in the current iteration, instead we would note the defects in the story and push it back to developing. If we found a defect outside of the ...


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: ...


1

Unit testing is a great way to test code with specific endpoint values and compare them with expected results, but there are many things that unit testing cannot cover. Unit tests provide you with a linear test, for the software. Automation should cover a more broad approach to what the software actually does. Agile is a difficult space to implement ...


1

This might help: http://www.allthingsquality.com/2010/04/what-do-qaers-and-testers-do.html Every company is different. But here are some of the things my QA Teams do, in no particular order. Review and respond to requirements Participate in design reviews Participate in architecture reviews Create and maintain Test Cases Execute Test Cases Exploratory ...


1

It is my opinion that QA, Typically on a team using Agile development methodology, is an integral part of the software production team. Your primary goal is to verify developed software is appropriate to be released to the client by analyzing from their perspective. Here is a list of some of the typical responsibilities i have or have had as a QA analyst. ...


1

Can I work in this scenario with the above background? First of all, anything is possible. It's really hard to give advice without knowing more about you and your background. Describing your background in a short post on a forum like this isn't easy. Assuming the company who extended you the offer, knows about your current background and wants to hire ...


1

I have worked in each of these scenarios: DB is cleared after each test. Pro: No artifacts left over so test are a little easier to write. Con: The DB restore can take the longest if you do something, then roll it back repeatedly. You also need to ensure the rollback is successful. DB is cleared after each test cycle. Pro: No artifacts left over so test ...



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