An Example-Driven API Tester
4 likes642 views
The document discusses using examples instead of assertions to test APIs. It proposes testing APIs by comparing the output to example outputs in the documentation rather than writing assertions. This avoids writing many assertions for complex JSON outputs and makes tests easier to update when examples change compared to changing assertions. However, example-based tests do not print failures on Jenkins. The document also explores using tree pattern matching as another approach for API testing.
An Example-Driven API Tester
- 1. Lorem Ipsum Dolor A Example-Driven API Tester Allen Lin! 2014.9.11
- 2. Unit Test on API ❖ JSON format! ❖ We use to write NSAssert! ❖ If the struct of JSON output is complex…! ❖ Takes time to write! ❖ Hard to check error
- 4. Better Unit Test by Example ❖ What if there’s a example…! Server API document output example ❖ The document should have example diff Unit Test
- 8. Restrict ❖ Objects struct in an array must be the same! ❖ Not exactly matching
- 9. Summary ❖ Pros:! ❖ Do not need to write NSAssert! ❖ Easy to change example than NSAssert! ❖ Cons:! ❖ Do not print on Jenskins
- 10. Another Approach? ❖ Tree Pattern Matching! ❖ Recursive vs. Pattern Abstract