Ah ok... That makes sense. I was thinking like generate a stream of data, data comes in some format like (string dataType, float dataValue) and a switch like case int{do this} case string {do that} then get new data and repeat while(true).

If it only was calculating based on the test case yeah that's bad.

I told this before but I had a project which had an xml configuration of many sections each targeting something different. I wanted each section as an object. This was a system of many combined systems like one dmm, one custom automated shield box, one bluetooth tester, etc. Each needed specific data to connect to it and configure it for the tests we wanted to run. This was all I needed in the xml file.

So I coded 1 function to read 1 section of the xml file and map it to an class object. I then copied that into Ai, copied configuration file into Ai, and told it to replicate it for each section. That worked. I think Ai can be used in specific circumstances where you are doing like repeated operations but it gets grossly overused. You also have to know the domain and the language to understand what it's doing.

Another example is I was asked to make a sql query which was basically a join(serial number and test guid in one table, test guid and test results in another table and only given serial number). My boss sent me a list of like 150 serial numbers separated by spaces over teams. I wrote the query for the first one and told the Ai to replicate it on the other serial numbers. Yes I could of gone through the list, backspace the space, add common, press enter and repeat. I knew how the query worked. I know the domain I was working in. The Ai output was basically the same as my original just with more serial numbers in the where clause.