Move discover and execution to a remote process

Pilchie / xunit.runner.wpf

XUnit Gui written in WPF

Apache License 2.0

44 stars 41 forks source link

Move discover and execution to a remote process #19

Closed jaredpar closed 9 years ago

jaredpar commented 9 years ago

This moves the discover and execution actions into a remote process (communicating over named pipes). I've been able to multi-run several applications using this latest code.

There is still a lot of work to do here:

Discovery should be made non-blocking in the same way run is
Discovery should be cancellable
The named pipe strategy should be reviewed with someone more familiar with named pipes

Overall though this works and puts us closer to a state where we can begin using this.

closes #4

jaredpar commented 9 years ago

PR is updated so that discover is non-blocking as well now.

Pilchie commented 9 years ago

Would like to see filtered TestCases before merging, but otherwise generally fine.

jaredpar commented 9 years ago

New commit:

Responds to PR feedback
Includes support for running only the filtered test cases (contents of TestCases)

jaredpar commented 9 years ago

After responding to the feedback around resetting of state in the try / finally I realized discover and run had the exact same boiler plate code. Ended up refactoring it out to a single method which wraps the actual test operation in a delegate.

https://github.com/Pilchie/xunit.runner.wpf/pull/19/files#diff-436bcba0e5fb859825c2c38d51f080b6R337