Testing? Making beer? They have one critical component in common. When done right, the results can be … Fantastic.

Quality Assurance, or QA testing, is an important step in the software development process. By discovering defects early in the development cycle, QA testing will save time, money, and frustration. Faster and more frequent software releases create room for error, which makes quality assurance a vital part for the success of any fast-paced development. With QA being the core business of SYVE, we are naturally excited to recognize and celebrate World QA Day.

A person that has put his heart into QA over the years is our CEO of System Verification Sweden, Fredrik Grimsberg.

Have you ever wondered what agile regression testing means and how to do it well in the IT industry? Whenever we introduce new functionality or an improvement, we need to make sure that existing functionality is not broken, which is something we achieve by regression testing. In agile, code updates happen more often so regression testing is of big importance, it must be effective, have good coverage, and prevent shipping any critical bugs to production. Today, our colleague Dalila Terzić, who is in the position of Technical Test Lead and has been in our team for more than four years, will talk about the significance of regression, which is a very important part of the testing process in order to improve your knowledge about the system under the test and have a more effective business in the QA world.

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: