Revision as of 14:51, 26 March 2015 edit 130.149.238.229 (talk) →Strengths and weaknesses: static analysis points to something different ← Previous edit		Revision as of 14:51, 10 April 2015 edit undo Rjwilmsi (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 933,673 edits m →Critique: Journal cites, added 1 DOI using AWB (10870) Next edit →
Line 95: An Oracle is an instrument for verifying whether the outcomes match the program specification or not. An operation profile is knowledge about usage patterns of the program and thus which parts are more important. For programming languages and platforms which have contracts (for example Eiffel. .NET or various extensions of Java like JML, CoFoJa...) contracts act as natural oracles and the approach has been applied successfully.<ref name="AutoTest">http://se.inf.ethz.ch/research/autotest/</ref> In particular, random testing finds more bugs than manual inspections or user reports (albeit different ones).<ref name="ManualvsRandom">{{cite journal\|title=On the number and nature of faults found by random testing\|year=2009\|publisher=John Wiley and Sons\|url=http://onlinelibrary.wiley.com/doi/10.1002/stvr.415/abstract\|author=Ilinca Ciupa\|author2=Alexander Pretschner\|author3=Manuel Oriol\|author4=Andreas Leitner\|author5=Bertrand Meyer\|journal=Software Testing, Verification and Reliability\|doi=10.1002/stvr.415\|volume=21\|pages=3–28}}</ref> == See also ==

Random testing: Difference between revisions