Answered Questions

  • Automated Testing

    When should you use an automated testing?

    Star Read Best Answer

    Editorial / Best Answer

    kurtz182  

    • Member Since Nov-2009 | Dec 19th, 2009


    Automated testing is best performed:


    1) When a product has enough value to a company to warrant it

    2) When a product has a long enough life cycle to warrant it

    3) When it directly helps your project's speed, coverage, risk mitigation and development nimbleness

    4) When it is relatively simple to implement

    5) When requirements are stable and not apt to change

    6) On components that are mission-critical

    7) On components that have failed and are apt to fail again

    8) On components that are self-contained

    9) On components that are scriptable

    10) On components that require little maintenance

    mail2vass

    • Jan 12th, 2011

    When the test case are testing regularly and the occurance of this test scenario is frequently using based on this the test manager will go for the automating this test... and based on resources also we will prefer automation testing.

    viplav15

    • Jan 10th, 2011

    Automation Testing can be initated and planned in two scenarios.One for the Agile development mode.Other for the Stabilised Modules just for the Regression activity to be performed as and when the nee...

  • what is the difference bw water fall model, prototype model,spiral modal.

    Anjali Gaikwad

    • Aug 7th, 2015

    Waterfall model is step by step process
    Spiral Model is Iterative Process
    Prototype Model is certainly changing Process

    Kundan Kotangale

    • Feb 7th, 2015

    Waterfall model:- 1. It is a linear sequential life cycle model it is also called classical model. it is proposed by Royce so that it is called as Royce model 2. when the requirement of the customer ...

  • Describe to me the difference between validation and verification.

    Answer posted by Radhika on 2005-05-24 08:29:43: Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements and specifications. Validation evaluates the product itself. The input of verification are checklists, issue lists, walkthroughs and inspection meetings, reviews and meetings. The input of validation is the actual testing of an...

    mail2vass

    • Jan 17th, 2011

    Verification:it is a process of verifying are we developing the right system or not that means , checking the srs , brs documents. and verification does not involve in code execution.Validation:it involves in code execution, and it is followed  by unit, integ, and system testing

    kurtz182

    • Dec 29th, 2009

    Here are some easy ways to remember the difference between verification and validation:First you verify what a customer wants, then you validate whether or not you have delivered it.  Verificatio...