So, got pretty far in actually running tdvt, but eventually ran into the issue that probably drove the BIC to use these yaml files to begin with: you can't run tabquerytool without a license server. It looked like it might work because I could get help text from it, but once it actually goes to run queries it tells you you don't have a license :(
So the second approach was to generate a junit test using the same yaml files we use in the BIC. To that end, I'm using the same makefile in the resources directory that we use to generate the functions/functionsColumns tables. It calls two python scripts:
generate functions/functionColumns
generate the junit tests from the tdvt yaml files
The yaml files are also checked in, so if we feel the need to add more tests, it should be very easy. Definitely, the yaml format is much nicer than the generated java code!
So, got pretty far in actually running tdvt, but eventually ran into the issue that probably drove the BIC to use these yaml files to begin with: you can't run tabquerytool without a license server. It looked like it might work because I could get help text from it, but once it actually goes to run queries it tells you you don't have a license :(
So the second approach was to generate a junit test using the same yaml files we use in the BIC. To that end, I'm using the same makefile in the resources directory that we use to generate the functions/functionsColumns tables. It calls two python scripts:
The yaml files are also checked in, so if we feel the need to add more tests, it should be very easy. Definitely, the yaml format is much nicer than the generated java code!