We discovered that if the PLC_solution folder of BeckoffTestRunner has not recursively pulled the submodules (ie. tca_std_lib) the automation tools won't fall over, despite not generating a .tpy file. We should make the automation tools spit out an error if this occurs as everything looks fine. The old AutomationTools used to complain if it couldn't build the solution so we should make TwincatAutomationTools do the same.
Reproducible?
Yes
To Reproduce
clone beckhoff test runner and just use git submodule update --init without the recursive flag
try and run build.bat
notice that it doesn't break! and falls over silently, the ioc tests subsequently fail
Acceptance criteria
[ ] TwincatAutomationTools is made to spit out lots of errors if the code is actually broken and the solution fails to build
Where?
We discovered that if the PLC_solution folder of BeckoffTestRunner has not recursively pulled the submodules (ie. tca_std_lib) the automation tools won't fall over, despite not generating a .tpy file. We should make the automation tools spit out an error if this occurs as everything looks fine. The old
AutomationTools
used to complain if it couldn't build the solution so we should make TwincatAutomationTools do the same.Reproducible?
Yes
To Reproduce
clone beckhoff test runner and just use
git submodule update --init
without the recursive flag try and run build.bat notice that it doesn't break! and falls over silently, the ioc tests subsequently failAcceptance criteria