TDD & Unit Testing

Transcript

1. Test Driven Design (TDD) & Unit Testing Serdar Büyüktemiz github.com/serdarb
2. What is Software Testing? • Software testing is a process used to identify the correctness and quality of developed computer software. • It includes a set of activities to find errors in software so that it could be corrected before product is released.
3. Cost of a Bug It is all about the money!
4. Industry is now passing the early majority stage! Software Development & Adaption Lifecycle • http://en.wikipedia.org/wiki/Technology_adoption_lifecycle
5. What does this mean? • This means in the past having a working software was cool, but today everyone has a working software! • The hard thing today is having a cheap maintainable code... which can be achievable only via automated processes.
6. The History of Software Testing • IEEE 829 Standard for Software Test Documentation is published in 1983. • Today’s modern testing frameworks are clones of SUnit which develped by Kent Beck who is also the creator of extreme programming.
7. This book contains a chapter on software testing at 1966!
8. Some Testing Types You May Heard • Black box testing • White box testing • Unit testing • Incremental integration testing • Integration testing • Functional testing • System testing • End-to-end testing • Sanity testing • Regression testing • Acceptance testing • Load testing • Stress testing • Performance testing • Usability testing • Install/uninstall testing • Recovery testing • Security testing • Compatibility testing • Comparison testing • Alpha testing • Beta testing • Exploratory Testing
9. What is Unit Testing? • Unit testing is a software development process. • Units are the smallest testable parts of an application. • Units independently test a proper operation.
10. Why Unit Testing Is Important? • A testable code is manitainable code. • When you code the unit tests you can automate the software testing. • It dramaticly improves the quality.
11. Unit Testing Advices • It should be easy to implement. • It should be automated, should be easy to repeat. • Anyone should be able to run it with a single click. • It should be isolated. (a unit test can not be effected from other tests, it should be independent…) • When it fails, failing reason should be obvious. • It should run quick.
12. What do you mean with TDD? • I mean Test Driven Design. • In TDD, Test is the first thing you do to design the software architecture!
13. The technique of TDD 1.Write a failing test for a function (Red) 2.Make the test pass (Green) 3.Refactor your code (Refactor)
14. Some Tools for Testing in .Net • Nunit • FakeItEasy • Selenium • SpecFlow • Ncrunch • Resharper • dotCover
15. TDD DEMO An enterprise application design
16. UNIT TESTING DEMO A basic money amount multiply method A test driven designed fibonacci squence method
17. Books to Read • http://www.amazon.com/Test-Driven- Development-By-Example/dp/0321146530 • http://www.amazon.com/The-Art-Unit- Testing-examples/dp/1617290890
18. References • http://en.wikipedia.org/wiki/Portal:Software_testing • http://www.softwaretestinghelp.com/types-of- software-testing/ • http://artofunittesting.com/ • http://martinfowler.com/tags/testing.html • https://www.youtube.com/watch?v=z9quxZsLcfo