Revision as of 03:52, 16 March 2025 edit Kl5528 (talk \| contribs) 43 edits →Usability testing: added information about usability testing models Tag: Visual edit ← Previous edit		Revision as of 14:06, 18 March 2025 edit undo Itstamiris2007 (talk \| contribs) 102 edits m “Based on the criteria for measuring correctness from an oracle, software testing employs principles and mechanisms that might recognize a problem.” → “Based on the criteria for measuring correctness provided by an oracle, software testing employs principles and mechanisms that can identify potential issues.” (Replaced “from” with “provided by” for clarity and changed “might recognize a problem” to “can identify potential issues” for a more precise and formal tone). Tags: Reverted Visual edit Next edit →
Line 11: Software testing can determine the [[Correctness (computer science)\|correctness]] of software for specific [[Scenario (computing)\|scenarios]] but cannot determine correctness for all scenarios.<ref name="pan">{{Cite web \|last=Pan \|first=Jiantao \|date=Spring 1999 \|title=Software Testing \|url=http://www.ece.cmu.edu/~koopman/des_s99/sw_testing/ \|access-date=November 21, 2017 \|publisher=Carnegie Mellon University \|type=coursework}}</ref><ref name="Kaner2">{{Cite book \|last1=Kaner \|first1=Cem \|title=Testing Computer Software \|last2=Falk \|first2=Jack \|last3=Nguyen \|first3=Hung Quoc \|publisher=John Wiley and Sons \|year=1999 \|isbn=978-0-471-35846-6 \|edition=2nd \|___location=New York \|author-link=Cem Kaner}}</ref> It cannot find all [[software bug\|bugs]]. Based on the criteria for measuring correctness ~~from~~provided by an [[test oracle\|oracle]], software testing employs principles and mechanisms that ~~might~~can ~~recognize~~identify apotential ~~problem~~issues. Examples of oracles include [[specification]]s, [[Design by Contract\|contracts]],<ref>{{Cite conference \|last1=Leitner \|first1=Andreas \|last2=Ciupa \|first2=Ilinca \|last3=Oriol \|first3=Manuel \|last4=Meyer \|first4=Bertrand \|author-link4=Bertrand Meyer \|last5=Fiva \|first5=Arno \|date=September 2007 \|title=Contract Driven Development = Test Driven Development – Writing Test Cases \|url=http://se.inf.ethz.ch/people/leitner/publications/cdd_leitner_esec_fse_2007.pdf \|conference=ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007 \|___location=Dubrovnik, Croatia \|access-date=December 8, 2017}}</ref> comparable products, past versions of the same product, inferences about intended or expected purpose, user or customer expectations, relevant standards, and applicable laws. Software testing is often dynamic in nature; running the software to verify actual output matches expected. It can also be static in nature; reviewing [[source code\|code]] and its associated [[documentation]].

Software testing: Difference between revisions