úÎQ%N“/      !"#$%&'()*+,-.None 24=EKM($A data type for tests against forms.(The error paths that should be populated4The value the form should take (and should be valid)YInternal state used to share site initialization across tests, and to propogate failures.gThe main monad that tests run inside of. This allows both access to the application (via requests and #) and to running assertions (like ! or )).oThe result of making requests against your application. Most assertions act against these types (for example, , ', etc). IRuns a given action once after all the tests in the given block have run.Warning®: Due to current limitations to how Hspec works, this only works if all of the tests within the block are run. This means that if you only run some of the tests (using the -m% option) the action will not be run.The way to run a block of  tests within an /T test suite. This takes both the top level handler (usually `route routes`, where routesJ are all the routes for your site) and the site initializer (often named appB), and a block of tests. A test suite can have multiple calls to }, though each one will cause the site initializer to run, which is often a slow operation (and will slow down test suites).Warning]: Due to current limitations to how Hspec works, the way that we run cleanup actions (using  () from your site initializer depends on all* of the tests within the block passed to H running. This means that if you only run some of the tests (using the -m^ option) the cleanup won't happen. But, there is no reason why you can't have many calls to -, so the recommended behavior is to only use -m8 with queries that will run entire blocks. For example: >describe "api-tests" $ snap ... describe "db-tests" $ snap ...And then run with  -m api-tests or  -m db-testsÄ, rather than trying to match anything within. Hopefully, hspec will eventually be able to support what we need in such a way that filtering on any query won't prevent the cleanup from running.·This allows you to change the default handler you are running requests against within a block. This is most likely useful for setting request state (for example, logging a user in).%This performs a similar operation to  but in the context of ! (which is needed if you need to Q, produce values, and hand them somewhere else (so they can't be created within f).*Evaluate a Handler action after each test.+Evaluate a Handler action before each test.Runs a GET request.-Runs a GET request, with a set of parameters.!A helper to construct parameters.5Creates a new POST request, with a set of parameters.^Restricts a response to matches for a given CSS selector. Does nothing to non-Html responses.8Runs an arbitrary stateful action from your application.oRecords a test Success or Fail. Only the first Fail will be recorded (and will cause the whole block to Fail).lAsserts that a given stateful action will produce a specific different result after an action has been run."Asserts that two values are equal.&Asserts that two values are not equal.Asserts that the value is True.>Asserts that the value is not True (otherwise known as False).OAsserts that the response is a success (either Html, or Other with status 200). .Asserts that the response is not a normal 200.!(Asserts that the response is a NotFound.",Asserts that the response is not a NotFound.#(Asserts that the response is a redirect.$,Asserts that the response is not a redirect.%fAsserts that the response is a redirect, and thet the url it redirects to starts with the given path.&ÁAsserts that the response is not a redirect to a given path. Note that it can still be a redirect for this assertion to succeed, the path it redirects to just can't start with the given path.'CAssert that a response (which should be Html) has a given selector.(LAssert that a response (which should be Html) doesn't have a given selector.)IAsserts that the response (which should be Html) contains the given text.*QAsserts that the response (which should be Html) does not contain the given text.+'Tests against digestive-functors forms.,LRuns a request (built with helpers from Snap.Test), resulting in a response.-‡Runs a request against a given handler (often the whole site), with the given state. Returns any triggered exception, or the response..hEvaluates a given handler with the given state. Returns any triggered exception, or the value produced.1 Pairs of parameter and value. !"#$%&'(0)*+…If the form should succeed, Value a is what it should produce. If failing, ErrorPaths should be all the errors that are triggered.The form to runThe parameters to pass,-.1/  !"#$%&'()*+,-./   !"#$%&'()*+,-.(   !"#$%&'(0)*+,-.12      !"#$%&'()*+,-./012345hspec-snap-0.2.0.0Test.Hspec.SnapFormExpectations ErrorPaths PredicateValueSnapHspecState SnapHspecM TestResponseEmptyOtherRedirectNotFoundHtmlafterAllsnap modifySite modifySite' afterEval beforeEvalgetget'paramspostrestrictResponseeval setResult shouldChange shouldEqualshouldNotEqual shouldBeTrueshouldNotBeTrue should200 shouldNot200 should404 shouldNot404 should300 shouldNot300 should300ToshouldNot300ToshouldHaveSelectorshouldNotHaveSelectorshouldHaveTextshouldNotHaveTextform runRequestrunHandlerSafeevalHandlerSafe hspec2-0.4.2Test.Hspec.Runnerhspec haveSelector'$fExampleStateT