The Philosophy of Test-Driven Development : Unit Testing « Unit Test « Ruby

Ruby 1.  ActiveRecord 2.  Array 3.  CGI 4.  Class 5.  Collections 6.  Database 7.  Date 8.  Design Patterns 9.  Development 10.  File Directory 11.  GUI 12.  Hash 13.  Language Basics 14.  Method 15.  Network 16.  Number 17.  Rails 18.  Range 19.  Reflection 20.  Statement 21.  String 22.  Threads 23.  Time 24.  Tk 25.  Unit Test 26.  Windows Platform 27.  XML Java Java Tutorial Java Source Code / Java Documentation Java Open Source Jar File Download Java Articles Java Products Java by API C# / C Sharp C# / CSharp Tutorial ASP.Net JavaScript DHTML JavaScript Tutorial JavaScript Reference HTML / CSS HTML CSS Reference C / ANSI-C C Tutorial C++ C++ Tutorial PHP Python SQL Server / T-SQL SQL Server / T-SQL Tutorial Oracle PL / SQL Oracle PL/SQL Tutorial PostgreSQL SQL / MySQL MySQL Tutorial VB.Net VB.Net Tutorial Flash / Flex / ActionScript VBA / Excel / Access / Word Microsoft Office PowerPoint 2007 Tutorial Microsoft Office Excel 2007 Tutorial Microsoft Office Word 2007 Tutorial

Ruby » Unit Test » Unit Testing   The Philosophy of Test-Driven Development class String   def titleize     self.capitalize   end end puts "this is a test".titleize raise "Fail 1" unless "this is a test".titleize == "This Is A Test" raise "Fail 2" unless "another test 1234".titleize == "Another Test 1234" raise "Fail 3" unless "We're testing titleize".titleize == "We're Testing Titleize"   Related examples in the same category 1.  Unit Testing: assert_equal 2.  Writing Unit Tests 3.  Test case setup 4.  Unit Testing: hard code value 5.  Test the values in an array 6.  Assert exception raised 7.  Structuring Tests 8.  Varying the Algorithm with the Template Method 9.  A test case for collection class

www.java2java.com | Contact Us

Copyright 2010 - 2030 Java Source and Support. All rights reserved.

All other trademarks are property of their respective owners.