What about Fuchu tests?

[cnd]

No description provided.

[mausch]

What would you like to see concretely in a FAKE-Fuchu integration? Since Fuchu tests compile to .exe and are their own runner, nothing specific is really needed, just run the test executable.
I just added test running to the build script you contributed . It wasn't really worth the Async.Parallel for two assemblies with a few tests, but it would be useful for larger test assemblies.
Alternatively, if the Fuchu tests assembly uses the [<Tests>] attribute, you can use the testFromAssembly function to load the tests dynamically, then use run/runParallel to run them.

[cnd]

Well I used to have weird idea.... https://github.com/Heather/Failess/blob/master/build.fsx#L45

but there are two problems with it currently...

• If I get Fuchu in RestorePackages stage I don't know if I can dynamically add it...
• If I get my package in BuildSolution stage don't know if I can dynamically add it...

so if I can somehow deal with this two cases then I will just write tests in FAKE script, not sure if that could be good idea but that's what I was thinking about.

But in other side just running exe-s should be also fine =) Thank you for example of how to do it.

[mausch]

Yeah, I'd have a separate test project (just as you had before), otherwise as you see you can't take a dependency on an assembly that isn't available until the same script builds it (!)

Or you could put the tests in a separate script, then from the main build script invoke it with fsi.

Out of curiosity, what was your reason to move the tests to the script?

[cnd]

@mausch I just try / discover things around so I think that I will get it back now... Thanks for your attention.

[forki]

Have you considered to contribute the stuff in mausch/Fuchu@55d995f as a task in FAKE.Core?

[cnd]

By the way: Seq.map (fun p -> asyncShellExec { defaultParams with Program = p })

Could fail with on some fsharp / fsi configuration. Should not be problem with what FAKE use by default (+ with workaround provided on second link) but just saying...

• http://stackoverflow.com/questions/9378973/internal-f-error-with-f-3-0-in-visual-studio-11-developer-preview
• error FS0193 when using FAKE with a .NET 4.0 solution #20
• "error FS0193: internal error: Value cannot be null. Parameter name: con" #113

[mausch]

@Heather Not sure I understand but I don't see how those issues apply to this, since Fuchu tests are stand-alone .exes and run out-of-process so nothing in FAKE should affect them (nor viceversa).

@forki Good idea but not just yet; it needs more usage so that we can find what's really worth parameterizing.

[forki]

OK close for now