Results 1 to 2 of 2

Thread: Testable and non-testable requirement.

  1. #1
    Junior Member
    Join Date
    Mar 2011

    Testable and non-testable requirement.

    I am preparing for a job interview. I can't think of any example about test and a non-testable requirement. please help me. Thanks.

    Give an example of a testable and a non-testable requirement. Using these examples, explain why requirements should be testable.

  2. #2
    Junior Member
    Join Date
    Jun 2011

    Re: Testable and non-testable requirement.


    Testable and non Testable requirements are defined based on the Testing Scope.

    For ex: Consider the Application "X" which have A,B,C modules which makes the Full application "X". All the requirements are mentioned in the Design documents.
    When Developers start working on the module A and the build A is availble for testing, then Module A is Testable and we can't test module B or C, so based on the development plan QA Analyst will prepare Test Strategy document and will give clear details on what requirements need to be tested and what should not.

    Hope it will help you.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.