Error when running `test.dart`

[enricojr01]

Hi,

I'm getting an error when I try to run the test.dart tool - I run

> dart tool/bin/test.dart clox --interpreter ~/Projects/C/enrico-clox/cmake-build-debug/enrico_clox.exe

Passed: 0 Failed: 0 Skipped: 0 (.\test\assignment\associativity.lox)Unhandled exception:
Unknown test state for '.\test\assignment\associativity.lox'.
#0      Test.parse (file:///C:/Users/enricojr/Downloads/craftinginterpreters-master/craftinginterpreters-master/tool/bin/test.dart:224:7)
#1      _runTest (file:///C:/Users/enricojr/Downloads/craftinginterpreters-master/craftinginterpreters-master/tool/bin/test.dart:160:13)
#2      _runSuite (file:///C:/Users/enricojr/Downloads/craftinginterpreters-master/craftinginterpreters-master/tool/bin/test.dart:121:5)
#3      main (file:///C:/Users/enricojr/Downloads/craftinginterpreters-master/craftinginterpreters-master/tool/bin/test.dart:87:15)
#4      _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:281:32)
#5      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:184:12)

All I did was clone this repository, set up dart 2.12.0, and ran the above command. Can anyone lend a hand?

[dnabre]

I'm not sure on specific cause of the error, but I'm run into this when running the tests on Windows. So it most likely either a matter of a paths and/or line-end characters -- in the dart testing framework, not your implementation.

[seclerp]

Also struggling with this one on Windows, see #1003.

Patched my fork of craftinginterpreters with a fix from #1076.

[enricojr01]

https://github.com/enricojr01/enrico-jlox/blob/master/tool/bin/test.dart

It's been a while since I touched this, but it really was just line paths. I walked through the dart script and tweaked it until it worked. Unfortunately, I didn't catch that the "bin/" folder had been excluded by my .gitignore so it was never tracked, and don't have a history of the changes. I had to add -f the thing to get it into the repository.

[seclerp]

I ended up with my own test runner for my C# version of Lox. It only reuses the existing .lox test data. It's much easier to maintain and integrate into the .NET testing infrastructure. Unfortunately, the test suite infrastructure in this repo is not sufficiently technology-agnostic to be easily used by custom implementations.