Difference between revisions of "What Test Case Is"

From CNM Wiki
Jump to: navigation, search
(Script)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[File:Cnm-digital.png|400px|thumb|right|[[CNM Cyber suite]]s]][[What Test Case Is]] (hereinafter, the ''Lectio'') is the [[lectio|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]].
+
[[File:Cnm-digital.png|400px|thumb|right|[[CNMCyber suite]]s]][[What Test Case Is]] (hereinafter, the ''Lectio'') is the [[lectio|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 [[CNMCyber Bootcamps]].
  
  
 
==Content==
 
==Content==
The predecessor [[lectio]] is [[What Manual Test Is]].
+
The predecessor [[lectio]] is [[Verification vs Validation]].
  
 
===Script===
 
===Script===
 
:The English word, [[case]], originally derived from a Latin [[noun]] ''casus'' that meant an ''accident, event, occurrence; occasion, opportunity''. A [[test case]] is a set of [[requirement]]s for particular [[testing]].
 
:The English word, [[case]], originally derived from a Latin [[noun]] ''casus'' that meant an ''accident, event, occurrence; occasion, opportunity''. A [[test case]] is a set of [[requirement]]s for particular [[testing]].
  
:In [[systems engineering]], a ''test case'' commonly specifies the inputs, external factors, available assets, procedures, and expected outputs that the tested system shall produce. Having that specification, the [[tester]] who administers the [[performance test]] can evaluate whether the tested system achieves the objectives it has been designed to achieve.
+
:In [[systems engineering]], a [[functional test case]] commonly specifies the inputs, external factors, available assets, procedures, and expected outputs that the tested system shall produce. Having that specification, the [[tester]] who administers the [[product work test]] can evaluate whether the tested system achieves the objectives it has been designed to achieve.
  
:Not all ''performance cases'' must be highly detailed. For instance, a ''test case'' for this very [[lectio]] can be:<blockquote><code>Evaluate whether the closing question of the lectio reflects the brief lecture that this lectio includes.</code></blockquote>
+
:Not all ''performance cases'' must be highly detailed. For instance, one [[performance test case]] for this very [[lectio]] can be:<blockquote><code>Evaluate whether the closing question of the lectio reflects the brief lecture that this lectio includes.</code></blockquote>
  
:All ''test cases'' can be divided in two categories: [[progression test]]s and [[regression test]]s. [[Progression testing]] is undertaken to ensure that newly-developed features are developed properly. [[Regression testing]] is undertaken to ensure that newly-developed features do not interfere the proper functioning of the system prior to the recent changes.
+
:''Test cases'' for [[usability testing]] are rarely detailed; they tend to be more general than those for ''performance testing''. A simplest example of a [[usability test case]] can be,<blockquote><code>While using the tested system, report if you feel uncomfortable, get confused, or even start thinking what to do next.</code></blockquote>
  
:Those [[User story|user stori]]es that have been used for the last development can be perfectly used for ''progression testing''. Regularly, any [[acceptance test]] involves these ''stories''. Vice versa, those ''user stories'' that that were used for all the developments prior to the last one can be perfectly used for ''regression testing''.
+
:''Regression testing'' for [[user experience]] improvements is not feasible; all of ''usability testing'' is in the ''progression testing'' category.
 
 
:''Test cases'' for [[usability testing]] are rarely detailed; they tend to be more general than those for ''performance testing''. A simplest example of an usability test case can be,<blockquote><code>While using the tested system, report if you feel uncomfortable, get confused, or even start thinking what to do next.</code></blockquote>
 
  
 
===Key terms===
 
===Key terms===
:[[Test case]], [[case]], [[progression test]], [[progression testing]], [[regression test]], [[regression testing]]
+
:[[Test case]], [[case]], [[functional test case]], [[performance test case]], [[usability test case]]
  
 
===Closing===
 
===Closing===
:
+
:Write True or False
 +
:*[[Regression testing]] is quite feasible for [[Usability testing]].
  
The successor [[lectio]] is '''[[What UX Test Is]]'''.
+
The successor [[lectio]] is '''[[What Reporting Is]]'''.
  
 
==Presentations==
 
==Presentations==

Latest revision as of 02:54, 21 October 2023

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 CNMCyber Bootcamps.


Content

The predecessor lectio is Verification vs Validation.

Script

The English word, case, originally derived from a Latin noun casus that meant an accident, event, occurrence; occasion, opportunity. A test case is a set of requirements for particular testing.
In systems engineering, a functional test case commonly specifies the inputs, external factors, available assets, procedures, and expected outputs that the tested system shall produce. Having that specification, the tester who administers the product work test can evaluate whether the tested system achieves the objectives it has been designed to achieve.
Not all performance cases must be highly detailed. For instance, one performance test case for this very lectio can be:

Evaluate whether the closing question of the lectio reflects the brief lecture that this lectio includes.

Test cases for usability testing are rarely detailed; they tend to be more general than those for performance testing. A simplest example of a usability test case can be,

While using the tested system, report if you feel uncomfortable, get confused, or even start thinking what to do next.

Regression testing for user experience improvements is not feasible; all of usability testing is in the progression testing category.

Key terms

Test case, case, functional test case, performance test case, usability test case

Closing

Write True or False

The successor lectio is What Reporting Is.

Presentations

Slideshow

Video