Tag Info

New answers tagged

0

I worked on an agile team where we used a notecard for each story. Once we committed to a story we wrote out the user acceptance criteria on the back of the card. The language used was important because you do not want to provide a solution within a story, so your criteria has to address the problem being solved rather than how to solve it. This made it so ...


0

During each iteration for each story I like to-do the following: During planning: Are we building the correct feature? I try to look from a user perspective instead of a technical During development: Prepare test-data, pair program with developers and question UX of new developments After development: Risk analyses with a code review, do the unit-test ...


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


0

One of our software suppliers operates in this manor but we still found 39 bugs when testing their latest delivery. Mark Smith.


0

It sounds like they might be looking for more of a Test Analyst. You have the expertise to know what tests should be performed even if you aren't performing writing the tests yourself, and crucially you should know what tests cannot or should not be automated.


5

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


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


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



Top 50 recent answers are included