summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
...
* tests/sandboxes/mounting/mount_simple.py: Changed to test new Mounter objectsandbox-mounts-refactorTristan Van Berkom2017-11-061-3/+3
|
* Refactoring: Move exceptions module to be privateTristan Van Berkom2017-11-0620-24/+26
| | | | Hide all of buildstream's internal exceptions from the API surface.
* tests/sources/tar.py: Removing some unused test dataTristan Van Berkom2017-11-062-8/+0
|
* tests/sources/zip.py: Adding tests for zip source edge casesTristan Van Berkom2017-11-0613-0/+221
|
* tests/sources/fixture.py: Removing the old deprecated fixtureTristan Van Berkom2017-11-061-55/+0
|
* tests/sources/bzr.py: Removing bzr source testTristan Van Berkom2017-11-0613-238/+0
| | | | | | | | This does not test much more than the regular frontend tests against the bzr source, and was presenting difficulty to migrate to the proper new CLI fixtures. This was also the last source test using the older deprecated fixture.
* Updating cache key test for recent changes related to issue #121Tristan Van Berkom2017-11-063-2/+2
|
* Updating all test cases for the removal of architecture conditionals and optionsTristan Van Berkom2017-11-0637-201/+53
|
* tests/sources/git.py: Converted to use newer CLI fixturesTristan Van Berkom2017-11-055-373/+63
|
* testutils: Added optional subdir parameter to repo creationTristan Van Berkom2017-11-055-10/+25
| | | | In case a test wants to create more than one repo.
* tests/sources/patch.py: Converted to use CLI fixturesTristan Van Berkom2017-11-048-103/+82
|
* tests/sources/local.py: Removed some more unneeded steps in the testTristan Van Berkom2017-11-041-10/+2
|
* tests/sources/local.py: Remove one line of deadcodeTristan Van Berkom2017-11-041-1/+0
|
* Add tests for multiple targetsTristan Maat2017-11-0415-0/+103
|
* Adjust tests to new APITristan Maat2017-11-048-74/+74
|
* tests/sources/local.py: Migrated test to use frontend fixturesTristan Van Berkom2017-11-043-40/+45
|
* tests/sources/tar.py: Converted tar test to use the CLI and enhancedTristan Van Berkom2017-11-0314-107/+134
| | | | | | Now test to also ensure that base-dir expressions always behave the same way regardless of whether the tarball was created with a leading '.' or not.
* Add a new zip sourcezipMathieu Bridon2017-11-038-1/+58
| | | | This is equivalent to the tar source, but for Zip archives.
* tests: Reuse utils.sha256sumMathieu Bridon2017-11-031-8/+2
| | | | | The utility function was added in 08da7cc7, but it never was removed from here.
* tests/testutils/repo/tar.py: Fixed for changed tar behaviorTristan Van Berkom2017-11-021-2/+2
| | | | | | This test was encoding tarballs with '.', so the change of ignoring '.' breaks this - now we just make the tar test scaffolding use an empty string for the base-dir.
* Clean old Platform.get_platform referencesTristan Maat2017-11-014-4/+4
|
* Catch attempts to compose a listSam Thursfield2017-10-313-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Attempting to compose a list property would result in an unhandled exception: AttributeError: 'CommentedSeq' object has no attribute 'get' We now at least detect the situation and produce an exception that the frontend will report neatly: Error loading pipeline: element.bst [line 11 column 4]: Only values of type 'dict' can be composed. I was getting this error from an attempt to conditionally extend the sources list: sources: (?): arch == "x86_64": - url: http://example.com/x86_64 The correct way to do this is to move the conditional into the parent dict, e.g.: (?): arch == "x86_64": sources: - url: https://example.com/x86_64 It would be nice if the error message could hint at how the user can do what they want, but it doesn't seem possible in this case.
* tests/frontend/track.py: Added tests for recursive tracking and --exceptTristan Van Berkom2017-10-301-10/+103
|
* tests/testutils/runcli.py: get_element_state() now uses --downloadableTristan Van Berkom2017-10-291-0/+1
| | | | | | | | This wont take any additional time because if there is a remote artifact share configured in the pytest suite, it can only be a locally created one - this makes the push/pull tests work after recently making downloading of remote refs optional for the sake of issue #140.
* test/format/projectoverrides.py: Test project wide element type overrides128-status-ticker-fails-to-update-periodically-on-some-buildsTristan Van Berkom2017-10-253-0/+38
| | | | | | First case simply asserts that prepending to configure-commands from the project.conf works as intended, ensuring we dont regress issue #127
* Issue #124: Add test for staging to element build directory124-test-that-an-error-is-raised-when-staging-to-the-elements-build-directoryTristan Maat2017-10-234-0/+35
|
* tests/format: Test proper failure of reference to undefined optionsTristan Van Berkom2017-10-233-0/+29
| | | | | When using an undefined option in a conditional expression, buildstream should error out and print a good message about it.
* tests/cachekey: Fixing cache key test after changing default strip commandsTristan Van Berkom2017-10-232-2/+2
|
* tests/cachekey: Refactoring to now include an automatic updaterTristan Van Berkom2017-10-232-15/+78
| | | | | | | | When cache key tests fail, and when it is intentional that the keys have changed, then run ./tests/cachekey/update.py to update the keys. This is also useful whenever adding new tests.
* tests/testutils/runcli.py: Optionally make the runner not verboseTristan Van Berkom2017-10-231-8/+10
| | | | This is so that we can use it in other contexts than running tests
* tests/frontend: Removing messTristan Van Berkom2017-10-223-16/+0
| | | | | | | | | Here would be the right place to test that an error is raised when staging files to the build directory. These files here, would be good for that purpose, however they are just deadcode which somehow got added to the git history, no tests use them.
* tests/sources/generic.py: Removing test, no tests should ever be added hereTristan Van Berkom2017-10-224-37/+0
| | | | | | | | | New tests only via the frontend cli, never mucking about with source APIs directly, this whole directory needs to eventually be removed. This test was also testing the wrong condition, it's okay that a source stage to a non-empty directory, it's not okay that an element stages it's group of sources to a non-empty directory.
* tests/frontend/buildcheckout.py: Assert that build directories are removedTristan Van Berkom2017-10-211-0/+5
| | | | After successful builds.
* tests/cachekey: Fixing cache key test after modifying project.conf default ↵Tristan Van Berkom2017-10-2122-36/+22
| | | | environment
* Add warnings when staging to /buildstream/build74-prevent-artifacts-from-containing-files-in-buildstream-buildTristan Maat2017-10-197-0/+53
|
* tests/yaml/, tests/format/: Added tests for list composition directivesTristan Van Berkom2017-10-1716-104/+324
|
* tests/format/optionexports.py: Testing variable exports for base option typesTristan Van Berkom2017-10-143-0/+69
|
* tests/format/assertion.py: Added tests for the (!) assertion directiveTristan Van Berkom2017-10-115-0/+74
|
* tests/format/optionarch.py: Added arch option specific test casesTristan Van Berkom2017-10-103-0/+97
|
* tests/format/optioneltmask.py: Added element-mask option specific test casesTristan Van Berkom2017-10-108-0/+135
|
* tests/format/optionflags.py: Added flags option specific test casesTristan Van Berkom2017-10-106-0/+180
|
* tests/format/optionenum.py: Added enum option specific test casesTristan Van Berkom2017-10-106-0/+162
|
* tests/format/optionbool.py: Added boolean option specific test casesTristan Van Berkom2017-10-106-0/+146
|
* tests/format/options.py: General tests for project optionsTristan Van Berkom2017-10-1018-0/+365
|
* tests/testutils/runcli.py: Provide the last raised exception in the resultTristan Van Berkom2017-10-102-1/+14
|
* Updated test cases for internal API changes stemming from project optionsTristan Van Berkom2017-10-1012-41/+58
|
* Updating test cases to construct the project/loader properly again.Tristan Van Berkom2017-10-0811-208/+44
| | | | | This had changed when we added project variants and had to split up the loading steps a bit, now all is back to normal without variants.
* Removing variant testsTristan Van Berkom2017-10-0823-545/+0
|
* _yaml.py: Fixing inconsistently named API _yaml.validate_node()Tristan Van Berkom2017-10-011-3/+3
| | | | | | | | | | All of the _yaml APIs which deal with a node (dictionary loaded from YAML) are named _yaml.node_foo(), _yaml.node_bar(), _yaml.node_baz() etc, except for this one glaring exception. Also added a missing internal API documenting comment for _yaml.node_validate() Also updated all callers to _yaml.validate_node() to now call _yaml.node_validate().
* Fix tests for other platformsTristan Maat2017-09-2815-3/+77
|