summaryrefslogtreecommitdiff
path: root/test/rebar_eunit_tests.erl
Commit message (Collapse)AuthorAgeFilesLines
* Fix Erlang 20 export_all warningsTuncer Ayaz2017-08-181-8/+0
| | | | Fix other warnings and whitespace errors as well.
* Fix windows eunit testsLuis Rascão2015-10-251-6/+10
| | | | | | | | | | | File tests: windows file operations should abort on error the same as unix operations invoked through sh. Also windows does not support the '?' character in filenames. Eunit tests: the 'All' prefix is missing on the 'x tests passed' message. Eunit only prints the 'All' prefix if there are more than 2 passed tests, dropping the prefix on the match works for all cases.
* Add test for eunit_first_filesAndrey Teplyashin2015-09-211-1/+37
|
* Fix eunit test on OTP18Luis Rascao2015-08-241-1/+1
| | | | | OTP18 changed the output failed assertion string from assertEqual_failed to assertEqual
* Manually clean up pathsEvan Vigil-McClanahan2014-08-181-0/+56
| | | | | | | Using code:set_path/1 with very large paths is very slow on larger projects. On my mid-sized project, it seems to take around .4s per call. Emulating the call with direct path removal (using code:del_path/1) seems to be quite a lot faster.
* Add qualified name tests specification (see #118)Sergey Savenko2014-05-291-0/+40
| | | | | | | | | Augment 'tests' option of 'rebar eunit' command with ability to specify tests to run using module-qualified names. This change also forced me to change the way modules for coverage and for testing itself are selected - module-qualified tests specifications are now taken into consideration. Extend tests to cover new functionality. Update dialyzer_reference accordingly.
* Fix file handling on windows for testsOliver Ferrigni2013-01-141-3/+11
| | | | | | | Running tests on windows creates false positive due to setup failures not executing all tests. Checking for tmp_dir was failing on subsequent runs. Added cases to tmp_dir creation to delete preexisting tmp_dirs in .eunit directory.
* eunit: analyze coverage only for cover compiled modulesShunichi Shinohara2012-09-131-17/+27
| | | | This change fixes #310.
* Cleanup and commentTuncer Ayaz2012-08-201-1/+1
|
* Fix tests= option not running generator testsRoberto Ostinelli2012-08-201-1/+27
|
* Add experimental tests= filter without eunit suitesRoberto Ostinelli2012-08-201-1/+19
|
* Add experimental tests= filter for eunit suitesRoberto Ostinelli2012-08-111-0/+118
|
* Use separate dirs for eunit and qcTuncer Ayaz2012-08-091-13/+13
|
* Add 'qc' cmd and rename eunit-compile to test-compileTuncer Ayaz2012-07-231-13/+13
|
* Fix test/rebar_eunit_tests.erlSlava Yurin2012-06-291-6/+8
|
* rebar_eunit_tests: avoid repetitionTuncer Ayaz2011-08-071-2/+3
|
* rebar_eunit_tests: check return valuesTuncer Ayaz2011-08-071-21/+15
|
* Fix whitespace errors in unit testsTuncer Ayaz2011-08-051-16/+17
|
* Clean up emacs file local variablesTuncer Ayaz2011-01-311-1/+1
|
* Fix file existence checksTuncer Ayaz2011-01-291-3/+3
|
* Apply Tidier suggestionsTuncer Ayaz2011-01-131-1/+1
|
* Port rebar_eunit_tests to WindowsJuhani Rankimies2010-10-271-5/+12
|
* Fix incorrect coverage count when prod modules include EUnit header.Chris Bernard2010-05-151-2/+22
| | | | | | | | Modules that include the EUnit header get an implicit test/0 fun, which cover considers a runnable line, but eunit:(TestRepresentation) never calls. Result: prod modules with tests can never reach 100% coverage. Ironic. In this case, fix it by decrementing the NotCovered counter returned by cover:analyze/3.
* Fixed 3 bugs in rebar_eunit. Added EUnit tests to capture them.Chris Bernard2010-03-041-0/+229
1. When running the eunit command with the convention of putting tests in "*_tests" modules, eunit would run those tests twice. This is because: 1) eunit:test/1 will naturally look for foo's tests both in foo, and in foo_tests, and 2) eunit:test/1 was being folded over all project modules. The fix is to filter "*_tests" modules from the list passed to eunit:test/1. 2. When running the eunit command with cover enabled and tests in a 'test' directory, cover would error because it couldn't find the source code for those tests. This is because cover:analyze/3 will only find module source in "." and "../src". This is hard-coded in cover :-(. Since cover shouldn't be calculating code coverage on test code anyway, the fix is to not fold cover:analyze/3 over non-production code. 3. When running the eunit command with cover enabled and a test suite defined, cover would only attempt to calculate coverage on the the test suite itself. This was because only the suite was passed to cover:analyze/3. The fix is to fold cover:analyze/3 over all the production code, filtering out the suite module if it is defined.