SulAmerica brings standardisation and organisation AssertThat’s BDD for Jira
Industry: Insurance
Product used: AssertThat BDD & Cucumber for Jira
Use case: Standardised, centralised QA with native Jira integration
SulAmerica is one of Brazil’s leading multi-line insurance providers
SulAmerica provides a wide range of insurance services—including health and dental, life and personal accident, asset management, and private pensions. With a long-standing reputation in the Brazilian insurance sector, SulAmerica is committed to innovation and operational excellence across every part of the organisation.
Before adopting AssertThat’s BDD for Jira plugin, SulAmerica’s QA processes lacked standardisation, and test scenarios were not consistently documented or easily accessible. This made it more difficult for teams to maintain visibility over test coverage and to ensure alignment between test scenarios and user stories..
A straightforward approach: embed QA into existing workflows
Rather than introducing new tools or processes that would increase overhead, SulAmerica took the approach of embedding test management directly into the systems already in use. That led them to adopt AssertThat BDD & Cucumber for Jira, a native Jira plugin that enables teams to write, organise, and manage BDD scenarios within Jira itself.
According to their QA team:
“The main benefit of using the tool is the standardisation of processes and the possibility of having all quality information gathered in a single place.”
This shift allowed them to consolidate their test scenarios, create a shared source of truth for QA, and improve the transparency of testing across teams.
Practical advantages in tagging, linking, and documentation
One of the key improvements SulAmerica noted was the ability to use tags to organise and track scenarios. Tags made it possible to group tests by functionality, feature, or sprint — providing a clear way to manage and review test coverage.
Scenarios were also directly linked to Jira user stories, creating a consistent relationship between requirements and test cases.
“We can mention some examples such as: the use of TAGS to track the scenarios back, the possibility to link test scenarios to Jira User Stories, and the documentation of test scenarios in one place so they don’t get lost along the way.”
This level of organisation made the testing process easier to follow, especially for teams working across multiple projects or domains. Crucially, it ensured that QA wasn’t treated as a separate or siloed function, but part of the core delivery workflow.
Outcomes: better visibility, more consistent coverage, increased maturity
By using AssertThat, SulAmerica saw meaningful improvements in how QA was perceived and managed within the organisation.
“By using the platform, the team now has a better vision of QA’s work and a greater control over deliveries.”
They also noted that the number of test scenarios written had increased, along with a measurable shift in how teams approached quality — with more structured processes and better test discipline across the board.
“Another positive thing to mention is the increase in the number of test scenarios and in the quality maturity of the team.”
These are incremental but important gains — and for large enterprises where QA must scale alongside delivery, they’re key to long-term improvement.
A practical solution for teams who already use Jira
AssertThat BDD & Cucumber for Jira provided SulAmerica with a straightforward way to improve test quality without reworking their existing toolchain. It sits inside Jira, requires no context switching, and supports BDD workflows in a way that’s easy to adopt across teams.
If you’re working in a technical leadership role and looking for a way to improve visibility, standardisation, and traceability in QA — particularly in Agile delivery environments — it may be worth reviewing the solution SulAmerica adopted.
