Changes between Version 2 and Version 3 of ConvertTestsToParrot
- Timestamp:
- 11/05/09 07:15:14 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ConvertTestsToParrot
v2 v3 80 80 Here is a brief list of some potential stumbling blocks and ways around them: 81 81 82 * There are a number of tests which confirm proper error reporting. This can be done in PIR in two ways. The simplest method is to create an exception handler and check the exception message. 82 * There are a number of tests which confirm proper error reporting. This can be done in PIR in three ways. The simplest way is to use dies_ok(), throws_like() or throws_substring(). 83 84 * You can also create an exception handler and check the exception message. 83 85 84 86 {{{ … … 110 112 }}} 111 113 112 Alternatively, you can create a EventHandler PMC and check for the appropriate error type. See t/pmc/ro.t for an example. This method may be preferable114 Finally, you can create a EventHandler PMC and check for the appropriate error type. See t/pmc/ro.t for an example. This method may be preferable 113 115 114 116 * Some tests create new classes and add methods to those namespaces. In a consolidated file you will need to make sure the new class names don't collide (you'll probably find a number of Foo and Bar classes), and you will need to make sure you return to the root namespace after the test completes.