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=85]

8 thoughts on “Manual Testing : Test Cases Discussion 6

  • Olubunmi Ogunsola

    Keeping it small, clear, and readable for others, testing for positive and negative scenarios, not overdoing steps.

    It needs a test suite and case ID, test steps, summary, expected and actual outcomes, and status

    -Tomiwa

  • collins

    The guidelines for a good test case is providing just enough information, comes with the basics so you can identify each column and tells you weather the software pass or failed

  • Jomon Elengical

    -Test case should identify requirement and should be traceable to requirement.
    -It should cover all functionality mentioned in requirement.
    -High priority test cases should be executed first
    – Should be simple and easy to understand.
    – should be grouped properly (eg: module wise)
    – Avoid repetition of test cases
    – test case should be written with end user in mind

    – jyothi

  • Pamela halbhavi

    Test Cases
    should be traceable to the requirement.
    should cover all the features in the requirements document.
    should be simple and clear.
    avoid repeating the test cases.
    should be reusable.
    should have high chances of finding errors

  • krishna shrestha

    Negative and Positive way testing are the guidelines for good writing test cases .

  • Banksy

    specified Input and preconditions that generate actual results against expected results

  • Solomon Ayanaw Habtu

    Try to identify categories of test cases like black box, whit box, functional, boundary, equivalence, decision table, phase change.

    Use to write with standard formats that include ID, test name, description, precise steps,…

  • Solomon Ayanaw Habtu

    The test cases should be created by considering: device and browser compatibility, Performance, usability, security, session, cookies.

Leave a Reply