\A      !"#$%&'()*+,-./0123456789:;<=>?@  Safe-InferredABTake a list of actions and execute them in parallel, no more than n  at the same time A#maximum number of parallel threads list of actions to execute BAABNone ;The purpose of this data type is to capture the dictionary ' corresponding to a particular option. <A set of options. Only one option of each type can be kept. GIf some option has not been explicitly set, the default value is used. +An option is a data type that inhabits the  type class. ;The value to use if the option was not supplied explicitly +Try to parse an option value from a string FThe option name. It is used to form the command line option name, for F instance. Therefore, it had better not contain spaces or other fancy @ characters. It is recommended to use dashes instead of spaces. @The option description or help string. This can be an arbitrary  string. A command-line option parser. ?It has a default implementation in terms of the other methods. D You may want to override it in some cases (e.g. add a short flag). FEven if you override this, you still should implement all the methods ) above, to allow alternative interfaces. Set the option value Query the option value Change the option value <Safe read function. Defined here for convenience to use for  . C$Later options override earlier ones DEF C    DEF CNone ;A pattern to filter tests. For the syntax description, see   4http://documentup.com/feuerbach/tasty#using-patterns !A pattern that matches anything. Parse a pattern FTest a path (which is the sequence of group titles, possibly followed & by the test title) against a pattern  GHIJKLMNOPQRSTUVWXYZ[  HGIJKLMONPTSRQUVWXYZ[None5Number of parallel threads to use for running tests. Note that this is not included in .  Instead, it'0s automatically included in the options for any   TestReporter ingredient by ingredientOptions, because the way test G reporters are handled already involves parallelism. Other ingredients ) may also choose to include this option. CThe list of all core options, i.e. the options not specific to any F provider or ingredient, but to tasty itself. Currently only contains  . \\None])Useful wrapper for use with foldTestTree /The main data structure defining a test suite. HIt consists of individual test cases and properties, organized in named * groups which form a tree-like hierarchy. CThere is no generic way to create a test case. Instead, every test F provider (tasty-hunit, tasty-smallcheck etc.) provides a function to  turn a test case into a . Groups can be created using %.  Add some options to child tests 1Assemble a number of tests into a cohesive group &A single test of some particular type 'The name of a test or a group of tests 4The interface to be implemented by a test provider.  The type t= is the concrete representation of the test which is used by  the provider.  Run the test @The list of options that affect execution of tests of this type Test progress information. HThis may be used by a runner to provide some feedback to the user while # a long-running test is executing. "textual information about the test' s progress  ) should be a value between 0 and 1. If it' s impossible ! to compute the estimate, use 0. !A test result ## should be ^ for a passed test and _ for  a failed one. $$. may contain some details about the test. For  a passed test it'6s ok to leave it empty. Providers like SmallCheck and D QuickCheck use it to provide information about how many tests were  generated. For a failed test, $ should typically provide more  information about the failure. %3Create a named group of test cases or other groups &&Fold a test tree into a single value. CApart from pure convenience, this function also does the following  useful things:  ? Keeping track of the current options (which may change due to   nodes) 9 Filtering out the tests which do not match the patterns FThus, it is preferred to an explicit recursive traversal of the tree. >Note: right now, the patterns are looked up only once, and won't be 8 affected by the subsequent option changes. This shouldn't be a problem 9 in practice; OTOH, this behaviour may be changed later. `@Get the list of options that are relevant for a given test tree ]aboptions the test to run a callback to report progress  !"#$%&interpret a single test interpret a test group initial options `c]ab !"#$%&` ]ab !"#$%&`cNone' Convert a test to a leaf of the  ' !"#$'!"#$ '' None (GMapping from test numbers (starting from 0) to their status variables. HThis is what an ingredient uses to analyse and display progress, and to  detect when tests finish. dInt is the first free index IntMap maps test indices to:  the action to launch the test * the status variable of the launched test )Current status of a test *"test finished with a given result +(test threw an exception and was aborted ,test is being run -!test has not started running yet eStart executing a test f Prepare the test tree to be run g7Start running all the tests in the TestMap in parallel .FStart running all the tests in a test tree in parallel. The number of  threads is determined by the  option. BReturn a map from the test number (starting from 0) to its status  variable. (hd)*+,-eCthe action to execute the test, which takes a progress callback as  a parameter variable to write status to fg.()*+,-.(hd)-,+*efg. None//s make your test suite tasty. EIngredients represent different actions that you can perform on your @ test suite. One obvious ingredient that you want to include is ; one that runs tests and reports the progress and results. GAnother standard ingredient is one that simply prints the names of all  tests. Similar to test providers (see  ), every ingredient may specify F which options it cares about, so that those options are presented to ; the user if the ingredient is included in the test suite. 1An ingredient can choose, typically based on the  , whether to  run. That' s what the i- is for. The first ingredient that agreed to I run does its work, and the remaining ingredients are ignored. Thus, the 8 order in which you arrange the ingredients may matter. GUsually, the ingredient which runs the tests is unconditional and thus G should be placed last in the list. Other ingredients usually run only G if explicitly requested via an option. Their relative order thus doesn't  matter. That'As all you need to know from an (advanced) user perspective. Read , on if you want to create a new ingredient. $There are two kinds of ingredients. 1, if it agrees to run, 6 automatically launches tests execution, and gets the ( which 9 it uses to report the progress and results to the user. 0< is the second kind of ingredient. It is typically used for H test management purposes (such as listing the test names), although it 1 can also be used for running tests (but, unlike 1 , it has C to launch the tests manually). It is therefore more general than  1. 1# is provided just for convenience.  The function'7s result should indicate whether all the tests passed. In the 0 case, it'(s up to the ingredient author to decide E what the result should be. When no tests are run, the result should  probably be ^7. Sometimes, even if some tests run and fail, it still  makes sense to return ^. jTry to run an /. 7If the ingredient refuses to run (usually based on the ),  the function returns k. For a 11, this function automatically starts running the  tests in the background. 2Run the first / that agrees to be run. #If no one accepts the task, return k. This is usually a sign of  misconfiguration. 3@Return the options which are relevant for the given ingredient. Note that this isn')t the same as simply pattern-matching on  /. E.g. options for a 1 automatically include  . 4Like ingredientOption', but folds over multiple ingredients. /01j234/01234/10j234 None5BGenerate a command line parser from a list of option descriptions 6@All the options relevant for this test suite. This includes the B options for the test tree and ingredients, and the core options. 7+The command line parser for the test suite 8FParse the command line arguments and run the tests using the provided  ingredient list 567856785678 Nonel,Compute the amount of space needed to align OKs and FAILs 9A simple console UI mnopqrstuvwxyl9z{|}~9monpqrstuvwxyl9z{|}~ None:This option, when set to ^&, specifies that we should run in the  list tests mod<*Obtain the list of all tests in the suite =<The ingredient that provides the test listing functionality :;<=:;<=:;<=None# &()*+,-./0123456789:;<=#&/102349=:;<578)-,+*(.6 None>3Parse the command line arguments and run the tests ?;Locally adjust the option value for the given test subtree @8Locally set the option value for the given test subtree >?@%8>?@%>8?@>?@ !"#$%&'()**+,--./012 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E E F GHIJKLMNNOPQRSTUVWXYZ[\]^_`abcdefgefhidjk l m n o lpqr spqt u v w v x y y z { | } ~  tasty-0.4Test.Tasty.OptionsTest.Tasty.RunnersTest.Tasty.Providers Test.TastyTest.Tasty.ParallelTest.Tasty.PatternsTest.Tasty.CoreOptionsTest.Tasty.CoreTest.Tasty.RunTest.Tasty.IngredientsTest.Tasty.CmdLine&Test.Tasty.Ingredients.ConsoleReporter Test.Tasty.Ingredients.ListTestsOptionDescriptionOption OptionSetIsOption defaultValue parseValue optionName optionHelpoptionCLParser setOption lookupOption changeOptionsafeRead TestPattern noPatternparseTestPatterntestPatternMatches NumThreads getNumThreads coreOptionsTestTreePlusTestOptions TestGroup SingleTestTestNameIsTestrun testOptionsProgress progressTextprogressPercentResultresultSuccessfulresultDescription testGroup foldTestTree singleTest StatusMapStatusDone Exception Executing NotStartedlaunchTestTree Ingredient TestManager TestReportertryIngredientsingredientOptionsingredientsOptions optionParser suiteOptionssuiteOptionParserdefaultMainWithIngredientsconsoleTestReporter ListTests testsNames listingTests defaultMain adjustOption localOption runInParallel myForkFinally$fMonoidOptionSet OptionValue NoPatterntp_categories_only tp_negated tp_match_mode tp_tokensTestPatternMatchMode PathMatchMode TestMatchModeToken LiteralTokenDoubleWildcardToken WildcardToken SlashTokentokenizebuildTokenRegexregexEscapeChar pathToStringdropLast$fIsOptionTestPattern$fReadTestPattern$fIsOptionNumThreads AppMonoidghc-prim GHC.TypesTrueFalse treeOptionsgetApp$fMonoidAppMonoidTestMap executeTest createTestMap launchTestsbase Data.MaybeMaybe tryIngredientNothingcomputeAlignmentMaximum MinusInfinityM RunnerStateix nestedLevelfailures initialState indentSizeindent formatDescfailokinfoOkinfoFailoutput$fMonoidMaximum$fIsOptionListTests