melezhik

Recently keep playing with TDD and swat I have created a small web framework based on Kelp and swat.

The essential features of this framework named Spek are:

• it's a Kelp wrapper so most anything you could do with Kelp you do with Spek ( there some limitations though )

• it's a test centric framework - to implement route/controller you have to define swat test for it first, this is by design. Unless you have a test for your route, an application does not "see" this route. So tests here having a dual nature one for testing , and secondly to act like "placeholders" - for http endpoints definitions . It also could be called "embedded testing" in a sense that having tests meaning having routes definitions, so to start add new route/controller you necessarily need to create a test for it first.

• well, not all is that smoothly as it sounds (-; , I just took Spek for a spin and want to see what is going to be ...

• If such a theory sounds quite "obscure" for you, you may take a look at real example at Spek documentation.

The possible usages of Spek are:

• for web developers - quick web applications prototyping
• for application architects - quick specification as test development , when Spek application acts like prototype for real production system, and both Spek and production application confirms the same test suite comes with Spek