Closed Danielku15 closed 7 years ago
Thanks @Danielku15 for the investigation. You are 100% right. I think its funny you are the first person to hit this. The right long term solution is Chutzpah should know which file it is looking for and if it is a one needed to run only look in the right place instead of using the generic probing method I wrote.
That said, I did what you suggested as a temporary mitigation and just renamed the folders. I will include this in the next release.
I am running chutzpah on our CCNet CI using the console runner but I've also discovered this issue locally: If you run chutzpah.console.exe from a different working directory it will fail to run the tests since it cannot find the neccessary chutzpah dependencies.
First I thought it might be a general issue that it looks for the chutzpah_boot.js within the working directory. But the problem seems to be caused by the
TestFiles
folder. For my own test files i have aTestFiles
directory in my test project. It seems that this misleads chutzpah to think it needs to look for the chutzpah_boot.js in the working directory. I found the cause in the code: https://github.com/mmanela/chutzpah/blob/3a54a62f6218fd5e789781c4ad57693d6e657027/Chutzpah/FileProbe.cs#L223I think the exe path should overrule the working directory by default. Or at least the
BuiltInDependencyDirectory
should not only look for theTestFiles
folder, but also for some chutzpah specific file.TestFiles
is quite a general name that might exist in your test project.So a simple alternative could also be to rename
TestFiles
toChutzpahTestFiles
orTestRuntime
to remove this ambiguous naming.