Every developer has an awesome project in mind. Such projects can take some time, depending on ambitions, skill, resources. Let’s consider someone planning to implement his own in 5 years, by working daily, assuming he will not use immediately the keyboard to avoid endless debugging. At this point, a first study over several months would save at least one or two years of refactoring, bringing the project to approximately 4 years. Then, it would be wise to choose a few abstractions, to increase productivity. In all cases, the time for learning and benchmarking those would be amortized during development.

First of all, to avoid confusion in the Ruby community, please note that: The code and the gem that I’m going to write about is not coming from rspec.info’s rspec, but from a personal project named r_spec-clone. My r_spec-clone project is totally independent from rspec.info, even if its interface is…

In the Ruby community, the two main testing frameworks offer different syntaxes to check the code: In RSpec, until recently, both expect and should syntaxes was available. For some technical reasons, however, the should syntax is not recommended. In minitest, expectations can be expressed through the Ruby or in an…

Short article to introduce Fix 0.7 features, and compare it with RSpec 3.3. How heavy is the package? On the one hand, the rspec gem (which is 7 LOC) runtime dependencies are: rspec-core: 6689 LOC rspec-expectations: 3697 LOC rspec-mocks: 3963 LOC rspec-support: 1509 LOC diff-lcs: 1264 LOC On the other hand, the fix gem (which…

After several drafts, we’re proud to announce the release of Fix! With 148 lines of simple code built on top of Spectus expectation library, facilities such as benchmarking and mocking are not supported. Fix offers however a consistent syntax to focus your BDD. While specs behave like documents which can…

We, programmers, are such artists. We program like painters paint, and there is nothing scientific here because no results can be proved. Thus, as long as the design is not satisfactory, or that in any case the specifications are not met, the work is not over. …

Tradition has it that, having a crowd of packets gathered in a dark network where a hundred specs would be performed inside an eerie atmosphere, the last matched one may yield an event… That’s when the NIDS demon — called Aoandon — was said to appear.