úÎ6W4{     7Anything that can be used as an example of a behavior. @Create a description and example of a behavior, a list of these  is used by  4. Once you know what you want to specify, use this.  describe "closeEnough" [ 3 it "is true if two numbers are almost the same" " (1.001 `closeEnough` 1.002),  8 it "is false if two numbers are not almost the same" ' (not $ 1.001 `closeEnough` 1.003)  ]  A description of this behavior. An example for this behavior. ;Everything needed to specify and show a specific behavior. 2What is being tested, usually the name of a type. $The specific behavior being tested. The status of this behavior. "The result of running an example.  DCreate a set of specifications for a specific type being described. 2 Once you know what you want specs for, use this.  describe "abs" [ : it "returns a positive number given a negative number"  (abs (-1) == 1)  ] AThe name of what is being described, usually a function or type. 7A list of behaviors and examples, created by a list of .  Combine a list of descriptions. MEvaluate a Result. Any exceptions (undefined, etc.) are treated as failures. MDeclare an example as not successful or failing but pending some other work. , If you want to report on a behavior but don'!t have an example yet, use this.  describe "fancyFormatter" [ 5 it "can format text in a way that everyone likes" > (pending "waiting for clarification from the designers")  ] 1An explanation for why this behavior is pending. &Create a document of the given specs. /Create a document of the given group of specs. %Create a document of the given spec. :Create a summary of how long it took to run the examples. GCreate a summary of how many specs exist and how many examples failed. &Create a document of the given specs. N This does not track how much time it took to check the examples. If you want # a description of each spec and don'+t need to know how long it tacks to check,  use this. !The specs you are interested in. !The specs you are interested in. =Create a document of the given specs and write it to stdout. J This does track how much time it took to check the examples. Use this if K you want a description of each spec and do need to know how long it tacks 3 to check the examples or want to write to stdout. Same as J except it returns a bool indicating if all examples ran without failures Same as N except the program exits successfull if all examples ran without failures or 0 with an errorcode of 1 if any examples failed. GCreate a document of the given specs and write it to the given handle. J This does track how much time it took to check the examples. Use this if K you want a description of each spec and do need to know how long it tacks C to check the examples or want to write to a file or other handle. R writeReport filename specs = withFile filename WriteMode (\ h -> hHspec h specs) .A handle for the stream you want to write to. !The specs you are interested in. ;Create a more readable display of a quantity of something.       !"#!"#!"#     $      !"#$$%&'( hspec-0.3.0Test.Hspec.InternalTest.Hspec.QuickCheckTest.Hspec.HUnitSpecs Test.Hspec SpecVerifieritSpecname requirementresultResultPendingFailSuccessdescribe descriptionssafelypending documentSpecs documentGroup documentSpec timingSummary failedCountsuccessSummary pureHspec pureHspecBhspechspecBhspecX toExitCodehHspecquantifypropertydetailsQuickCheckPropertymainpreablespecs