• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Unit Testing & Test Driven Development
 

Unit Testing & Test Driven Development

on

  • 2,879 views

A presentation of mine at universtiy...

A presentation of mine at universtiy...

Statistics

Views

Total Views
2,879
Views on SlideShare
2,871
Embed Views
8

Actions

Likes
3
Downloads
86
Comments
0

3 Embeds 8

http://www.linkedin.com 5
https://www.linkedin.com 2
http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Unit Testing & Test Driven Development Unit Testing & Test Driven Development Presentation Transcript

    • by Ersan BİLİK
    • unit : smallest testable part of  an application an individual program   a function  a procedure  a method..  depends on your viewpoint !
    • test: a means of determining the presence, quality or  truth of something determining “the unit” works as it is promised to?   determining the quality of “the unit” ?  determining the truth about “the unit” ?
    • Unit Testing : a procedure used to validate that  individual units of source code are working properly. unit testing itself, is a procedure  unit testing applies to individual units  unit tests build-on to source code   to ensure source code is working properly
    • Unit testing is a white  box approach in testing activity usually, it is  integrated with implementation phase but also, it depends on your software development life cycle..
    • PROS CONS isolation of units go to definition: it   refactoring code applies to individual  units, therefore it can simplifies integration  not guaranty the overall documentation  system will work ! seperation of interface  from implementation it only shows the  presence of errors, not a good habit: motivator  for decoupled, cohesive absence of errors.. code bodies, refactored with design patterns..
    • Manually..  step by step instructional document..  Automated tools  frameworks are available..  usually called xUnit frameworks.. 
    • we will investigate test driven development  methodology with nUnit framework based on Microsoft .NET
    • an approach for software development  actually, itself is not a lifecycle model, but an  approach for implementation phase for agile software lifecycles.. it is a bottom-up approach..  think: write tests first, then code necessary  instructions to pass your tests..
    • yes, first write a test case.  then build it.. it will fail because no code  written to pass the test implement your code as long as test case is  passed.. and voila..! YAGNI : you aint gonna need it. So,  you code as much as you need.. then think about it, how to do it better ? 
    • is the code satisfies my requirements ?  lets assume requirements sais: if a customer  wants to transfer money, minimum balance for the customer should be 10.00$ so, lets continue.. 
    • mock objects and their usage in unit testing.. 
    • Check out Behaviour  Driven Development Watch video of Dave  Astels ( co-author of “A  practical guide to eXtreme Programming” and author of award winning test-driven development: a practical guide)
    • any questions or comments ? 