Skip to content
trans edited this page Sep 13, 2010 · 1 revision

In practice QED and LDD prove an excellent means of API-based development. QED demos make an great way to quickly develop a new system. The demos provide a large swath of code coverage. Once implemented and stabilized, one can then write unit tests for more critical pieces of code as needed. It therefore help to solve the question of what should be tested in a natural way.

While capable of any level of testing, QED specifications tends to fall somewhere between unit testing (eg. Lemon) and full integration testing (eg. Cucumber). Where an integration test, a la Cucumber, are great for clients and and unit tests, a la Lemon, help ensure strong coverage, QED demonstrations are most useful to developers, who can read them and see exactly how an application or library is utilized via code.

Clone this wiki locally