Blogs

Endur release testing starts with a list. Every release arrives with one: report definitions, regulatory reporting, queries, tasks, plugins, trade templates, simulation definitions, scripts, date sequences. Each item is deliberate. You know what you changed.

Every ETRM/CTRM team has a regression test pack. Most teams privately suspect theirs isn’t covering enough.

Every ETRM/CTRM team runs regression tests. The interesting question is how. Manual vs automated regression testing isn't really a debate about tools, it's a decision about what your platform can absorb: how often it changes, how much risk sits behind each release, and how much of your team's time ...

Why “did that change break anything?” is such a hard question to answer Every other question about an ETRM/CTRM change can be answered late. You can review the approval trail months afterward, reconstruct who signed what, and pull the release notes years later if anyone asks. One question doesn't ...

Trinitatum has achieved ISO/IEC 27001:2022 certification, issued on 3 August 2026 and independently verified by Insight Assurance. The certification covers our Information Security Management System (ISMS), which supports the development and configuration of Triangle Test Automation.

That's exactly why it's a problem. It’s one of the most reasonable things a compliance officer can say, and it comes up often: “Compliance isn’t a testing problem.” They’re right. Compliance isn’t about whether a test script ran last Tuesday. It’s about whether the transaction report you filed was ...

Here’s a scenario worth thinking through if you monitor position limits. You come in one morning, nobody on the desk has done anything unusual, no new trades of any size, and yet your reported limit utilization has moved. Far enough, in the worst case, to put you over a hard regulatory line. No one ...

Interview written by Dr. Gary M. Vasey, at Commodity Technology Advisory.

Why the routine changes to your trading systems are the ones worth proving.

Ask a testing team how they know a test has worked, and you'll usually get a technical answer. But strip the question back and something more fundamental sits underneath it: how do you know what the right answer should be in the first place?