Difference between revisions of "What Test Case Is"

From CNM Wiki
Jump to: navigation, search
(Script)
(Script)
Line 6: Line 6:
  
 
===Script===
 
===Script===
:
+
:The English word, [[case]], originally derived from a Latin noun ''testis that meant a witness or one who attests or, equally possibly, the related verb, testari that meant to bear witness. Testament literally means a witness testimony.
  
For example, say that you were testing the iOS app login example referenced above. You might write the following test cases:
+
from Latin casus (“a falling, a fall; accident, event, occurrence; occasion, opportunity; noun case”), perfect passive participle of cado (“to fall, to drop”).  
  
    Tapping “Login” in left nav menu should bring up a login screen
+
In software engineering, a test case is a specification of the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed to achieve a particular software testing objective, such as to exercise a particular program path or to verify compliance with a specific requirement.[1] Test cases underlie testing that is methodical rather than haphazard. A battery of test cases can be built to produce the desired coverage of the software being tested. Formally defined test cases allow the same tests to be run repeatedly against successive versions of the software, allowing for effective and consistent regression testing.[2]
    When logged in, tapping “Logout” in left nav menu should log the user out
 
    If user enters an email address that does not exist (with any password) and selects Login, relevant error message should come up
 
    If user enters a valid existing account email address with an incorrect password and selects Login, error message should come up
 
    When user enters valid email address and password and taps Login, they should be logged in and taken to Home screen
 
    When user is logged in, and closes app or re-starts device then re-opens, they should still be logged in
 
    Email address field should not be case sensitive
 
    Password field should be case sensitive
 
    Login screen elements should match design file
 
    Login button should be grey until user enters credentials (whether valid or not), at which point it should turn red
 
  
Test cases will usually be more detailed than the above, but these provide a simple example of what test cases are. When a deadline is urgent and the timeline is short, you may have to wing it. But when you do have time, having test cases makes testing less stressful and more thorough. It also increases the reliability of the process and results.
 
  
 
:Those [[User story|user stori]]es that have been used for the development can be perfectly used for ''progression testing''. Regularly, any [[acceptance test]] involves these ''stories''.
 
:Those [[User story|user stori]]es that have been used for the development can be perfectly used for ''progression testing''. Regularly, any [[acceptance test]] involves these ''stories''.

Revision as of 20:31, 8 November 2020

What Test Case Is (hereinafter, the Lectio) is the lesson part of Manual Testing Essentials lesson that introduces its participants to manual testing concepts. This lesson belongs to the CNMCT Entrance section of the CNM Cyber Placement.


Content

The predecessor lectio is What Manual Test Is.

Script

The English word, case, originally derived from a Latin noun testis that meant a witness or one who attests or, equally possibly, the related verb, testari that meant to bear witness. Testament literally means a witness testimony.

from Latin casus (“a falling, a fall; accident, event, occurrence; occasion, opportunity; noun case”), perfect passive participle of cado (“to fall, to drop”).

In software engineering, a test case is a specification of the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed to achieve a particular software testing objective, such as to exercise a particular program path or to verify compliance with a specific requirement.[1] Test cases underlie testing that is methodical rather than haphazard. A battery of test cases can be built to produce the desired coverage of the software being tested. Formally defined test cases allow the same tests to be run repeatedly against successive versions of the software, allowing for effective and consistent regression testing.[2]


Those user stories that have been used for the development can be perfectly used for progression testing. Regularly, any acceptance test involves these stories.

Key terms

Test case

Closing

The successor lectio is What UX Test Is.

Presentations

Slideshow

Video