Crosskey: Increased Traceability and Overview – From Development to Maintenance
When Test Leader Wilhelm joined Crosskey, he noticed a need for better structure in the testing process. By starting to use Reqtest in the early phases of projects, the company has increased the transparency, traceability, and quality in both its deliveries and ongoing maintenance.
Crosskey Banking Solutions is a Nordic IT company specializing in developing and delivering banking and financial systems. With clients such as Mangold, it is crucial for Crosskey that their solutions and systems maintain high quality and function as intended. Wilhelm Lund, Software Test Lead at the company, explains:
“We aim to be a one-stop-shop and develop everything from mobile banking, online banking, card systems, or the complete suite a bank may need. The most important thing is to deliver the highest possible quality so the customer is satisfied.”
Scattered documentation and lack of traceability
For Crosskey, quality and performance in solutions are top priorities – both during development and maintenance. Reqtest was introduced back in 2012 to help manage regression testing. But when Wilhelm joined Crosskey in 2023, he saw that the tool could be even more beneficial.
“When I started, we had poor documentation of test coverage before systems went into maintenance. Test information was scattered in Excel, Notepad, and Jira. By documenting requirements and tests in Reqtest already in the project phase, everyone has access to the same information – which helps during illness or staff turnover.” – says Wilhelm.
A shared test tool and a new structure
Wilhelm and the team at Crosskey have begun the transformation by using Reqtest already in the project phase. Thanks to a Jira integration, requirements can be imported with a click directly into Reqtest and then linked to test cases and test runs, something that facilitates the transition when a project moves into maintenance.
“It’s easy to see where we are in the testing phases. Have we executed all the test cases we planned for these requirements or not? Are we on schedule, or do we need to postpone some and complete them later?”
Wilhelm Lund
Crosskey
“The advantage is that we now get better traceability in our deliveries. For example, if we get an incident in production, we can go back in Reqtest to see if the scenario was tested against the requirement or if we need to supplement the regression suite” – says Wilhelm.
This new way of working provides not only traceability but also better project oversight.
“It’s easy to see where we are in the testing phases. Have we executed all the test cases we planned against these requirements or not? Are we on time or do we need to postpone some and do them later? It gives better visibility into the delivery”, says Wilhelm, and continues;
“I like Reqtest. It’s user-friendly and easy to get started with in the requirements, testing, and bug reporting modules. Of course, the change will take time, but the most important thing is that we take small steps – and we will reach the goal eventually.”
Try Reqtest yourself
Fill out the form to test Reqtest for 10 days. You’ll be sent an email with instructions on how to activate your account.
-
Structure your tests, requirements and bugs
-
Delegate tasks and collaborate with suppliers or project members
-
Follow the progress and get approval before Go-Live