ISO certifications are a key part of how System Verification drives quality and sustainability. By being certified under ISO9001 and ISO14001, we ensure not only that our processes are efficient and structured, but also that we actively take responsibility for the environment. We sat down with Jonas Gyllenspetz, overall responsible for our ISO Certifications and our internal auditors Eric Järdemar, and Fredrik Hägg, to gain a deeper understanding of how ISO certifications impact our daily work and how they help us continually strive for improvement.

In the growing landscape of the financial industry, quality assurance (QA) professionals face many challenges in ensuring financial software's robustness, security, and compliance. This blog post dives into the challenges faced by QA teams within the financial sector and provides insights into their perspectives and strategies to address them effectively. With strict regulations, rapid technological advancements, and the need for seamless user experiences, QA teams must employ innovative and comprehensive approaches to uphold the integrity of financial systems.

As someone who transitioned from software development and data science into the world of quality assurance (QA), my first weeks at System Verification were a whirlwind of discovery. While my expertise in machine learning (ML) and MLOps was warmly welcomed, I quickly realized I had to learn more about QA and testing. It was a steep learning curve, but the eagerness of my colleagues for technical insights gave me a clear mission: to bridge the gap between our strong QA foundation and the rapidly evolving AI landscape.

We are excited to announce that we have joined Open Tech, a vibrant network that recently underwent a transformation from its original identity as Mobile Heights. This change reflects a forward-thinking approach to technology, inclusivity, and collaboration, values that deeply resonate with our company as we continue to innovate in the tech space.

In the ideal worldof software development, releases should be moments ofcelebration. It’s the timewhenour hard workfinallybecomes a reality, delivered to the users. Yet, insteadofjoyousmilestones, releases oftenbecomeourgreatest source of stress. We plan ceremoniesaroundthese releases, but the anxietyoftenovershadowsany sense ofaccomplishment.  

So, whydoes hearing thatsomeprojectshavemultiple releases a dayoverwhelmuswithanxiety, and why do wehesitate to try adoptingthis approach ourselves? Why do we still runaway so much from continuousdelivery and from trulystandingbehindourwork? 

In the thrilling race to utilize the power of generative AI, companies around the world are jumping on the bandwagon faster than you can say “artificial intelligence.” But, as the saying goes, "Not all that glitters is gold"—and not all AI projects are destined for glory. In fact, according to a recent article from Computer Sweden, nearly a third of these shiny new AI projects might end up in the digital dumpster. Ouch.

At our company, we truly value the loyalty of our employees who choose to stay with us over the long term. It's incredibly rewarding to see those who have been with us grow and develop, taking on new roles and embracing various educational opportunities along the way. We take pride in creating an environment where our team members can build their careers and achieve personal and professional growth. Kerim Kurtagić has been a valuable member of our team for eight years now, and here he will share some of his journey insights.

In our last article, we discussed how important it is to follow the most beneficial and crucial recommendations while developing or maintaining test automation solutions. The benefits are large and well worth the time and effort required to acquire them.

In this article, we will continue with recommendations. 

As previously said, there are numerous suggestions and practices that should be followed when developing AT solutions.

Most QA engineers today are already following the standard of implementing test automation solutions on their projects. But are we assessing our AT solution to ensure that we are getting the most out of it? Do we use AT recommendations and best practices, and how crucial is that? Is it even possible to apply best practices to every project? 

Let's find out together.