Changes between Version 1 and Version 2 of ConvertTestsToParrot
- Timestamp:
- 12/03/08 21:06:13 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ConvertTestsToParrot
v1 v2 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 two ways. The simplest method is to create an exception handler and check the exception message. 83 83 84 84 {{{ … … 92 92 }}} 93 93 94 > becomes... 95 94 becomes... 96 95 97 96 {{{ … … 111 110 }}} 112 111 113 >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 preferable112 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 preferable 114 113 115 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. 114 * 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. 117 115 118 116 {{{ … … 120 118 }}} 121 119 122 * Many tests are skipped based on the operating system. You can test for this in PIR with the following:120 * Many tests are skipped based on the operating system. You can test for this in PIR with the following: 123 121 124 122 {{{
