This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
example_driven_development [2014/03/17 16:40] Joel Dare |
example_driven_development [2020/06/01 22:53] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Example Driven Development ====== | ||
| + | //TODO// | ||
| + | |||
| + | Test Driven Development (TDD) is all the rage these days. I personally find it difficult to write tests. I feel like no matter how much time I spend on them, my tests are never complete. I feel like not everything I want to test can be tested. I feel like I'm wasting time writing tests. | ||
| + | |||
| + | What about Example Driven Development (EDD)? Specifically for API's. Instead of writing a test, using some testing framework that I don't understand, I simply write an example of how to use the API. It's essentially a test, but it doesn't use some proprietary testing framework. It's simply an example that calls the API and gets the responses. | ||
| + | |||
| + | I guess it stops short of being a test because it doesn't test the result of the call (although it easily could). | ||