summaryrefslogtreecommitdiff
path: root/spec/make_spec.lua (follow)
Commit message (Collapse)AuthorAgeFilesLines
* tests: avoid repeated hardcoded package version numbers all overHisham Muhammad2022-04-121-33/+33
|
* fix: pack: rockspec with a bare file in the urlHisham Muhammad2021-03-221-2/+3
|
* editorconfig: trim trailing whitespaceHisham Muhammad2021-03-161-11/+11
|
* make: support --only-depsHisham Muhammad2020-02-141-0/+12
| | | | Closes #1156.
* tests: shorter descriptionsHisham Muhammad2020-02-141-11/+11
|
* dependency pinning: luarocks.lock file and --pin flagHisham Muhammad2019-11-291-0/+119
| | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for pinning dependencies in projects and rocks: * Adds a new flag called `--pin` which creates a `luarocks.lock` when building a rock with `luarocks build` or `luarocks make`. This lock file contains the exact version numbers of every direct or indirect dependency of the rock (in other words, it is the transitive closure of the dependencies.) For `make`, the `luarocks.lock` file is created in the current directory. The lock file is also installed as part of the rock in its metadata directory alongside its rockspec. When using `--pin`, if a lock file already exists, it is ignored and overwritten. * When building a rock with `luarocks make`, if there is a `luarocks.lock` file in the current directory, the exact versions specified there will be used for resolving dependencies. * When building a rock with `luarocks build`, if there is a `luarocks.lock` file in root of its sources, the exact versions specified there will be used for resolving dependencies. * When installing a `.rock` file with `luarocks install`, if the rock contains a `luarocks.lock` file (i.e., if its dependencies were pinned with `--pin` when the rock was built), the exact versions specified there will be used for resolving dependencies.
* Support make --no-doc (#1092)Paul Ouellette2019-11-151-0/+16
| | | | | | * Support make --no-doc * Add test for make --no-doc
* Tests: add test cases for rocks with conflicting module namesHisham Muhammad2018-09-041-0/+105
| | | | | This tests the behavior of upgrades and downgrades on rocks that deploy both foo.lua and foo.so
* Tests: replace #blackbox with #integration and #whitebox with #unitGeorge Roman2018-06-041-1/+1
|
* Tests: make sure tests run from testrun/Hisham Muhammad2018-03-301-9/+18
|
* Reorganize test suite filesHisham Muhammad2018-01-081-2/+2
|
* Use versioned files only. (#734)Hisham Muhammad2017-10-041-5/+5
| | | | | | | | Let's take the opportunity of a new major version to make an important cleanup: getting rid of the error-prone unversioned configuration files. This drops support for: * Unversioned config.lua -> use config-5.x.lua * Unversioned luarocks/site_config.lua -> it always generates luarocks/core/site_config_5_x.lua * Unversioned lib/luarocks/rocks -> it always uses lib/luarocks/rocks-5.x
* Change setup/teardown in make tests to before/after due to wrong useroboo2017-07-061-2/+2
|
* Added LPeg dependency for lxsh to luarocks make testsroboo2017-07-051-0/+1
|
* Add a test for conflict resolution with mixed deploy typesPeter Melnichenko2016-11-011-1/+68
|
* Tests: luarocks_bool commands log their outputs on failure.Hisham2016-09-081-4/+4
|
* Windows and appveyor support for testsroboo2016-08-211-20/+23
|
* Test improvementsroboo2016-07-191-5/+5
|
* Fix of upload tests for lua5.3roboo2016-07-181-1/+1
|
* Make env vars, paths and run commands available on test env loadPeter Melnichenko2016-07-081-2/+2
|
* Tests: disable insulation and use describe() instead of expose()Peter Melnichenko2016-07-081-1/+1
|
* Remove all the unused imports in test suitePeter Melnichenko2016-07-081-2/+1
|
* New test-suite for LuaRocks (#581)robooo2016-07-071-0/+99
First version of new test-suite, using Busted framework based on Google Summer of Code project: https://summerofcode.withgoogle.com/projects/#5695811874717696 * Rewritten from Bash to Lua * Tests now check if they did what they were supposed to, beyond only checking success or failure of the `luarocks` command * Support for black-box (launching `luarocks` as an external command) and white-box (testing functions in modules directly) testing