Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

I can't speak for the market, but if you wanted to work for me, I'd like to see:

  • A sound understanding of general QA principles and the whole development life cycle.
  • Good knowledge of QA techniques and when to apply them (e.g. Design for Testability, Mock Objects, Stubs, ...).
  • An understanding of the different possible types of testing: unit testing, white box testing, black box testing, system testing, acceptance testing, stress testing, documentation-driven testing, exploratory testing, beta testing, ...
  • A feel for what to test so as to get best value for money from testing (since there are an infinite number of things you could test).
  • Knowing when to automate a test.
  • Know how to ensure requirements are testable.
  • Experience writing test plans.
  • Experience with Test::More and associated CPAN modules.
  • Experience with Test::Harness, Devel::Cover and the prove command.
  • Knowledge/experience with tools, such as bug tracking, CM (e.g. Subversion), truss, valgrind, mech, HTML verification tools, lsof, ethereal, wikis, ...
  • Ability to write automated test harnesses for black box and system testing.
  • Ability to set up test labs.
  • Reasonable sysadmin and build engineering skills and domain knowledge.


In reply to Re: How can I use Perl knowledge in my Software Testing career by eyepopslikeamosquito
in thread How can I use Perl knowledge in my Software Testing career by pallav

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (3)
As of 2024-04-25 23:53 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found