1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
ripperX plugin tester v0.1
This document describes what ripperX_plugin_tester is and how to use it.
1. ripperX_plugin_tester?
ripperX_plugin_tester is a program with which one can test if a plugin he/she
wrote works fine. It is essentially made from the code segments from ripperX
which handles execution of ripper/encoder/plugin and the parsing of output
from plugin. So if a plugin looks fine when tested with ripperX_plugin_tester,
it should work with ripperX.
2. How do I use it?
The syntax is
$ ripperX_plugin_tester "ripper/encoder command" "plugin command"
for example, to test cdparanoia plugin.
$ ripperX_plugin_tester "cdparanoia 4" "ripperX_plugin-cdparanoia 31987 4215
After executing ripperX_plugin_tester like above, if everything goes ok,
you'll see output like this
***Executing "cdparanoia 4"
with plugin "./ripperX_plugin-cdparanoia 31987 4215"
*** No report available from plugin. Ctrl-C to stop
*** PLUGIN_MSG_PARSE_ERR returned
*** No report available from plugin. Ctrl-C to stop
*** PLUGIN_MSG_PARSE_ERR returned
*** No report available from plugin. Ctrl-C to stop
*** PLUGIN_MSG_PARSE_ERR returned
*** No report available from plugin. Ctrl-C to stop
*** PLUGIN_MSG_PARSE_ERR returned
*** No report available from plugin. Ctrl-C to stop
*** PLUGIN_MSG_PARSE_ERR returned
*** Output read from plugin : [P 0.055991 "--> "]
Report type : progress, Progress : 0.055991,
Msg : -->
*** Output read from plugin : [P 0.092527 "-+-> "]
Report type : progress, Progress : 0.092527,
Msg : -+->
If something goes wrong, it will print out error msgs. The error msgs are
quite easy. I think you can figure what's wrong when an error msg appears.
==============================================================================
ripperX_plugin_tester v0.1
TeJun, Huh
wineking@adam.kaist.ac.kr
|
