comment on

++ g0n!

I am a Quality Assurance professional and I totally agree with you that testing is not about filling out defect reports but about finding bugs before they hit production. It is not only embarrassing to the development team but the QA team as well. That is why I like to create test cases from the very first draft of the specification. I think that QA should happen as the BA is writing the spec. Testing for logic as well as design before it even hits development would make unit testing a lot easier.

QA People at your place of work may be non-technical but I dont' think this is the norm. I QA by profession but I code in my personal time. I think this helps me to write better test cases because I think as a developer not as a "non-technical" QA person.

I have used Test::More to automate some tests before but I like manual testing. It allows me to get personal with the code and the application i'm testing. Automated testing is very impersonal and quick like a one-night stand :-). I like to get to know the application i'm testing even before I can see it.

Very nice meditation!

In reply to Re: The purpose of testing by mikasue
in thread The purpose of testing by g0n

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.


We don't bite newbies here... much
	PerlMonks