Test script editing needs some updates to support coded tests

[johnpaliotta]

There are a few improvements needed - in the main branch

• [x] TEST.CODED_TEST_FILE should be added as a valid syntax in a .tst file (it should appear in the auto-complete list when you type in TEST., and not give an error when you type in)
  • What comes after the : will be a file path (this could be relative or absolute), but we do not want to do auto-completion on the filename (i.e., for TEST.CODED_TEST_FILE there is no autocomplete after :)
  • We probably need to make sure that coded tests are enabled in the environment/version of VectorCAST as well (they are not supported in 2023)
• [x] When the TEST.SUBPROGRAM is set to: coded_tests_driver
  • [x] TEST.CODED_TEST_FILE should be allowed (that is, it should not give error diagnostics)
  • [x] TEST.VALUE and TEST.EXPECTED lines should not be allowed (these should give error diagnostics)
  • [x] Look for "Command is only valid" inside of the Python to see what kind of errors we already return
• [x] When the TEST.SUBPROGRAM is not set to: coded_tests_driver
  • [x] TEST.CODED_TEST_FILE should not be allowed (i.e., it should now give an error diagnostic)
• [x] coded_tests_driver should not show up in the subprogram list for TEST.VALUE and TEST.EXPECTED lines
  • Normally when you type in TEST.VALUE:<unit>. you will get a list of all of the subprograms in <unit> -- DataAPI will tell you that coded_tests_driver is in <unit>, but we want to hide that from a user (the same for `TEST.EXPECTED)

Note:

• In file tstCompletions.ts, comment: // TBD will need to change how this is done during the fix for issue #170
  • The way I get the completion for TEST.SUBPROGRAM is a little bit of a hack and will need to change
  • Currently, I send a fake TEST.VALUE:unit. line to get the list of subprograms
  • But currently, the Python strips coded_tests_driver in function: getFunctionList()
• Need to check if coded_tests_driver should be allowed in TEST.SLOT lines
  • Does vcast support compounds with coded tests?
  • @Den1552 won't address this until Andrew is back
• Look for all other uses of getFunctionList()
  • getFunctionList() is the "core" of the interaction between VS Code and VectorCAST, and is probably the place where coded_test_driver should be filtered, but not for TEST.SUBPROGRAM

[johnpaliotta]

@aytey The first two items should be easy, the third one might be a little tricky, so let me know if Denis needs help

[aytey]

Note: @johnpaliotta is going to remove coded_tests_driver from TEST.VALUE, TEST.EXPECTED and TEST.SUBPROGRAM (which will then allow the current tests to pass when coded mocks are turned on).

When we come to solve this case, we need to re-enable coded_tests_driver being a valid option for TEST.SUBPROGRAM.

[aytey]

Note: @johnpaliotta is going to remove coded_tests_driver from TEST.VALUE, TEST.EXPECTED and TEST.SUBPROGRAM (which will then allow the current tests to pass when coded mocks are turned on).

When we come to solve this case, we need to re-enable coded_tests_driver being a valid option for TEST.SUBPROGRAM.

@Den1552 this was done in this commit: https://github.com/vectorgrp/vector-vscode-vcast/pull/105/commits/da8f133a92951280dd3f06083179e5ee587d3836