I wish everyone would get out of the bad habit of referring to testers and test teams as 'QA'. Generally, we are doing testing. We might be doing quality control. Quality assurance is a whole different animal.
Evidently at some point, someone decided the words 'test team' or 'tester' don't sound important enough. I'm proud to be a tester (although ashamed of some in my profession, such as the team described in this post). I work on a team where everyone including the programmers shares responsibility for quality, testing and test automation. We're very happy with the results.
As for test teams needing to be 'independent', that's silly. A good tester provides information about the application. It doesn't matter who we report to. We aren't going to be somehow insidiously influenced to not find issues because we have a collaborative relationship with the programmers. More communication and collaboration would go a long way with most projects.
-
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.
|
