git-annex/Command/Test.hs

{- git-annex command
 -
 - Copyright 2013 Joey Hess <joey@kitenet.net>
 -
 - Licensed under the GNU GPL version 3 or higher.
 -}

module Command.Test where

import Command

def :: [Command]
def = [ dontCheck repoExists $
	command "test" paramNothing seek "run built-in test suite"]

seek :: [CommandSeek]
seek = [withWords start]

{- We don't actually run the test suite here because of a dependency loop.
 - The main program notices when the command is test and runs it; this
 - function is never run if that works. -}
start :: [String] -> CommandStart
start _ = error "Cannot specify any additional parameters when running test"
embed test suite into git annex; available by running: git annex test I have seen some other programs do this, and think it's pretty cool. Means you can test wherever it's deployed, as well as at build time. My other reason for doing it is less happy. Cabal's handling of test suites sucks, requiring duplicated info, and even when that's done, it fails to preprocess hsc files here. Building it in avoids that and avoids having to explicitly tell cabal to enable test suites, which would then make it link the test executable every time, which is unnecessarily slow. This also has the benefit that now "make fast test" does a max speed build and tests it. 2013-02-27 19:35:07 +00:00			`{- git-annex command`
			`-`
			`- Copyright 2013 Joey Hess <joey@kitenet.net>`
			`-`
			`- Licensed under the GNU GPL version 3 or higher.`
			`-}`

			`module Command.Test where`

			`import Command`

			`def :: [Command]`
break dependency cycle by special casing running of test command 2013-02-27 19:48:26 +00:00			`def = [ dontCheck repoExists $`
embed test suite into git annex; available by running: git annex test I have seen some other programs do this, and think it's pretty cool. Means you can test wherever it's deployed, as well as at build time. My other reason for doing it is less happy. Cabal's handling of test suites sucks, requiring duplicated info, and even when that's done, it fails to preprocess hsc files here. Building it in avoids that and avoids having to explicitly tell cabal to enable test suites, which would then make it link the test executable every time, which is unnecessarily slow. This also has the benefit that now "make fast test" does a max speed build and tests it. 2013-02-27 19:35:07 +00:00			`command "test" paramNothing seek "run built-in test suite"]`

			`seek :: [CommandSeek]`
			`seek = [withWords start]`

break dependency cycle by special casing running of test command 2013-02-27 19:48:26 +00:00			`{- We don't actually run the test suite here because of a dependency loop.`
			`- The main program notices when the command is test and runs it; this`
			`- function is never run if that works. -}`
embed test suite into git annex; available by running: git annex test I have seen some other programs do this, and think it's pretty cool. Means you can test wherever it's deployed, as well as at build time. My other reason for doing it is less happy. Cabal's handling of test suites sucks, requiring duplicated info, and even when that's done, it fails to preprocess hsc files here. Building it in avoids that and avoids having to explicitly tell cabal to enable test suites, which would then make it link the test executable every time, which is unnecessarily slow. This also has the benefit that now "make fast test" does a max speed build and tests it. 2013-02-27 19:35:07 +00:00			`start :: [String] -> CommandStart`
break dependency cycle by special casing running of test command 2013-02-27 19:48:26 +00:00			`start _ = error "Cannot specify any additional parameters when running test"`