CSC/ECE 517 Fall 2010/ch1 1f vn: Difference between revisions
| Line 15: | Line 15: | ||
==Assertions== | ==Assertions== | ||
The core part of test::unit framework is the ability to assert a statement of expected outcome. If an assert statement is correct then the test will proceed, otherwise the test will fail. Test::unit provides a bunch of assert methods for this purpose. | The core part of test::unit framework is the ability to assert a statement of expected outcome. If an assert statement is correct then the test will proceed, otherwise the test will fail. Test::unit provides a bunch of assert methods for this purpose. | ||
| border=1 cellspacing=0 cellpadding=5 | {| border=1 cellspacing=0 cellpadding=5 | ||
| assert( boolean, [message] ) | | assert( boolean, [message] ) | ||
| True if ''boolean'' | | True if ''boolean'' | ||
| Line 21: | Line 21: | ||
| assert_equal( expected, actual, [message] )<br>assert_not_equal( expected, actual, [message] ) | | assert_equal( expected, actual, [message] )<br>assert_not_equal( expected, actual, [message] ) | ||
| True if ''expected == actual'' | | True if ''expected == actual'' | ||
|- | |- | ||
| assert_raise( Exception,... ) {block}<br>assert_nothing_raised( Exception,...) {block} | | assert_raise( Exception,... ) {block}<br>assert_nothing_raised( Exception,...) {block} | ||
| True if the block raises (or doesn't) one of the listed exceptions. | | True if the block raises (or doesn't) one of the listed exceptions. | ||
|- | |- | ||
|} | |} | ||
For the full list of assertion methods provided by test::unit refer to [http://ruby-doc.org/stdlib/libdoc/test/unit/rdoc/classes/Test/Unit/Assertions.html test::unit assertions] | For the full list of assertion methods provided by test::unit refer to [http://ruby-doc.org/stdlib/libdoc/test/unit/rdoc/classes/Test/Unit/Assertions.html test::unit assertions] | ||
Revision as of 21:03, 6 September 2010
Introduction
Unit testing is a method by which we can isolate and test a unit functionality of the program, typically individual methods during and long after the code is written. Unit testing frameworks provides us with constructs and methodologies which simplifies the process of unit testing. This chapter walks through three different unit testing frameworks available for Ruby, explains how to use them with examples, and compares them with one another. The three commonly used unit testing frameworks for ruby are
- Test::Unit
- Shoulda
- RSpec
Test::Unit
Ruby comes with an in-built, ready to use unit testing framework called Test::Unit. It is a XUnit type framework and typically have a setup method for initialization, a teardown method for cleanup and the actual test methods itself. The tests themselves are bundled separately from the code it is testing.
Test Fixture
Test fixture represents the initial environment setup(eg. initialization data) and the expected outcome of the tests for that environment. This is typically done in the setup()/teardown() methods and it helps to separate test initialization/cleanup from the actual tests. It also helps to reuse the same fixture for more than one tests.
Assertions
The core part of test::unit framework is the ability to assert a statement of expected outcome. If an assert statement is correct then the test will proceed, otherwise the test will fail. Test::unit provides a bunch of assert methods for this purpose.
| assert( boolean, [message] ) | True if boolean |
| assert_equal( expected, actual, [message] ) assert_not_equal( expected, actual, [message] ) |
True if expected == actual |
| assert_raise( Exception,... ) {block} assert_nothing_raised( Exception,...) {block} |
True if the block raises (or doesn't) one of the listed exceptions. |
For the full list of assertion methods provided by test::unit refer to test::unit assertions
Example
The test methods should start with 'test' prefix. This helps in isolating the test methods from the helper methods.