el-get/test/README.md

# Tests

Like, yes, we have some! :)

## ERT-based tests

See `el-get-tests.el` in this directory.  You can run ERT-based tests by:

    test/run-ert.sh

To run the tests with GUI window for debugging, you can use:

    test/run-ert-interactive.sh

## Old issue reproducers

See the test/issues directory.
Remove el-get 'wait that's been broken for a long time already, fixes #758. The use case for el-get 'wait is very thin (setup file only), and fixing it would be hard enough that we're not going to work on it. If you want to wait until the packages are installed, just use 'sync. One reason why fixing that situation is not easy is that some error cases that happen at install time are not catched by El-Get code, so there's no place where to set the package status as "failed" or something equivalent. We wouls still have some "required" packages left, and if we don't count them in the progress information we hang up completely. This commit also refresh the test/README content to cope with the recent status.old backup file, and in passing reformat the file as Markdown. 2012-07-31 01:22:30 +08:00			`# Tests`
Fix the refactoring so that it actually works. This includes teaching methods that they now work with a symbolp PACKAGE, some more cleaning up, and some load-path adjustments now that a part of the code is in a subdirectory (methods). Also include some of the tests used to convince oneself that the refactoring didn't break any and all use cases for el-get, with some rough documentation about how to use them. 2011-09-23 03:48:11 +08:00
			`Like, yes, we have some! :)`

enable ert tests in travis, reorganize test files rename ert tests file test.el => el-get-tests.el move el-get-issue-* files to separate dir 2015-11-14 09:30:36 +08:00			`## ERT-based tests`
Fix the refactoring so that it actually works. This includes teaching methods that they now work with a symbolp PACKAGE, some more cleaning up, and some load-path adjustments now that a part of the code is in a subdirectory (methods). Also include some of the tests used to convince oneself that the refactoring didn't break any and all use cases for el-get, with some rough documentation about how to use them. 2011-09-23 03:48:11 +08:00
enable ert tests in travis, reorganize test files rename ert tests file test.el => el-get-tests.el move el-get-issue-* files to separate dir 2015-11-14 09:30:36 +08:00			See `el-get-tests.el` in this directory. You can run ERT-based tests by:
Add usage in test/README.md 2012-11-25 09:37:37 +08:00
			`test/run-ert.sh`

			`To run the tests with GUI window for debugging, you can use:`

			`test/run-ert-interactive.sh`
enable ert tests in travis, reorganize test files rename ert tests file test.el => el-get-tests.el move el-get-issue-* files to separate dir 2015-11-14 09:30:36 +08:00
			`## Old issue reproducers`

			`See the test/issues directory.`