For each requirement ...

Before programmers start their work the testers begin planning tests. It is important that we do so at this stage to be able to detect flaws in requirements and analysis. The testers are experts in their field of business, and this gives them a different view of the changes being developed. Programmers are more knowledgeable of the product at the point of view of structure and architecture.

Today I can begin to review the requirements, analyze in detail what will be doing and draw a test plan. For each requirement I will create one or more test cases. The tests that I run are not limited to written test cases, go beyond that.  In fact, test cases guide us in testing, they are a starting point. Some of the test cases I write will be used by programmers to perform unit tests.

Another important aspect is automating tests. I will have to choose what to automate. The selection depends on the complexity, how critical is the functionality and ability to be automated. I know that everything can be automated but cost varies and it is an important criterion that weighs on the decision to automate.

In the next few hours I will come to me with some doubts that I will have to clarify with the Product Manager. Depending on complexity of the Change Set, some meetings are organized in order to clarify doubts about the new functionality. Testers, Developers,  Technical Documenters and the Product Manager, all attend to these meetings. Anyway, the communication between the various people involved in the process is continuous.

Any defects found are recorded on a tool developed internally. Everyone access this tool and every defect can be monitored. It is possible to know at any moment in what state a defect is, who will fix it, who will test it, the expected date of resolution, etc. The whole story is transparent to everyone. This way each one has the responsibility for monitoring the corrective tasks to which is responsible.

During testing phase requirements changes may occur. For example, a defect can lead to a change of requirements. These changes can be treated in time, when they are simple, or when they imply significant changes, lead to other Change Sets.

This is the begining of testing phase.


Great readings

Communicating Testing using Visuals

By Rob Lambert

Communicating Testing using Visuals http://post.ly/1Ypxd

via Rob_Lambert

The Checklist Is Not the Purpose

By Catherine Powell

The Checklist Is Not the Purpose http://bit.ly/gnZvn8 by Catherine Powell

via Lubaia

Pair programming research misses the most important point

by Johannes Brodwall

Pair programming research is flawed by @jhannes: http://bit.ly/fxcklR

via smalltalk80

One Test Per Requirement

by Michael Bolton

Possibly my shortest-ever blog post: One Test Per Requirement.http://bit.ly/h4m371 #testing #agile #softwaretesting #qa

Via michaelbolton

Pairing is Conversation

By Michael Norton

Doc On Dev: Pairing is Conversation http://www.docondev.com/2011/02/pairing-is-conversation.html?spref=tw

Via Lubaia

Usability Testing with my Mortgage Adviser?

By Adam Brown

RT @brownie490: Blog post: Usability Testing with my Mortgage Adviser? http://bit.ly/f01QL5 #softwaretesting #testing #qa

via Lubaia

To close the year

Why is it so hard to teach “what we started to call ATDD”?

by Markus Gärtner

ATDD – that is acceptance test-driven development – is a requirements elicitation approach, which provides development teams with automated tests as a side-effect. (…)

#testing news: Why is it so hard to teach “what we started to call ATDD”? http://bit.ly/gtXvHc

via testingref

The Helpful model

by Henrik Emilsson

Here is neat story I told to Michael Bolton, Martin Jansson and Markus Gärtner when we were exploring the Metro in Copenhagen, during the coldest days the city had experienced since they started measure the temperature. I promised to blog about it…(…)

I love this story! RT @henrikemilsson Last night I blogged about “The Helpful model” http://bit.ly/gyc5A1 #testing #softwaretesting

via mgaertne

User Experience Testing: Communicating Through the User Interface

by Stephen Hill

A lot of time and energy is spent on making sure that the software components work together in different situations but how much time do we devote to making sure that the systems all work together cohesively to form an entire process?  How much time is spent making sure that the process itself can work correctly?(…)

Published last night: UX Testing: Communicating Through the User Interface #softwaretesting #qa #in #testing: http://wp.me/pRZ0L-1q

via Stephen_J_Hill

Q&A #1 – Young Software Tester Skills

by Shilpa Venkateshwaran

I am rephrasing the question that was asked by fellow ITKE member. His question: “Skills for Software Tester for 1 year Experience” (…)

Q&A #1 – Young Software Tester Skills http://bit.ly/ebNUEV #testing #softwaretesting #QA @ITKE

via shillu13

Quality attributes of the Cloud infrastructure

by Ewald Roodenrijs

Why does nobody worry where his or her email messages are stored? Where do these new apps get there information? Nobody worries about these things, but they don’t know what goes on beyond these applications an infrastructure is being used. This cloud infrastructure is, at least should be, tested to show the state of the quality. This also needs to be done for new cloud applications. But regarding the implementation of Cloud Solutions it’s not sufficient to verify that it works, it also needs to tested against some intangible quality attributes; the so-called non-functional requirements.(…)

RT @ewaldroodenrijs Quality attributes of the Cloud infrastructure http://bit.ly/hQYMyl

via Lubaia

What if you ditched your test cases?

by Peter L.

I have some questions for you testers out there who like using test cases. To be clear, I’m talking about detailed, stepwise instructions written in order to guide testing and be executed manually. (…)

What if you ditched your test cases? http://bit.ly/e4xA7N

via Lubaia


Your Chance To Shine

by Tony Simms

If you have any desire at all to speak, if you have any passion about what you do, if like me you have an over grown ego, then I highly recommend you give conference speaking a go. It really is not as hard as it looks. (…)

Be a speaker – Your chance to shine http://bit.ly/hXHGUW

via Lubaia