> You did not write code to terminate or provide an answer for all inputs... Definitely not an expert. But to my eyes checking for non-termination seems very c

> You did not write code to terminate or provide an answer for all inputs... Definitely not an expert. But to my eyes checking for non-termination seems very close to things that happen in SQL all the time. For example, a parent query joins two subqueries that both map data, and then maps on that data. To test, I could just test one specific scenario with specific values in all columns. That would be more of a concrete test case. But I might want something more robust checking the outer bounds of acceptable data (like a min and a max). That seems much closer to the non-termination test. Of course, I'm open to being corrected on this.