07.10.2026, 02:26
(This post was last modified: 07.10.2026, 02:47 by Stanley Durham.)
That’s the best use case for AI.
I wrote an array for FB. I asked it to test all procedures with edge test, noting how many passed and failed. This code would be a lot of work if I had to write.
115 tests for 23 procedures.
You can tell it to do all kinds of tests because you don’t have to write the code.
I used AI to provide F256 floating point for FB. Just for kicks, I had it do an extreme test just now.
This is the prompt I gave it:
“test all procedures with all possible edge cases”
“at the bottom, note how many passed and failed”
208 tested, 208 passed.
Initial, it did find some rounding errors, “Note on the precision boundary: 78 significant digits (F256_NDIG) slightly exceeds what a 256-bit mantissa reliably holds (~77.06 digits), so values with non-terminating binary expansions (e.g. 1e-3, 1e-5) do not round-trip exactly as strings.”
Fixed it and tested it again.
3m, 45s; done deal.
I wrote an array for FB. I asked it to test all procedures with edge test, noting how many passed and failed. This code would be a lot of work if I had to write.
115 tests for 23 procedures.
You can tell it to do all kinds of tests because you don’t have to write the code.
I used AI to provide F256 floating point for FB. Just for kicks, I had it do an extreme test just now.
This is the prompt I gave it:
“test all procedures with all possible edge cases”
“at the bottom, note how many passed and failed”
208 tested, 208 passed.
Initial, it did find some rounding errors, “Note on the precision boundary: 78 significant digits (F256_NDIG) slightly exceeds what a 256-bit mantissa reliably holds (~77.06 digits), so values with non-terminating binary expansions (e.g. 1e-3, 1e-5) do not round-trip exactly as strings.”
Fixed it and tested it again.
3m, 45s; done deal.