Welcome to the Debugging, Testing and Correctness workshop

Within modern, complex software landscapes, developers typically spend a significant proportion of their time on debugging. Studies estimate that more time is required to find bugs than to write actual code. This has a footprint beyond lost productivity: on HPC systems, buggy or incorrect code often means jobs are rerun, partial results are discarded, and compute cycles — and the energy and cooling that go with them — are wasted at scale. Finding bugs and delivering correct(er) code the first time becomes both an efficiency and a sustainability imperative, yet it also becomes more difficult with modern HPC systems, which offer unprecedented concurrency: the systems become heterogeneous, i.e. process code differently, bugs become non-deterministic, different programming models are used in combination, and standard debugging tools are no longer applicable.

The sessions targeted PhD students, Postdoctoral Research Associates (PDRAs), and Research Software Engineers (RSEs) who develop massively parallel data analysis and simulation codes for High-Performance Computing (HPC) ecosystems. Their main focus was on:

  • Debugging
  • Testing 
  • Correctness
Last modified: Tuesday, 21 July 2026, 10:57 AM