News for hackers. Stuff that matters.

A comment on Old C code – how to upgrade it?. Parent comment

Re:Old C code – how to upgrade it? by HenrikB on Friday April 08, 2022 @03:15PM (#30961331)
Maybe also:

- Write lots of tests with high test coverage before migration. Then you can rely on them on a continuous basis to make sure any updates do not break the existing functionality

[ Parent | on HN ]
Re:Old C code – how to upgrade it? by all2 on Friday April 08, 2022 @03:35PM (#30961535)
This sounds like it could be a fun exercise all by itself (I'm a test engineer, and I enjoy testing :D )
[ Parent | on HN ]
Re:Old C code – how to upgrade it? by pflanze on Saturday April 09, 2022 @09:07PM (#30973597)
Yes, extending the test suite may definitely be worthwhile. Also, using AFL+ to collect non-crashing test cases can make this quick and somewhat exhaustive (while admittedly not giving as easy hints about what might be broken than manually created tests would).

Just in case you're interested in joining the sessions that I initiated, see https://news.ycombinator.com/item?id=30973570

[ Parent | on HN ]
Re:Old C code – how to upgrade it? by stazz1 on Saturday April 09, 2022 @12:10AM (#30965222)
This is the only way to ensure sanity is maintained through this arduous process.
[ Parent | on HN ]