Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
user:zeman:interset:how-to-write-a-driver [2007/10/01 15:37] zeman Replacing arrays. |
user:zeman:interset:how-to-write-a-driver [2007/10/01 17:38] zeman |
||
---|---|---|---|
Line 124: | Line 124: | ||
See [[user: | See [[user: | ||
+ | |||
===== Test your driver ===== | ===== Test your driver ===== | ||
- | When you have written a driver for a new tagset, you should test it. An Interset service module | + | When you have written a driver for a new tagset, you should test it. The driver package contains a test script called '' |
+ | |||
+ | < | ||
+ | driver-test.pl ar::conll | ||
+ | </ | ||
+ | |||
+ | Note that only drivers implementing the '' | ||
+ | |||
+ | The following tests will be performed: | ||
- | * Get list of possible tags by calling list(). Go through the list and check for each tag that encode(decode($tag))=$tag. While sometimes it can be annoying to try to preserve some obscure information hidden in the tags, this test can also reveal many unwanted bugs. Besides, you should preserve information of your own tagset because people may want to use your driver merely to //access// the tags, instead of // | + | * Get list of possible tags by calling |
- | To perform the test, run the script '' |