This winter holiday season, give a precious gift to your career by upgrading your skills. | Get Flat 15 - 20% OFF on All Courses | Save Today

[iqquestion id=82]

9 thoughts on “Manual Testing : Test Cases Discussion 3

  • karim

    Identification of specific Requirement to be tested.
    Test case success / failure criteria.
    Specific steps to execute the test.
    test data.

  • Olubunmi Ogunsola

    Unique title of the test case, the description of the requirement, steps performed for the test case, expected outcome, actual outcome

    – Tomiwa

  • collins

    various fields in a test case are test id(which represents the test number, detailed steps(which is info about what you are going to do) pass/fail( if the test failed or pass)

  • Jomon Elengical

    Test case ID: is the unique identity of test case
    Test case summary: it is summary/ objective of test case
    Prerequisites or preconditions: preconditions that must be fulfilled prior to the test case
    Test steps: details of steps in test case
    Test data: data those are used to process the test
    Expected result: expected result per requirement
    Actual result: result generated after execution of test
    Status: pass, fail or not executed
    Remarks:(if required)

    – jyothi

  • Pamela halbhavi

    Test Suite ID: ID of test case suit(which is a group of test cases), if required
    Test Case ID: Unique identifier of the TC
    Test Case Summary: Objective of the TC
    Prerequisites or preconditions: condition that must be satisfied before the test case is executed
    Test steps: Steps that will be executed in the order listed
    Test data: Data that is used to conduct the test
    Expected result: expected behavior predicted by the requirement specs under the specified conditions
    Actual result: The behavior produced/observed/generated by the system after execution of the test.
    Status:Pass / fail / not executed depending on the case.
    Remarks: additional comments(optional)

  • krishna shrestha

    test case has following fields .
    1) test ID : it is test numbers.
    2) test name : it is the test name . what you are writing ?
    3) description : it means, what are you going to do on testing period ?
    4) detail steps : it means, how are you doing testing , write here in, step to step.
    5) expected result : when you are testing . what you think about result . we can write here.
    6) actual result . after testing, what happened you see ? . we write here about that .

  • Banksy

    1)Test Suite ID: typically the test unit
    2)Test Case ID:typically the test Number
    3)Test Summary:The objective of what is being tested
    4)PreRequisites: conditions that must take place prior to the test
    5)Test Steps: Steps for testing
    6)Test data: test data used while conducting the test
    7)Expected Results
    8)Actual Results
    9)Status: Pass or Fail
    10)Remarks

  • Solomon Ayanaw Habtu

    1. ID: to identify from other test cases and to create relation between test cases easly
    2. Test Name: short and concrete test case title
    3. Description: precise explanation of the test objective
    4. Prerequisites : preconditions to be fulfilled to run the test case
    5. Test Steps: numbered sequences to be executed to fulfill the described objective
    6. Test data: if necessary for the test steps as input
    7. Expected result: the result we expect from the execution
    8. Actual result: the real result of test step execution
    9. Status: Pass/fail for the goal based on actual and expected result
    10: Remarks:

  • Solomon Ayanaw Habtu

    ID: the unique identifier for the test case among other test cases
    Description: short explanation to show the objective of the test case

    Steps: serous of steps to be run to get the result of the test

    Prerequisite: Requirements to be fulfilled before executing each steps.

    Data: data if necessary for the test

    Expected result: it is what is expected after executing the test steps, based on the requirement specification

    Actual result: the real result the system gives at the end of step execution

    Status: pass or fail mark for the system. By comparing the expected and actual result.

Leave a Reply