Since OpenAI came up with ChatGPT, rumors about the upcoming improvements of Artificial Intelligence are omnipresent. In this article, I want to discuss, if and how we can use chat-bots for software QA and Test Automation. Therefore I want to use ChatGPT. The tool is designed to give detailed answers to questions, using multiple Sources with the ability to summarize complex topics. Before I start to discuss how we can use this technology for Software QA, I want to point out how ChatGPT works. I am not an expert in the field so I had to ask someone who knows exactly what’s going on behind the scenes. I asked the only real expert within the field that I know and that is – you guessed it – ChatGPT itself.

For the Question of how ChatGPT works, I got a response that was a bit too long so I asked it to sum it up into two sentences. Here’s the response:  

Every once in a while we host and share games and events for our QA network to attend for challenging themselves within our field. Two of those challenges are Solve a problem and Bug hunter. Sometimes we host them during specific events to take part in IRL at a job fair for example, and sometimes we host them on our website and social media. 
To make the most fun and challenging activities to share with you, we have to use highly creative and skilled people (and we have lots of those people in our company).
So let us introduce two of the brains behind some of the challenges - Mille and Selma! 

Let's go through some of the things that happened this year!

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

I live with my family on a horse farm 150 kilometers from my workplace.

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.

Quality assurance engineers are quite often perceived as master bug hunters. They are fearless, opinionated, and always ready to enable a destructive mindset. However, intentions matter. We intend to support the team in delivering top quality to the end users of our systems. But does it only involve catching bugs?

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.

Automating manual tests for a software application helps reduce significant costs of a test cycle where a lot of the test steps involve repetition of the same actions. The prime candidate tests in a test cycle for automation are regression tests and smoke tests. By automating these you save a lot of resources and mainly the test cycle duration.

Each framework for your business has its benefits, and not every framework can be considered a "one size fits all" solution. When it comes to choosing which framework to use and why, you may come to a dilemma as to which to choose, and for this very reason we are here to help and better explain this educational theme. Our colleague Omer, who had the chance to work as a QA on a variety of projects and in a variety of teams within our company for a long time now, wrote this excellent blog that will guide you on how an organization or team evaluates what methodology and framework is the best fit for them and their client needs. Omer has been with us for more than three years, and through different ways of working and different approaches, he has seen how everything affects the teams and their deliverables, and he wants to share his experience now through this quality blog with you.