Merge pull request #108 from cubicdaiya/langsupport/ja

support japanese message output
Add Terra support.
Merge branch 'master' of git://github.com/Olivine-Labs/busted

Conflicts:
	src/core.lua
	src/moon.lua
Merge branch 'master' of github.com:Olivine-Labs/busted
make pcall loop dependent

fixes #171
use copcall only if _VERSION==Lua 5.1

This applies to luajit and Lua 5.1
Merge pull request #173 from lipp/fix-pcall-segfault

make pcall loop dependent
Merge branch 'master' of git://github.com/Olivine-Labs/busted

Conflicts:
	src/core.lua
Merge pull request #162 from Eloff/master

Remove unused function moon.loader, add some missing local declarations, add Terra support
Merge branch 'master' of github.com:Olivine-Labs/busted
Attempt to fix windows install with lua-cliargs
Reverted last commit
add finally call
Merge pull request #183 from lipp/add-finally

add finally call
Fix describe issues

Show nested describe names in test output, and also fix a problem where
describe-level tags were broken.
update test for longer descriptions
Merge pull request #190 from Olivine-Labs/nested-describes-and-fix-tags

Fix describe issues
busted 1.9.1
Implement support for excluding tests based on tags

This patch introduces a new command-line option, ‘--exclude-tags’,
which allows to user to skip any tests that have the given tags.
Syntactically the option is the same as ‘--tags’, but semantically it
is the exact opposite.  There are situations where the user will not
want to run every test.  For example, if certain tests are
time-consuming or use a lot of resources then the user may want Busted
to ignore those tests.

It is an error for the user to use the same tag name in both ‘--tags’
and ‘--exclude-tags’.  We treat this as an error under the assumption
that the user made mistake when invoking Busted.  Logically it makes
no sense to tell Busted to include and exclude the same tests at the
same time.

This patch resolves #193.

Signed-off-by: Eric James Michael Ritz <lobbyjones@gmail.com>
Improve the tests for ‘--exclude-tags’ to clarify its precedence

This patch introduces a separate collection of tests for running
Busted with ‘--tags’ and ‘--exclude-tags’ at the same time.  It also
adds multiple tags to one test so that we can demonstrate that
‘--exclude-tags’ always takes precedence.  For example, consider the
following test:

    it("tests database creation #database #longtime", function ()
        -- ...
    end)

It is reasonable for the user to want to run all tests tagged with
‘#database’ but exclude those tagged with ‘#longtime’ so as to skip
tests that would eat up a lot of time and resources.  In this
situation the command

    busted --tags="database" --exclude-tags="longtime"

will prevent Busted from running the example test.  The changes to the
tests in this patch help clarify that behavior.

Note well that we do not treat this situation as an error.  There are
legitimate situations where a user may use ‘--exclude-tags’ and
‘--tags’ to refer to different tags which happen to match the same
test, e.g. the example above.  However, we still consider it an error
for the same literal tag to appear with both options, e.g.

    busted --tags=database --exclude-tags=database

and the test suite checks for this user error.

Signed-off-by: Eric James Michael Ritz <lobbyjones@gmail.com>