summaryrefslogtreecommitdiff
path: root/test/rebar_ct_SUITE.erl
Commit message (Collapse)AuthorAgeFilesLines
* move definition of 'EUNIT' macro to eunit provideralisdair sullivan2016-03-031-4/+28
| | | | add definition of 'COMMON_TEST' macro to eunit provider
* Take CT options errors and turn them to warningsFred Hebert2016-03-021-7/+7
| | | | | | | | The idea is that given we accept arbitrary config items for CT, we should similarly be able to pass unsupported options and keep things running. However for unsupported options, a warning is very useful to have.
* Merge pull request #1099 from talentdeficit/ct_includeTristan Sloughter2016-03-011-3/+27
|\ | | | | add support for common tests `include` flag
| * add support for common tests `include` flagalisdair sullivan2016-03-011-3/+27
| |
* | add a link to the docs about `test_spec` and `cover` in ct warningsalisdair sullivan2016-03-011-2/+2
| |
* | error on a cover spec in ct_optsalisdair sullivan2016-03-011-1/+19
|/
* fix paths for multiple app projects when running ct with no --dir argumentalisdair sullivan2016-01-301-5/+6
|
* add test for foo_SUITE_data filesalisdair sullivan2015-12-201-2/+8
|
* put `extra' ct test suites in `extras/apps/APPNAME' rather than `extras'alisdair sullivan2015-12-201-1/+44
| | | | this allows repeated test suite names across apps without conflicts
* allow ct suites to be specified at the root of a project (or root of app)alisdair sullivan2015-12-201-1/+45
| | | | | | | | previously rebar3 dropped suites declared at the root of the project (via `--suite=whatever_SUITE' probably) and warned. this was because the compiler would recursively copy and compile everything in the directory indicated by the test suite. this changes the copy mechanism to only copy erl source files and directories that end with `_SUITE_data' into the `extras' dir in `_build'
* error on ct/eunit argument errors instead of warningalisdair sullivan2015-11-151-10/+68
|
* calculate coverage info as late as possible in ct provider executionalisdair sullivan2015-11-051-2/+36
|
* reenable support for most command line options and rename `ct_tests` to ↵alisdair sullivan2015-11-011-3/+400
| | | | `ct_opts`
* 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
generated by cgit v1.1 at 2024-12-30 21:32:14 +0000