Testing 101 – Communicating the Value of Testing

 The Ministry of Testing (MoT), Accra, once again held an interactive meetup session at the German-IBT office. The event which happened on March 14, 2020, was aimed at understanding the ‘Value of Testing.’

Here are some key highlights:

 

The Software Development Life Cycle

The event kicked off with an overview of the basis of software testing. This was achieved by explaining the Software Development Life Cycle.

Image result for the software development life cycle

 
The Value of Testing

Next was the main agenda — with members trying to find answers to this important topic. Through this, attendees got the chance to reflect on the following, as testers; 

– Why add value
– What values can be added
– How to add them and
– When to add them 

The session was made more interactive with the introduction of a ‘post-it’ note system, where everyone wrote down and shared their answers.

WHAT?

Testers used this as an opportunity to learn from each other about value. So for the question; ‘What values can be added?’, here are some of what was suggested:

  • Fast Development and Delivery Process
  • Double – Checking (2nd Eye) for the developer
  • Finding defects and handling error
  • Continuous Improvement of Application
  • Deploying products with great user interface and experience
  • Longevity
  • Customer Satisfaction
  • Improved security
  • Improve code efficiency

 

Some participants displaying their post-it notes

HOW?
How testing and value addition is implemented differs from team to team. Hence, we touched on the several efficient and effective ways testers do this.

Some points raised include;

  • Asking questions about the product 
  • Understanding system requirements and their objectives
  • Generating meaningful reports
  • Working together with stakeholders (developers especially)
  • Posing as a user/customer
  • Knowledge Sharing 
  • Being concerned about projects
  •  Automating tests
  • Using appropriate development methodologies
  • By giving faster response/resolving any issues from feedback been given
  • Constant verification of code at any stage
  • Ensuring security by creating a two-way authentication system embedded in the app.

WHEN?

Different organizations introduce testing in their development process at different stages. In a typical agile environment, it is easy to find testers working with stakeholders right from the beginning of a project. Therefore, we discussed the various periods when project testers should/can contribute:

  • Beginning of a project
  • During development
  • During project reviews and sprints
  • Right before production
  • After Production

 

Quick Tips on Adding More Value

We wrapped up the day’s event  with a short discussion on manual and automated test tools and some take-home tips on value addition. These were:

  • Be concerned; about the project and believe that your team members are concerned too.
  • Offer solutions; to challenges at work or on the project that may not necessarily affect your work.
  • Offer to lift some work weight off your colleagues.
  • Improve your skills.
  • Be proactive in preventing bugs rather than reactive. It may be too late to fix bugs at the time of production.

 

Adea, a member of the MoT, explaining a concept

Testing 101 was all around an exciting and educative experience!

Here are some more images from the event:

Keep reading our blog and check our social for more updates on our upcoming events.

Follow us on:

   @thegermanibt

  German Institute of Business and Technology

 

READ MORE: AZUBI AFRICA: The Journey So Far & What’s Next