comment on

I can't tell what you're advocating, if anything.

I've heard it said that you can't define something by what it isn't. (It's true that a chair isn't a table, but "a chair isn't a table" isn't a definition.) I mention this because what I've read seems to imply "there is a better way than what is commonly advocated", yet there doesn't seem to be any explanation of what the better way is.

I think that different people work differently. They come to different methods based on their personal strengths and personal experiences.

I'm interested in reading about your experiences and the methods those experiences have taught you to value. I'm not so much interested in the advocacy of a better way that isn't presented.

In reply to Re: Testing methodology, best practices and a pig in a hut. by kyle
in thread Testing methodology, best practices and a pig in a hut. by BrowserUk

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