Results 1 to 7 of 7

Thread: Difference b/w Test case and Test?

  1. #1
    Moderator
    Join Date
    Sep 2006
    Answers
    920

    Thumbs up Difference b/w Test case and Test?

    Explain:

    Difference b/w Test case and Test?

    Regards,
    Brijesh Jain
    ---------------------------------------------------------
    Connect with me on Skype: jainbrijesh
    Google Plus : jainbrijeshji

  2. #2
    Expert Member
    Join Date
    Oct 2005
    Answers
    383

    Re: Difference b/w Test case and Test?

    test is a general term for testing!
    There can b many test cases while you are testing.
    U have to think of all cases which can occur in program.
    for eg if a exception occurs how does prog handle it etc.
    so u should check with all possibilities!


    :)
    NEVER SAY DIE.

  3. #3
    Junior Member
    Join Date
    Oct 2006
    Answers
    1

    Re: Difference b/w Test case and Test?

    Quote Originally Posted by vmshenoy View Post
    test is a general term for testing!
    There can b many test cases while you are testing.
    U have to think of all cases which can occur in program.
    for eg if a exception occurs how does prog handle it etc.
    so u should check with all possibilities!
    You write test cases or test scripts to verify if the features will work according to the
    requirement. Test cases can be derived as a use case scenario or a combination of different
    requirments of that feature.


  4. #4
    Contributing Member
    Join Date
    Feb 2006
    Answers
    33

    Re: Difference b/w Test case and Test?

    Test case test case: is a document that describing input, action or event and expected response to determine whether feature of application working correctly or not. Developing test cases:
    • design test cases for unit test event based on objectives of test
    • should be specifications derived tests
    • should consider equivalence partitioning
    • state transitions testing
    • design test cases that include abnormal situations and data.
    • design test cases for all known and expected error conditions
    • design test cases to be easily duplicated
    • each test case must be described input and predicted result and conditions under which the test has been run.
    test case design test case id: it is unique number given to test case in order to be identified. Test description: the description of the test case you are going to test. Revision history: each test case has to have its revision history in order to know when and by whom it is created or modified. Function to be tested: the name of function to be tested. Environment: it tells in which environment you are testing. Test setup: anything you need to set up outside of your application for example printers, network and so on. Test execution: it is detailed description of every step of execution. Expected results: the description of what you expect the function to do. Actual results: pass / failed if pass - what actually happen when you run the test. If failed - put in description of what you've observed. test plan a software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the 'why' and 'how' of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. A test plan states what the items to be tested are, at what level they will be tested, what sequence they are to be tested in, how the test strategy will be applied to the testing of each item, and describes the test environment. A test plan should ideally be organisation wide, being applicable to all of organisations software developments. The objective of each test plan is to provide a plan for verification, by testing the software. The software produced fulfils the functional or design statements of the appropriate software specification. In the case of acceptance testing and system testing, this generally means the functional specification. What to consider for the test plan:
    1. test plan identifier
    2. references
    3. introduction
    4. test items
    5. software risk issues
    6. features to be tested
    7. features not to be tested
    8. approach
    9. item pass/fail criteria
    10. suspension criteria and resumption requirements
    11. test deliverables
    12. remaining test tasks
    13. environmental needs
    14. staffing and training needs
    15. responsibilities
    16. schedule
    17. planning risks and contingencies
    18. approvals
    19. glossary
    the test plan answers such questions as:
    • what is being tested?
    • what are pass/fail criteria?
    • when will each test occur?
    • what hardware and software environment is required?
    • what features must be tested?
    • what features will not be tested?
    • what are the responsibilities of individuals and organizations involved in the project?



  5. #5
    Junior Member
    Join Date
    Jun 2007
    Answers
    1

    Re: Difference b/w Test case and Test?

    Quote Originally Posted by jainbrijesh View Post
    Explain:

    Difference b/w Test case and Test?
    Hi,
    Testing: To verify whether the product we are building is right, which means the product we build meets the needs of specification.Testing is a series of process.

    Testcases: Testcase is a set of conditions or variables where in the tester will determine if the requirement is fullfilled or not. Testcases are generaly scripts which is used for testing an application.


  6. #6
    Moderator
    Join Date
    Sep 2006
    Answers
    920

    Re: Difference b/w Test case and Test?

    Quote Originally Posted by vmshenoy View Post
    test is a general term for testing!
    There can b many test cases while you are testing.
    U have to think of all cases which can occur in program.
    for eg if a exception occurs how does prog handle it etc.
    so u should check with all possibilities!
    Test has different meaning then testing.Test and testing are two different terms.

    Quote Originally Posted by minhn_007 View Post
    You write test cases or test scripts to verify if the features will work according to the
    requirement. Test cases can be derived as a use case scenario or a combination of different
    requirments of that feature.
    Quote Originally Posted by Pradeep7 View Post
    Hi,
    Testing: To verify whether the product we are building is right, which means the product we build meets the needs of specification.Testing is a series of process.

    Testcases: Testcase is a set of conditions or variables where in the tester will determine if the requirement is fullfilled or not. Testcases are generaly scripts which is used for testing an application.
    Again test and testing are two different terms.Please read question carefully before answering the question.

    Regards,
    Brijesh Jain
    ---------------------------------------------------------
    Connect with me on Skype: jainbrijesh
    Google Plus : jainbrijeshji

  7. #7
    Junior Member
    Join Date
    Oct 2008
    Answers
    2

    Re: Difference b/w Test case and Test?

    Testcase is a set of input values ,execution preconditions,expected results and execution postconditions,developed for a particular objective.
    Test : A set of one or more test cases.


  8.  Sponsored Ads
    Ad


     

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.
Interact