Difference between revisions of "What Manual Test Is"

From CNM Wiki
Jump to: navigation, search
(→‎Closing)
 
(29 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
[[File:Cnm-digital.png|400px|thumb|right|[[CNM Cyber suite]]s]][[What Manual Test 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 Manual Test 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]].
  
  
Line 6: Line 6:
  
 
===Script===
 
===Script===
−
:[[Testing]] can be defined as an [[endeavor]] undertaken to try somebody or something out to discover, evaluate, and/or measure the one's capacities and/or characteristics. The word originally came to English from Latin [[noun]] ''testis'' that meant ''a witness'' or ''one who attests'' or, possibly the related [[verb]], ''testari'' that meant ''to bear witness.'' ''Testament'' literally means a ''witness testimony.''
+
:Although [[manual testing]] can be defined as any [[testing]] that is administered by one or more [[human being]]s and is done with hands, ''manual testing'' usually refers to trials of [[work product]]s to discover their capacities, characteristics, and defects that are commonly called [[bug]]s. ''Manual testing'' is opposed to [[automated testing]] that is run by some [[testing software]]. This [[software]] is specifically designed specifically for ''automated testing''.
  
−
:In Old English, meanings of ''testing'' included ''trial to determine the correctness of something'' for a noun and ''examining the correctness of'' and ''putting to the proof'' for [[gerund]]s and [[verb]]s.
+
:The most of ''manual testing'' involves controlling whether the [[work product]] meets its [[requirement]]s, looking for ''bugs'', [[user experience]] issues, and/or areas for improvements while manually performing actions on a [[website]], [[mobile app]] or another [[end-user application]]. Those who perform those actions may be called [[manual tester]]s. The ''testers'' perform those actions occasionally or specifically.
  
−
:Another Latin word, ''contestari'' derived from the assimilated [[preposition]] meaning ''with, together'' and the [[verb]], ''testari''. The English word, ''contest'', literally means ''testing several objects together''.  
+
:The most of occasional testing is performed by [[end-user]]s who routinely use the software-powered systems while not having testing as their specific purpose. Any organization that runs these systems either gets or may consider getting [[feedback]] from the [[end-user]]s; this ''feedback'' may be used to improve the systems.
  
−
:In modern English, the term, ''testing'' may be used to describe a variety of actions and processes. However, all of those actions and processes involve two principal roles, a testing subject is one role and a tested object is another role.
+
:The specifically-arranged testing is usually performed by those workers, which [[job description]] directly or indirectly includes manual testing. Besides ''testing'' itself, these workers may perform four types of tasks. These ''testers'' may (a) plan testing, (b) write [[test case]]s, (c) report the identified ''bugs'', user experience issues, and/or areas for improvement, and/or (d) make those corrections that can be done.
  
−
:The tested object bears those capacities and characteristics that are the subject of testing. This object may be a human being, a group of people, non-human things, as well as any systems, including those that combine human beings and non-human things such as motor racing teams. The tested object can be defined as someone or something that undergoes a test.
+
:The specifically-arranged testing may address particular issues or areas for improvement. For instance, [[product work testing]] evaluates functionality of [[work product]]s, performance of those teams that developed them, and/or other results of the development. [[Usability testing]] aims to find areas for [[user experience]] ([[UX]]) improvements. [[Acceptance testing]] is undertaken to validate whether the developed system complies with its completion [[requirement]]s routinely called [[acceptance criteria]].
  
−
:For instance, [[drug test]]s determine the presence or absence of specified drugs or their metabolites. The [[Placement Admission Test]] that you have just successfully passed aimed to assess your general knowledge of [[CNM Cyber]]. One governments may study the effects of those laws that neighboring governments impose.
+
:The occasional testing involves neither planning nor writing ''test cases''; however, occasional testers either report or, in some cases, correct the bugs and other issues. For instance, you are using the product of those people who wrote the lines you are reading or listening right now. To improve any text that you see on [[CNM Wiki]] with or without any report, you don't need any [[job description]].
−
 
 
−
:Sometimes, the tested objects are called [[testee]]s or [[examinee]]s.
 
−
 
 
−
:On another side, a testing subject is someone or something that administers a test. Often, the testing person, people, or things are called [[tester]]s or [[examiner]]s. [[Educator]]s and [[researcher]]s conduct testing on a regular basis. [[Proctor]]s are those who watch ''examinees'' taking an examination to make sure that the ''examinees'' do not cheat. Human ''examiners'' may have plenty of other titles, but more and more ''tests'' are conducted automatically, by computers and machines rather than by people.
 
−
 
 
−
:Principally, all of tests may be categorized as ''experimental'', ''interventional'', or ''natural''.
 
−
 
 
−
:[[Observation]] is an essential part of any test. Those tests that include nothing, but ''observation'', are natural. Two examples of natural tests are temperature checks and so-called [[duck test]]s. The ''duck test'' asserts that,<blockquote>If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.</blockquote>
 
−
 
 
−
:Blood tests would be examples of interventional testing and vaccine testing is an experimental one.
 
  
 
===Key terms===
 
===Key terms===
−
:[[Testing]]
+
:[[Manual testing]], [[bug]], [[automated testing]], [[testing software]], [[manual tester]], [[usability testing]], [[user experience]] ([[UX]])
  
 
===Closing===
 
===Closing===
−
:
+
:Which of the statements below is correct:
 +
<ol type="a"><li>[[Automated testing]] is not always run by some [[testing software]].</li><li>Occasional testing could be organized to get [[end-user]]s feedback about testing object.</li><li>Writing [[test case]]s is an essential stage in occasional testing.</li><li>All of the other substantive answers are correct.</li></ol>
  
−
The successor [[lectio]] is '''[[What Test Case Is]]'''.
+
The successor [[lectio]] is '''[[Product Work Tests]]'''.
  
 
==Presentations==
 
==Presentations==

Latest revision as of 02:54, 21 October 2023

CNMCyber suites

What Manual Test 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 What Testing Is.

Script

Although manual testing can be defined as any testing that is administered by one or more human beings and is done with hands, manual testing usually refers to trials of work products to discover their capacities, characteristics, and defects that are commonly called bugs. Manual testing is opposed to automated testing that is run by some testing software. This software is specifically designed specifically for automated testing.
The most of manual testing involves controlling whether the work product meets its requirements, looking for bugs, user experience issues, and/or areas for improvements while manually performing actions on a website, mobile app or another end-user application. Those who perform those actions may be called manual testers. The testers perform those actions occasionally or specifically.
The most of occasional testing is performed by end-users who routinely use the software-powered systems while not having testing as their specific purpose. Any organization that runs these systems either gets or may consider getting feedback from the end-users; this feedback may be used to improve the systems.
The specifically-arranged testing is usually performed by those workers, which job description directly or indirectly includes manual testing. Besides testing itself, these workers may perform four types of tasks. These testers may (a) plan testing, (b) write test cases, (c) report the identified bugs, user experience issues, and/or areas for improvement, and/or (d) make those corrections that can be done.
The specifically-arranged testing may address particular issues or areas for improvement. For instance, product work testing evaluates functionality of work products, performance of those teams that developed them, and/or other results of the development. Usability testing aims to find areas for user experience (UX) improvements. Acceptance testing is undertaken to validate whether the developed system complies with its completion requirements routinely called acceptance criteria.
The occasional testing involves neither planning nor writing test cases; however, occasional testers either report or, in some cases, correct the bugs and other issues. For instance, you are using the product of those people who wrote the lines you are reading or listening right now. To improve any text that you see on CNM Wiki with or without any report, you don't need any job description.

Key terms

Manual testing, bug, automated testing, testing software, manual tester, usability testing, user experience (UX)

Closing

Which of the statements below is correct:
  1. Automated testing is not always run by some testing software.
  2. Occasional testing could be organized to get end-users feedback about testing object.
  3. Writing test cases is an essential stage in occasional testing.
  4. All of the other substantive answers are correct.

The successor lectio is Product Work Tests.

Presentations

Slideshow

Video

Retrieved from "https://pravka.bskol.com/w/index.php?title=What_Manual_Test_Is&oldid=119275"