How programmers make sure that their software is correct

Re:How programmers make sure that their software is correct by ChrisMarshallNY on Thursday January 06, 2022 @09:41AM (#29824041)

I write UI and communication software.

It is pretty much impossible to write meaningful tests that cover everything.

This is especially true, when you mix complex, asynchronous server interactions, with random-access UI.

Today, I am fixing a couple of bugs in an app that interacts with three different servers (all asynchronously, but some semi-synchronously. The timing diagram is a bit ... intense), and also allows the user to do things like switch contexts, while some part of the server interaction is still unresolved.

I write a bit about my approach to testing, here: https://littlegreenviper.com/miscellany/testing-harness-vs-u...

[ Parent | on HN ]

Re:How programmers make sure that their software is correct by monkeyjoe on Thursday January 06, 2022 @10:16AM (#29824526)

I started reading through your site a bit. Great content.

Wanted to let you know that the "Here is the Doxygen-generated documentation for the BADGER layer" link is broken on this page: https://littlegreenviper.com/miscellany/forensic-design-docu...

[ Parent | on HN ]

Re:How programmers make sure that their software is correct by ChrisMarshallNY on Thursday January 06, 2022 @10:19AM (#29824576)

Hey, thanks!

I'll look at that.

[ Parent | on HN ]