waldo1001
commented
2 years ago I don't see reference for the assert in your app.json .. .
can you add this:
"test": "14.0.0.0"Closed JohnnyUndercover closed 2 years ago
waldo1001
commented
2 years ago I don't see reference for the assert in your app.json .. .
can you add this:
"test": "14.0.0.0"
JohnnyUndercover
commented
2 years ago Thanks, that fixed it!
I didn't think about that something was missing in the app.json because it worked in vs code..
Just in case someone is having the same problems: After adding "test": "14.0.0.0" to the app.json, i also needed to change "import_testtoolkit" to "true", because without i got the follwing error:
[error]Run-Test-Exception: Cannot open page 130409. You might need to import the test toolkit to the container and/or remove the folder and retry. You might also have URL or Company name wrong.
The changed task in the pipline
- task: ALOpsAppTest@1
displayName: 'ALOPS - Run TestSuite'
inputs:
usedocker: true
import_action: "Skip"
show_available_tests: true
import_testtoolkit: true
failed_test_action: 'Ignore'
continueOnError: true
Describe the bug I have an app with a test app for BC14 without C/Side customizations. When I try to compile the test app, I get errors that the symbols for the test objects are missing.
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior In the ALOpsDockerCreate step I set includetesttoolkit to true, so I expected the test toolkit symbols to be present.
I am not sure if this is a bug or my assumption that the includetesttoolkit parameter is the same as the parameter in bccontainerhelper is wrong.
Screenshots
Additional context If I manually add the testtoolkit before compiling the test app, everything works as expected. But then it takes a few minutes to import the toolkit on each run and not just once when the image is created.