The V model has played a huge part of the evolution of developing that we see today. Legend has it that it was developed in Germany during the early 1990’s and its mission was to describe the complex ritual of what we today know as developing. The model describes needs, that gets broken down to System architecture which leads to detailed design. The steps of the V model have many names so keep that in mind if you ever talk to someone about this model. However, the fundamental principle is to create requirement(s) structure based on a need. The second and third level of the model describes that development takes place and at the bottom we so how the developed system is tested. At the “test” step we need to keep in mind what I wrote earlier; a step of the model can be called different things depending on who you talk to. Some refer to testing activities as Test, validation or verification.  All three concepts are important to consider when assuring oneself about the quality of the product/system. I keep this note always in my head:

January 2022 is not only the start of a new year, but also the official start of our new German System Verification office in Hamburg. Of course, our journey in Hamburg didn’t just start and our first Hamburg colleagues already joined us in October 2021. Michael Lucas, Prasanth Sivakumar and Andrei Suvorkov are very excited about the opening of the new office. Read what they think about the start in Hamburg and our future journey in the north of Germany: 

Here’s a list of stuff that my dog, and my role as a dog owner, taught me that I’ve been able to apply on my everyday work life in the field of QA.

I have always called myself a manual tester. But why really? What do I mean by that? It is very common in the test world to divide into two areas, automated tester or manual tester.

How often do you test a test case?

Two months ago, the well reputed Springer Nature journal SN Computer Science, published an article by our colleague Adha Hrusto and co-authors Prof. Per Runeson and Dr. Emelie Engström. The title was “Closing the Feedback Loop in DevOps Through Autonomous Monitors in Operations”. The work presented in the article has been carried out in collaboration with our customers in the region.

“Requirements, how complicated can it be?
Just listen to what the clients says, write it all down and you are good to go!”

Can everyone test? Yes!

Can everyone be a tester? No!