Thursday
Room 3
11:40 - 12:40
(UTC+02)
Talk (60 min)
Omg, how do I write software that isn't a ticking timebomb!?
2023 had some spectacular public software failures like the UK air traffic control failure of September which cancelled more than 2,000 flights cancelled due to “an extremely rare set of circumstances” involving two identically named but separate waypoint markers.
For any software project, the potential presence of certain bugs is a cost-risk-benefit proposition. How much time can one spend to ensure catastrophic failure does not happen?
Property Based Testing (PBT) is a technique which seems to uncover many bugs compared to the effort needed. It can also be incorporated early in the development process which decreases the effort required to debug.
This presentation looks at the hypothesis property based testing tool used in our Scientific Computing team at Equinor. We look at how it compares to traditional testing methods and verification techniques, and how we use PBT in our team.
Eivind Jahren
Eivind is a software developer at Equinor where he works on scientific computing that runs on HPC clusters. He is passionate about testing and can't stop talking about Property Based Testing after becoming enamoured with haskell programming. In his spare time he likes to ride bicycles.