846 karma · joined May 15, 2010
http://byterot.blogspot.co.uk/2015/09/rule-of-most-accessibl...
Part of the information contained in a test is the intent of the verification being performed, and part is code for mapping that intent onto the implementation. The latter part can be discarded during a rewrite. Cucumber/SpecFlow etc. make the difference between these explicit.
1. Don't write fast running behavioural tests that verify the software is working as required.
With fast running tests I can maintain any old crap. Well, technically speaking I can rewrite it, but no-one will mind.
Then again, I live in London. Maybe they all telecommute to here.
I did so, and submitted it. They then emailed me back I had been rejected without any feedback at all, and didn't send me any when I asked for some.
Abstracting away web development and http has been tried again and again, and always ends up being more hassle than plain ol' HTML+JS+HTTP.
Then you've limited yourself to interop with the js libraries they've provided leaky wrappers over, or you can write your own leaky wrapper if you want to use coolnewthing.js you saw on github.
And to cap it all, this framework requires commercial licensing for closed source projects!
Actual LINQ is a lot more powerful.