summaryrefslogtreecommitdiff
path: root/test/rebar_test_utils.erl
Commit message (Collapse)AuthorAgeFilesLines
* Use same random seeding function for random_name and random_vsnViacheslav V. Kovalev2015-06-281-3/+8
|
* Fixed review commentsDaniel Widgren2015-06-261-19/+1
|
* Some fixes after reviewViacheslav V. Kovalev2015-06-261-1/+2
|
* Fixed so that release tests now pass. Got all green tests.Daniel Widgren2015-06-261-1/+19
|
* Fix multi_app_default_dirs test on windows.Viacheslav Kovalev2015-06-261-2/+2
| | | | | Seed random with erlang:now() because os:timestamp precision is not enough on windows.
* Adding erl_first_files testFred Hebert2015-06-261-1/+1
| | | | | | The test works by using a parse transform that stamps modules with an attribute as it runs them. It then compiles everything, loads the module, and makes sure the stamps respect the defined order.
* check format of config file and print the bad section in the errorTristan Sloughter2015-06-181-1/+1
|
* add test for plugin with transitive depsTristan Sloughter2015-05-271-3/+4
|
* update stable_lock test from Fred's branchTristan Sloughter2015-05-211-12/+12
|
* install plugins from the global config to ~/.cache/pluginsTristan Sloughter2015-05-171-1/+16
|
* don't load package registry unless there are pkg deps to solveTristan Sloughter2015-04-281-2/+2
|
* track and cleanup code paths for different contextsTristan Sloughter2015-04-211-1/+2
|
* test building of deps pluginsTristan Sloughter2015-04-041-0/+15
|
* add a more direct way to generate an `eunitized` test app toalisdair sullivan2015-03-241-5/+25
| | | | test utils and add better eunit tests
* Merge pull request #286 from tsloughter/checkoutsFred Hebert2015-03-231-1/+2
|\ | | | | treat _checkouts as deps that are always compiled
| * treat _checkouts as deps that are always compiledTristan Sloughter2015-03-211-1/+2
| |
* | Test cases to exercise the dev_mode release optionKelly McLaughlin2015-03-231-1/+10
|/ | | | | | | | | | Add one test case to verify the dev_mode option for a release and another to verify overriding the dev_mode option in a profile for a release. Verification of proper dev_mode functioning is done in the rebar_test_utils:check_results/2 function by checking if all the directories in the release lib dir are symlinks or not and comparing that result to the dev_mode expectation passed as input to the check_results function.
* Implement deps conflicts as errorsFred Hebert2015-03-151-9/+13
| | | | | | | | The option {deps_error_on_conflict, true} will make it so conflicts in deps being fetched interrupts the operation rather than just display a warning. Defaults to `false'.
* update erlydtl compiler to output to _build, add simple testTristan Sloughter2015-03-071-0/+3
|
* copy project apps to deps output dir for compilationTristan Sloughter2015-02-281-9/+10
|
* make base_dir for a run include the profiles in path, link to shared depsTristan Sloughter2015-02-281-3/+3
|
* Add tests and fixes for packages upgradesFred Hebert2015-02-231-0/+3
| | | | | | | | | | - Track level of packages properly, they're not level 0 anymore (this could yield an issue where a src dep takes precedence over a pkg dep) - Proper stable sort of vertices in the digraph module - PkgDeps no longer 'see themselves' when fetching and upgrading after locking themselves - Pkg Locks are added to pkg deps rather than source deps - Updating test cases to support pkg mocking on top of src mocking
* Reuse test code and drop duplicated stuffFred Hebert2015-02-231-1/+10
|
* basic profile deps testsTristan Sloughter2015-02-221-0/+32
|
* fix test, remove use of filelib:wildcard for R15 supportTristan Sloughter2015-02-221-2/+2
|
* release and tar testsTristan Sloughter2015-02-221-0/+24
|
* Support multiple app upgrade & lock testsFred Hebert2015-02-111-0/+14
| | | | | | - Many apps is supported through and through - Not mentioning any app upgrades all apps - Locks are refreshed on disk and tested as such after an upgrade
* Partial work + Failing testsFred Hebert2015-02-111-8/+0
| | | | | The problem with the current effort is handling of transitive dependency upgrades and possible values.
* WIPFred Hebert2015-02-111-1/+11
| | | | | | Test that all the correct locks are set for an upgrade run. Now to actually re-run the install deps and prove it works
* add hook SUITE testsTristan Sloughter2015-01-311-0/+20
|
* test for eunit provideralisdair sullivan2015-01-061-4/+27
|
* Adding tests for checkouts being found & compiledFred Hebert2014-12-291-1/+9
|
* Add release-structured compiling testsFred Hebert2014-12-241-3/+9
|
* rewrite profilesTristan Sloughter2014-12-161-2/+1
|
* Adding pkg deps tests and refactoringsFred Hebert2014-12-161-1/+2
| | | | | | | | | | | | | | | | | | | - Adding tests for package deps - Adding conflict/override warnings for package deps - Adding cycle detection for packages - Adding cycle detection for mixed packages+source - Fixing internal dependency format of package resources when converted to rebar_app_info - normalizing level-order prioritization to be based on lexicographical sort of app names rather than traversal order (which is undefined for package deps) - Fixing tests for source deps for deep cycle detection - Fixing bugs with source deps - Relaxed version format checks for test utils A lot of fixes are combined in there because I didn't want to commit non-passing code, and many bugs were found when adding the second batch of tests as part of the original effort.
* Partial fix to circular deps (#40)Fred Hebert2014-12-061-21/+31
| | | | | | | | | - Adding tests - fixing use of set fetching to find repeated deps and prevent infinite loops On a circular loop rebar3 now fails with `{error, no_sort}`, which is uncaught and should be handled to consider the issue fully fixed.
* Initial tests for dependency resolvingFred Hebert2014-12-041-0/+138
- Reworked the helpers for existing suites and expanded them - Created a mock git resource module to test for its dependency fetching - Added a test suite for dependency resolving with first checks for common cases (https://gist.github.com/ferd/197cc5c0b85aae370436) Left to do would include: - Verify warnings - Verify failures - Verify dependency updates resolving