comment on

I really like the CPAN smoke test efforts, automatically sending me feedback for platforms I'm not testing my releases on.

Only problem is that some things are meant to be broken, and I don't want to get email to tell me that they are. For example, some modules just don't work on Windows because of OS limitations. What am I as the CPAN author supposed to do about it?

If I mark the tests as "SKIPPED" on these platforms, the smoke tests will show up as PASS and module consumers might be tricked into thinking that it's OK to use the module on the broken platform.

On the other hand, if I don't do anything about it, I look somewhat foolish with my broken tests and keep getting emails from the smokers.

Is there a way to say "This is not supposed to be working, don't use it on this platform"?

In reply to CPAN Smoke Tests: Some platforms are meant to be broken by saintmike

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks