Results 1 to 6 of 6

Thread: New Requriements

  1. #1
    Junior Member
    Join Date
    Sep 2010

    New Requriements


    When we get requirements on what techquines we need to write the test cases?

  2. #2
    Contributing Member
    Join Date
    Apr 2008

    Re: New Requriements

    Whenever a new requirement comes in either in form of new project or as a change request, as a tester we need to look into the requirement closely. We need to break the requirement in small-small module to make it simple to understand and easy to create test case on the same.

    Once you analysed and evaluated the requirement and have calculated the risk associated with that then you can decide which testing technique would best suited to your requirement. You can go for following testing

    Testing Types:
    1. Unit testing
    2. Integration Testing
    3. Regression Testing
    4. System testing
    5. Acceptence Testing.
    6. Performance Testing
    7. Load Testing
    8. Stress Testing
    9. Alpha Testing
    10. Beta testing

    Testing Techniques:
    1. Black Box Testing
    2. White box (or gray box) testing

    Testing Levels:
    Black box testing:
    1. Graph based testing
    2. Equivalence partiioning testing
    3. Boundry Value analysis testing.
    4. Comparision Testing
    5. Orthogonal Array testing.

  3. #3
    Contributing Member
    Join Date
    Sep 2010

    Re: New Requriements

    When you get a new requiremnt analyse it completly then if its a big requiremnt divide it small small modules based on functality level .then under each modules we can see so many sub usually if companies that are not using any tool for testcase creation then they will create folder for each modules and write testcases on doc or execel for that module and keep in that folder

  4. #4
    Contributing Member
    Join Date
    Nov 2007

    Re: New Requriements

    Once get the new requirements from the Business Analyst, Test Engineer go through the requirements and understand the requirements. If have any clarification regarding the Requirements we will clarify from BA. Then we prepare the high level test Scenarios and from scenarios we can retrieve/derive the Testcases.

  5. #5
    Junior Member
    Join Date
    Jul 2007

    Re: New Requriements

    Usually working on new requirements is BA work providing Functional specification doc since BA would be in touch with clients and they must be gathered all requirements.

    Anyhow sometimes in small organizations QA should do all the work and without BA contribution if we are getting requirements/without functional specification doc, it might be product. In this case, QA should understand the req first.

    But with single line req it can’t achieved. In that case, can follow below process

    1. Search in Google..
    2. Get more details from respective project/product sr team members/managers/BAs
    3. Clarify all your doubts
    4. Start writing high level test scenarios(HLS) and submit to lead/sr to get correct direction
    5. If HLS is confirmed, then start writing test cases by following std test case sheet

    Testcase techniques would be same whether new req/old. Use all black box testing techs (Functional; BVA, ECP, field validations, url validation checks, security checks, E2E and so on)


  6. #6

    Re: New Requriements

    Test Design Technique 1 - Fault Tree analysis

    Fault tree analysis is useful both in designing new products/services (test cases for new components) or in dealing with identified problems in existing products/services. Fault tree analysis (FTA) is a failure analysis in which the system is analyzed using boolean logic.

    Test Design Technique 2 - Boundary value analysis

    Boundary value analysis is a software testing design technique in which tests are designed to include representatives of boundary values. The test cases are developed around the boundary conditions. One common example for this technique can be, if a text box (named username) supports 10 characters, then we can write test cases which contain 0,1, 5, 10, >10 characters.

    Test Design Technique 3 - Equivalence partitioning

    Equivalence partitioning is a software design technique that divides the input data to a software unit into partition of data from which test cases can be derived.

  7.  Sponsored Ads


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.