testing

Ollivander

One Assertion Per Test Considered Ambiguous

There's a practice of good programming which is often referred as One Assertion Per Test. In the opinion of some people, this practice would advocate the usage of a single call to xunit assert method for each test. I think that idea is plainly wrong. Saying "One

Ollivander

Unit testing with Twisted: testing protocols

I had some hard time when testing Twisted protocols. Although they should be decoupled from factories, most examples I could find, including those from the official doc, were just too noisy and suggested using a factory. I don't like that approach - I should not be forced to