It’s all about visibility
Most organizations use a test case management solution to aggregate test plans and report results across their many teams. This provides a single source of truth that allows management to understand the current state of quality across their applications. You can then identify areas for improvement across sprints and releases. The reality is that automation makes this sort of centralized reporting more challenging, since most organizations use disparate automaton tools. Every tool is different, which means that many testing teams will review results from automation tools and then manually update the results in their test case management system.
Reporting in this way is clearly inefficient. Worse, it’s also incomplete, since the manual results don’t include key details such as screenshots and log details to troubleshoot failures. Furthermore, most automation tools rely on test scripts or other forms of code. So, understanding why tests failed or even what has been automated is hidden from key team members such as quality analysts, business stakeholders, or management.
We think this is wrong. Our mantra for testing is the more the merrier! We believe that automated test scripts should be easy to create and even easier to understand. When more people can understand your tests and can view execution results, it will ignite conversations earlier in the process. Your team can achieve higher quality, faster and quality becomes more strategic because of its increased visibility.
Increase visibility and report both manual and automated results in TestRail
Rapidly increase automation coverage using Architect
Why is TestRail so important?
In the spirit of collaboration, we now provide native integration with TestRail. TestRail is one of the most popular test management tools on the market. It allows testers to see the status of testing across different teams and products. Our integration allows you to share execution results from Functionize into TestRail, so you can build reports with all your test results from a single place. Better still, we don’t require you to install a desktop client or acquire extra software licenses.
How does it work?
It couldn’t be easier. Simply link your TestRail test from the related Functionize test. As you execute your Functionize orchestration, the results will be visible from the TestRail test run. And remember, the more the merrier. Navigating between Functionize and TestRail is a doddle with clickable links for every test, so collaboration is as easy as pie. Once you’re in Functionize, the test details are easy to understand, with screenshots for each step. Diagnosing test failures is simple thanks to our powerful visual testing approach, letting you compare each step against the previous successful run.
Visibility for all your TestRail users
And the best part of all this? You don’t need extra Functionize licenses in order to view the details in Functionize. Functionize subscriptions are based on the number of test executions, so you can allow anyone from your team to access the results in Functionize without the need for a license. This is a big difference from many other test automation solutions which rely on strictly limited licenses.
What other integrations are available?
Integrations are incredibly important to ensure that your teams are working efficiently together. After all, testers are part of a much larger engineering or IT organization. It’s not uncommon for a large enterprise to have hundreds of applications used for application development. That’s why Functionize has a multitude of integrations with the most commonly used tools.
One of the most popular tools to connect is Slack. You can notify your whole team when Functionize tests are executed or if there are failed tests. Simply select the Slack channel you wish to send results to, and your team can click the notification to view the details in Functionize.
Another popular integration is Jira for defect management. Developers love all the log data that can be found from Functionize results. This combines with all the screenshots we capture to give a powerful way to understand how to reproduce and fix bugs quickly. Speaking of developers, most organizations have a CI/CD process. Functionize tests can be triggered alongside CI builds easily. Just use our native integrations like Bamboo, Jenkins, GitLab, or TeamCity. Or, you can use our APIs to build a custom integration to seamlessly fit Functionize into any toolchain. To learn more, book a demo with our sales team.