I have been testing and trying to create a Proof of concept using TAZ. But it does not feel super user friendly to understand what is feasible of and what's the thought behind it. because the Test input and test Expected confuse when you have a program with a sub-program call. and if i have just a simple standalone db2 batch program for which both input and output is DB2 table, what does taz record? if i change something in the program, what would be compared? is it like a flow test instead of unit test? also if anyone knows how TAZ works like what data it captures and what fields are compared and how are IO mocked after a record for running it next time, please do explain.
------------------------------
Madhubalan Periyasamy
Devops engineer and System programmer
Freelancing
Stockholm
------------------------------