Blog

October 26, 2016

Was God a Tester?

The world of testing is an exciting dissection of the programs and software we use in our every day lives, in our interactions with businesses, our workplace and our friends. Our creations are there to make our lives easier, better, more enjoyable, yet we find that they leave us frustrated or annoyed. This is a tester’s job, to interact with these systems and make sure that when the system is released it can be used reliably.

God started with the creation of heaven and earth, ending with the creation of mankind. With a 7 day timescale and managing to create everything by the 6th it would seem as though the project was going well. We’re currently 4.543 billion years into the systems lifecycle and with a world history full of defects I think you could say the projects running a little over. 

Integration testing - “They want to speak how many languages?!”

Integration testing is the phase in which individual modules are combined and tested as a group. As a Tester it would be preferable to test all interactions. With 7.125 billion people, over 1 million species of animals and 196 differing countries, a lot of testing was needed. Maybe testing with 2 people and a snake wasn’t the best representation of a real life scenario.

If history has taught us anything it’s that integration isn’t mankind’s strongest trait. We seem to have a really hard time integrating with anyone outside of our small groups, I think we’d have to say that this area of testing was lacking.

Risk analysis“It’s a piece of fruit, in a garden, what could possible go wrong?”

Risk analysis is a method of trying to prevent a projects failure by predicting what areas of a system will require the most attention and testing. With risk analysis you can identify the potential risk of adding additional systems, in our case you’d have to agree it was all pretty much downhill from that first bite. 

Waterfall vs Agile“I can knock this out in a couple of days, no worries"

A project run under a Waterfall methodology follows the simple process of starting with a design going into development and ending with the testing phase. Whereas an Agile methodology allows the creator to take an iterative approach – developing the system in sprints. Repeating the Waterfall method over and over, starting off small and growing the system up piece by piece. Agile is arguably better for larger projects, like earth, but it seems as though after day 6 the system has pretty much been left to run on its own. With defects growing and evolving to the point of self-awareness.  

We may have been left with no aftercare technical support but unlike the latest piece of technology we can’t just trade this planet in for another. This is our home and we’ll have to fix this ourselves.

 

By Mike Tindal, Test Analyst, Edge Testing

Back