What's the rationale behind the unit test structure for PromiseKit?

[mxcl]

What's the rationale behind the unit test structure for PromiseKit?

[mxcl]

I like not having to open Xcode (like obviously I am developing in Xcode, but usually it would mean having to open another Xcode window for the PromiseKit tests), so I made it so I can just run it in the Terminal. There are no disadvantages, but I also can run a sinatra web server that returns fixtures so I don't need to mock NSURLConnection and that’s very handy.

In many ways it was just experimentation, seeing what was possible. I've done it with several other projects too and each time it felt like I was gaining in ways I appreciate while not losing anything that mattered to me. I find the testing environment in Xcode unsatisfactory since it requires the iPhone simulator and also runs an entire application inside the simulator, with event loop and UIApplication. This way I have more control while also knowing for sure what is running, which when it comes to testing, seems important.

The only disadvantage is not getting the Xcode debugger when tests fail in ways you need to debug. I added a -d flag but the CLI LLDB is not as nice as Xcode.

[jessedc]

👍 Thanks for the clarification.