summaryrefslogtreecommitdiff
path: root/test/rebar_ct_SUITE.erl
Commit message (Collapse)AuthorAgeFilesLines
* refactor `rebar_prv_common_test`alisdair sullivan2015-11-011-167/+144
| | | | | | | | * remove partial support for ct `test_spec` until it can be done properly and warn if `test_spec` is present in test opts * use new compiler functionality to reduce complexity of provider * reduce command line options available to those that can be supported properly
* refactor `rebar_erlc_compiler`alisdair sullivan2015-10-261-0/+1
| | | | | | | | | | | | | | | | | | | * modify compiler interface to work on either application objects or directories containing source files * compile all sources in `src_dirs` to the application `ebin` dir and all sources in `extra_src_dirs` to a directory mirroring it's position in the app's `_build` directory. for example, `apps/foo/more` would compile to `_build/default/lib/foo/more` for `extra_src_dirs` in the root of a project with multiple applications (so orphan directories that don't "belong" to an application) compile to `_build/default/extras/more` * copy directories specified in `extra_src_dirs` into the `_build` directory so tools like `ct` and `xref` that expect source to be in a particular location still work * clean compiled artifacts from all `extra_src_dirs` * alter `eunit`, `ct` and `cover` to work with the new directory structure * billions of new tests
* add comment for `data_dir' test in `rebar_ct_SUITE'alisdair sullivan2015-09-141-0/+1
|
* test for ensuring `data_dir` is set correctly in ct configsalisdair sullivan2015-09-141-4/+14
| | | | | | this test almost certainly only fails under very limited circumstances limiting it's utility. it is known to fail with some versions of rebar3 when this test is run via `rebar3 ct --cover`
* delete all symlinks when copying from project files to `_build` treealisdair sullivan2015-05-091-2/+34
| | | | | | to prevent any data from being overwritten fixes #395
* modify `ct` provider to copy selected directories and compile themalisdair sullivan2015-04-031-0/+520
alongside their source (ie, if `some_tests` is a directory that contains test suites beams resulting from compiling them will be placed in `some_tests` in the appropriate `_build` directory