I have some tests in modules that require user input. I put them in a test.pl file so that tests won't fail with auto build processes (like that of Activestate's PPM) but also allow the user to supply information if they want to run the full test suite.

Have a look at the test.pl script in the Cisco::Management module for example. The test.pl script asks for a router IP address and SNMP community strings to run the full set of tests. Pressing just enter skips the suite entirely. That may be a way to go - put your regular tests in a file and the ones that require authentication - put them in a test file that prompts the user for input (their own credentials) or allows them to skip the tests.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.