Keeping Stakeholders Updated Is Crucial for Quality

Testers shouldn’t be the only ones who care about the software quality. In fact, software quality is one of the most, if not the most, important goals of a software development organization and it’s a shared effort of all parties involved.

There are multiple teams and roles that are in charge of different stages of the process and testing is certainly a part of it. So, it shouldn’t function separately and shouldn’t be treated as a standalone component.

It’s necessary to keep all the stakeholders updated with testing activities

Let’s take the role of a product manager as an example. Although testers and QAs are responsible for most of the testing, a product manager is the one who can see the whole development and delivery process. Before a release goes into production, he/she has a voice to say whether it’s a go or no-go.

And one of the key factors to decide is whether the quality is up to standard through testing or whether any major critical bugs are found during the regression or functional tests. It’s extremely important that the product manager, and decision-making stakeholders, are informed of the quality state as soon as possible.

Testers, developers, product managers, and stakeholders all need to collaborate to assure software quality. So, it’s important that they can get updated with the latest test results to assess the quality and take action.

Then, how to get this done, and how to get it done with the least resources and time spent?

Notify the right people with test results via emails automatically

One of the means to maintain communication effectively between parties is through email. And Katalon supports users to send email notifications to inform different stakeholders about test reports. It’s a simple solution yet can enhance team collaborations significantly.

1. You can configure to send email notifications automatically, what, when, and who to receive. Automated tests are executed very frequently. Let’s say, you run multiple test suites or test suites collections on a daily basis. If you decide to report to your manager, or clients, via email manually, it would take a significant amount of your day, and you need to jump between tasks to write report emails if the executions take place at different times throughout the day. With email notifications made automated, you can focus on doing your main tasks while stakeholders are still aware of the test results and quality.

2. With an email template in place, your team can have standardized and consistent reports. Image your team has many members, and each one reports on different information with different structures. This might confuse the stakeholders who are reported to. With a template, you don’t need to spend time thinking about what to write or remember what fields or information to mention in the mail.

3. You can easily personalize and customize your report emails, from the subject to email content in the template. You can even use parameterized global variables to override the values in email settings, including sender, recipients, Cc, Bcc, subject, and also in the body template.

Let’s say, you provide testing services for 3 clients. Then, you can create an execution environment for each client, and apply a global variable to your email report settings. If you run a test suite with one of the execution environments, the report email will automatically be sent according to the predefined global variables in that environment.

Here are some resources on how to use these functionalities in Katalon:

Some best practices for email notifications

1. Having automatic email notifications is great but you certainly don’t want it to be spammy. Consider selecting to send reports only when your executed test suites have failed tests.

2. Choose an informative format for your email subject. Some information that you may want to include is the test suite name, purpose, and the version of the application under test.

3. What email reports to send depends on what tests you run. For example, the 8.4.0 version of Katalon Studio focuses on enhancing certain API testing features. Certainly, functional tests will be executed to validate the software system against the functional requirements as well as regression tests (to make sure that other core functionalities still work fine). So, the product manager expects to receive reports on those kinds of tests to see whether there are any major bugs or the quality is still assured with new code changes.

Special thanks to @Jass - our Katalon product manager for sharing this topic. Hope this article helps. Take advantage of this feature and keep your manager and other stakeholders updated with the software quality. Have a nice day!