Calabash
•Download as PPTX, PDF•
0 likes•353 views
Behaviour-Driven Development Style Testing
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Calabash
Similar to Calabash (20)
More from Panji Gautama
More from Panji Gautama (14)
Recently uploaded
Recently uploaded (20)
Calabash
- 1. BDD-TESTING
- 3. TDD BDD Test-Driven Development vs Behavior- Driven Development
- 4. Behavior-Driven Development • TDD done right • Business Readable, can be read almost like a sentence • Improves communication, monitoring and transparency *https://pragprog.com/book/hwcuc/the-cucumber-book
- 5. Calabash? • BDD-style acceptance testing • Ruby-based • Cross platform, supporting iOS & Android • Supported by Xamarin Test Cloud, TestObject, AWS Device Farm, etc
- 6. Cucumber • Natural Language • Can be understood by business experts and non-technical QA staff.
- 7. Calabash in Action Start calabash-android gen Basic calabash-android run <apkfile>.apk Verbose calabash-android run <apkfile>.apk -v Generate HTML Reports calabash-android run <apkfile>.apk --format html --out reports.html
- 9. Links • http://calaba.sh/ • https://github.com/calabash/calabash-android • https://github.com/calabash/calabash-android/blob/master/ruby- gem/lib/calabash-android/canned_steps.md • https://xamarin.com/test-cloud • http://agiledata.org/essays/tdd.html • https://github.com/jdavis/tdd-vs-bdd
Editor's Notes
- TDD – test driven development BDD – behavior driven development
- If we were to unpack the definition of TDD a bit more, we’d see that it is usually broken up into five different stages: First the developer writes some tests. The developer then runs those tests and (obviously) they fail because none of those features are actually implemented. Next the developer actually implements those tests in code. If the developer writes his code well, then the in next stage he will see his tests pass. The developer can then refactor his code, add comments, clean it up, as he wishes because the developer knows that if the new code breaks something, then the tests will alert him by failing.
- If we were to unpack the definition of TDD a bit more, we’d see that it is usually broken up into five different stages: First the developer writes some tests. The developer then runs those tests and (obviously) they fail because none of those features are actually implemented. Next the developer actually implements those tests in code. If the developer writes his code well, then the in next stage he will see his tests pass. The developer can then refactor his code, add comments, clean it up, as he wishes because the developer knows that if the new code breaks something, then the tests will alert him by failing.