RSS

Common Testing Issues

21 Jul

What are the key things that we find are issues for software testing? How can we address these problems? In my experience we usually have a solution to most of the problems – we just need to identify the problems and then we can workshop the solutions!

Here is my top 10 problems
1. late delivery of code
2. poor requirements
3. wrong requirements
4. late engagement of the testers
5. shoddy code
6. problems in communicating with PMs
7. problems in communicating with developers
8. lack of career growth
9. lack of exposure to/access to test tools
10. lack of training on tools

What are your key issues?

Posted by Sharon Robson

Advertisements
 
4 Comments

Posted by on July 21, 2009 in Testing

 

Tags:

4 responses to “Common Testing Issues

  1. John Watson

    July 28, 2009 at 11:34 am

    My key issues are:
    1. Sketchy or non-existent business benefit requirements
    2. Non-testable functional/system requirements
    3 Absent quality (aka non-functional)requirements
    4. Premature delivery of code
    and everything else on your list Sharon

     
  2. James King

    August 2, 2009 at 10:53 am

    I think there are two key issues
    – We (testers and the team) think testers should be able to simply walk in and test the system without time for learning, understanding and communication. So testers feel they should succeed on a project without being set up for success
    – Many team members think testing is a separate function – “I do stuff and he/she tests it”.

    The simple answer is to engage testers early to both learn about the project and help the crew with how to validate their own work (ie prove it had value).

     
  3. Sharon Robson

    August 3, 2009 at 10:57 am

    Good points John, although the concept of “premature” delivery of code is interesting. It can be benefitial to get code early, even partitially completed code, but if it is not yet ready to test, it can be delivered too early.

     
  4. Sharon Robson

    August 3, 2009 at 10:59 am

    James – you have hit the nail on the head, we need to have testers involved earlier and we need to encourage everyone in the project to be focussed on Quality. This would work to swiftly eradicate my “top 10”. But….how do we convince people to do this??

     

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: