Missing test dll does not fail build
In this case I mistyped the path to the assembly containing my tests in appveyor.yml
I would have expected the build to fail as it could not run the tests but instead it just said it couldn't find the file and moved on successfully. Is this the expected behavior? Is there an option somewhere to fail build when a test dll can't be found?
Errors, Failures and Warnings
1) Invalid : C:\projects\upload-client\ClientUnitTests\bin\Release\ClientIntegrationTests.dll
File not found: C:\projects\upload-client\ClientUnitTests\bin\Release\ClientIntegrationTests.dll
Test Run Summary
Overall result: Failed
Test Count: 0, Passed: 0, Failed: 0, Warnings: 0, Inconclusive: 0, Skipped: 0
Start time: 2017-06-01 17:13:39Z
End time: 2017-06-01 17:13:40Z
Duration: 0.531 seconds
Results (nunit3) saved as TestResult.xml
...
Build success
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Ilya Finkelshte... on 02 Jun, 2017 09:34 PM
Sorry we do not have option and I do not see if we can safely add this in our current design. We do not always expect this to be specific path. This also can be just assembly name or wildcard mask (https://www.appveyor.com/docs/running-tests/#selecting-assemblies-a...). So this is other way around - we do recursive search for all given patterns (including specific paths and other not so specific things) inside build folder and run tests against what we found.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:17 AM.