On 3/5/07, Ovid <[EMAIL PROTECTED]> wrote:
Good point. How about, if an .rc file is used, the output of runtests is something like: shared_cp $ runtests -lrq Using .rc file: /home/ovid/.runtestsrc t/cp_demo_lib.....................ok t/cp_lib..........................ok t/db_connection...................ok t/dh_password.....................ok t/dh_server.......................ok ... Thoughts?
I'm a testing newbie, and I apologize if this has been beaten to a pulp in the past. I'd try to use something like YAML for as much of the output as practical, especially the configuration information or warnings. Perl is great at parsing, but why make it difficult. Especially for the person I'll worship who'll write the Eclipse TAP plugin. Hey, we all have our vices, I like Eclipse. :) So I'd do something like. rc_file: /home/ovid/.runtestsrc Peace, -- Eric Hacker, CISSP aptronym (AP-troh-NIM) noun A name that is especially suited to the profession of its owner I _can_ leave well enough alone, but my criteria for well enough is pretty darn high.
