Archive | Best Practices RSS feed for this section

Agile Thinking instead of Agile Testing

By on March 29, 2011 in Best Practices, On-Going Improvement

Is there such a thing as Agile Testing? I’m not sure there is…
You don’t need to work on an agile team to work and test based on an Agile Thinking mindset.

Read full story • Comments { 7 }

Teaching programmers to test

By on December 23, 2010 in Best Practices, Management, Tools

Yesterday I started providing short training sessions for agile programmers who need to learn how to test better.
Would you trust a programmer to test your application? It’s like asking a Fox to guard the chicken-house, right? Well, sometimes you don’t have a choice, or you do but that choice is to release the application untested…

Read full story • Comments { 8 }

The Power of Empowerment

By on November 23, 2010 in Best Practices, Test Process

Have you ever been on a situation where you need to test 10 things but you have only the time for 6 of them, and on the other hand you look at your development team and 2 programmers are done with all their important tasks and started working on stuff that sits under the “nice-to-have” list (or even worst, they went to the game room to “test the Wii”)? What do you do?

Read full story • Comments { 0 }

There is value in changing hats

By on November 11, 2010 in Best Practices, Communication, Test Process

It is important for developers to take responsibility for end-to-end testing tasks once in a while. It helps them to understand what matters to us when we do our job, and maybe even more importantly it teaches them to do their jobs better.

Read full story • Comments { 1 }

Creating your “Testing Zone”

By on November 2, 2010 in Best Practices, Test Process

Each of us has a specific atmosphere / way / routine that helps us test better. If you want to be good tester you should figure out how to enter your Testing Zone.

Read full story • Comments { 1 }

If you’re going to write-down just one test case…

By on October 31, 2010 in Best Practices, On-Going Improvement, Test Process

If you are going to write-down just one (more) test case, what would that test be?
Will you write a very descriptive (and deep down) test for the most risky component/screen in your application? Or would you write an end-to-end sanity/smoke test that goes over 80% of your system? This is a question to ask yourself whenever you sit to write down your scripted testing scenarios.

Read full story • Comments { 5 }