Skip to Content
Dev – Test Relation ship   “testing is simply a non-deterministic task the outcome of which is somewhat unpredictable.’ this is how Micheal hunter – describes in one of his posts. Dev – Test relationship has always been my fav topic. I am fortunate enough all these years to work with those ‘understanding” developers who thinks that dev and test compliment each other. As I hear stories about dev feeling testers are “necessary evils”, I feel that most of this due to historical reasons or due to the way some organizations look at testers. Without enough training, career paths – people are pushed to do testing – that is why we have lots of people called testers who made to this title because that failed in other area – mainly development. Micheal further says in his post about true dev test relationship that is based mutual trust and respect  “Every relationship is founded on trust – or the lack thereof – and this one is no different. Remember that you’re not just fighting stereotypes about testers (“Testers can’t code.” “How hard can it be to find bugs?”) but also about developers (“Developers write bugs into their code just to make my life miserable!” “How hard can it be to write bug-free software?”) ”  A collaborative dev test relation is sign of a good project team …
To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. I was a member of an SQA team before I joined the
    development. I was already developing apps and
    had been programming alot but I did choose testing
    team when I joined SAP despite having a choice of
    joining the development. Why? because it is a
    field that is not taught in school.

    >Without enough training, career paths – people
    >are pushed to do testing – that is why we have
    >lots of people called testers who made to this
    >title because that failed in other area – mainly
    >development.
    I totally disagree.
    Tester is not just a position created just for
    those who failed in the development. there is a
    testing field much more wider than development;
    only that it is commonly not a part of a school’s
    curriculum.

    testing is more difficult than development task;
    testing skills require time to be developed and
    sometimes require deeper skills if you are
    really to break a software. implementing a
    feature is very easy when you already have a
    design and validating it with the specs could
    only be thru the result without consideration for
    other factor like performance and algorithm.

    testing involves mainly the following
    – planning
    -> defining scope and strategies that suits
    best in evaluating the subject software
    – testcase design
    -> designing a testcase according to strategies
    and scope
    – testcase development
    -> development of testcases: manual steps or
    automated according to the design
    – testcase execution
    -> execution of testcases
    – analysis & reporting
    -> analyzing the result and reporting to the
    responsible person.
    -> involves persuading the developer why it is
    a bug and should be fixed
    – programming/configuration
    -> sometimes involves creating the prototype and
    knowing the system configuration

    these tasks require knowledge on the subject
    system/software and employed technologies as well.
    it actually requires more skills than a developer
    does. i was really very lucky that i joined
    testing prior to development. i was already aware
    of the common mistakes the developers do and i was
    able to avoid them in my development tasks then…
    and does know how to test my work as well.

    just my 2 cents.
    jo

    (0) 

Leave a Reply