summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAge
* Test suite: Remove refs/remotes/dgit/dgit/sid from pari-extra worktreeIan Jackson2016-09-05
| | | | | | | | This, effectively, simulates a previous fetch of something. Do this in the actual tests instead: in this case, only necessary in fetch-localgitonly. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: examplegit: make "new" branch be 2.xIan Jackson2016-09-05
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: t-commit: honour $majorv for major versionIan Jackson2016-09-05
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: Honour t_dgit_xoptsIan Jackson2016-09-05
| | | | | | No callers. This may come in useful, though, at some point. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: examplegit: Make two pushes to unstableIan Jackson2016-09-05
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: examplegit: Save mirror as part of setupIan Jackson2016-09-05
| | | | | | incoming has nothing in it. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: t-setup-*: Fix lock pathIan Jackson2016-09-05
| | | | | | Needs to be not in a directory which may not exist yet. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: Provide t-setup-* machineryIan Jackson2016-09-05
| | | | | | | | | | | | | | | | | | | | | Setups are, essentially, prefixes to test cases. We arrange to be able to reuse their state (as explicitly recorded in t-setup-done), so that manual runs of the test suite can be faster. We save the tmp base directory (the directory shared by tests), if there is one. That will be used for cacheing of setups. And we save the environment in form we can use xargs and env to restore. We use a conventional with-lock-ex and stamp file pattern for the cache. The IMPORT file (containing shell variables) doubles as the stamp. The setup execution rune is exciting. This mostly results from the fact that we want xargs to pass all the env vars to env, and that xargs cannot be persuaded to append fixed arguments to the arguments read from its input file. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: examplegit setup scriptIan Jackson2016-09-05
| | | | | | | | | | We are going to have `setup' scripts which explain how to set up the preconditions for one or more tests. This is the first one. Right now it runs to completion, generating its deliverables in $tmp, but then crashes due to the as-yet-unimplemented t-setup-done call. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: t-commit: Permit specification of the suite in $3Ian Jackson2016-09-05
| | | | | | | | | This also means that we need to default $2 with ${2:-} since callers want need to pass an empty value for the version, to get the default. No functional change since none of the call sites use this yet. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: t-pushed-good: Support other suitesIan Jackson2016-09-05
| | | | | | | | Honour $2 being the suite codename, defaulting to sid. No functional change, since no-one passes this argument right now. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: t-archive-none: Support multiple suitesIan Jackson2016-09-05
| | | | | | | | | | t-archive-none now honours `suitespecs', which defaults to just `sid:unstable'. No overall functional change since no-one sets suitespecs to a non-default value. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Split brain: Test case: Do pushIan Jackson2016-09-05
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Split brain: TODOsIan Jackson2016-09-05
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Split tags: Push the maintainer view tag, where supportedIan Jackson2016-09-05
| | | | | | | | | | | | | | | | | We introduce a new `maint' possibility in to the dgit-tag-format access cfg list, presence of which indicates that the receiver is content to receive DEP-14-style maintainer-view (ie, non-dgit0 tags. For now, we default this to true. However, repos handled by dgit-repos-server cannot currently cope with this, because: * dgit-repos-server currently tries to be compatible with old dgits which send DEP-14-named dgit tags; * dgit-repos-server doesn't currently permit the creation of `extraneous' (ie, non-dgit) tags and branches. So for Debian, we do not set this flag. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: Canonicalise json output when generating aqIan Jackson2016-08-14
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: run-all: record outputIan Jackson2016-08-14
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: Test pushing with forcing old and new tag formatIan Jackson2016-07-31
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Tag change: Test suite: Introduce $tagpfxIan Jackson2016-07-31
| | | | | | | | | | | | | | Currently this is `test-dummy' (the distro the tests work with). Have checked that after this commit find tests -type f | xargs perl -i~ -pe 's/\$tagpfx/test-dummy/g' puts everything back. (This does not prove I have changed the right set of occurrences, but it does suggest that each actual change is good.) No functional change. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: Print better info on t-ref-same failureIan Jackson2016-07-31
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: Print better info on failuresIan Jackson2016-07-31
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: quilt-gbp: New test (not yet complete)Ian Jackson2016-07-17
| | | | | | | | This test does not yet do all that we want, but it does some things and then exits 0. The current intent for the future is written in prose in the rest of the file.
* Test suite: t-gbp-example-prep: Arrange to be FF from the archiveIan Jackson2016-07-16
| | | | Otherwise pushes will necessarily (spuriously) fail.
* Test suite: unapplied-pq2qc: leave us on the qc/ branchIan Jackson2016-07-16
| | | | | The patch queue branch is not really very useful. Certainly, the build tests will require the patch queue branch.
* Test suite: When sbuild log file missing, make a noteIan Jackson2016-07-16
| | | | | | | This updates "Test suite: When sbuild fails, do not crash", to arrange that in this situation we do leave a message in the $bmlog, where it will be reported (eg) by diff. This makes debugging less confusing in cases where the log is indeed missing.
* Test suite: Provide t-gbp-example-prep [FOLD INTO QUILT-GBP TEST?]Ian Jackson2016-07-16
| | | | | This function is useful for setting up a test case --quilt=gbp working tree and corresponding archive contents, ready for substantive tests.
* Test suite: Move bm-quirk-sbuild-after-act to lib-build-modesIan Jackson2016-07-16
| | | | This will allow other tests to check dgit sbuild.
* Test suite: build-modes: Move sbuild knowledge to libIan Jackson2016-07-16
| | | | | Teach bm-guess-e-source-e-targets about sbuild, so this knowledge can be reused.
* Test suite: build-modes: Move `build-source' knowledge to libIan Jackson2016-07-16
| | | | | Teach bm-guess-e-source-e-targets about dgit build-source, so this knowledge can be reused.
* Test suite: Break out bm-prep-ownpackage-branchesIan Jackson2016-07-16
| | | | | We are going to want to run some build modes tests on other exciting trees.
* Test suite: quilt gbp: Provide example worktree tarballIan Jackson2016-07-16
| | | | | | | This working tree has some patch queues etc. in it, which will be useful for testing --quilt=gbp. Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* Test suite: unapplied-pq2qc: move into lib as a t- subroutineIan Jackson2016-07-16
|
* Test suite: Provide tests/unapplied-pq2qcIan Jackson2016-07-16
| | | | | Utility script for invoking gbp pq. I think I will want to swallow this into a t-* function in tests/lib.
* Provide 3.0 (quilt) patches-unapplied with .gitignore test caseIan Jackson2016-07-16
|
* Test dgit-repos-policy-debian with multiple (identical, as it happens) ↵Ian Jackson2016-07-16
| | | | existing taints.
* Test suite: Provide test for nonexistent --always-split-source-buildIan Jackson2016-07-16
| | | | | | | | | We are going to introduce this option soon. It is not supposed to actually have very much overall effect, although it will replumb the way dgit goes about making the source package. So the tests are just the same as the normal tests only with the additional option.
* Test suite: tartree-edit: document gitfetchinfo-merge in usage messageIan Jackson2016-07-16
|
* Test suite: run-all should use make -kIan Jackson2016-07-03
| | | | | Otherwise one failure causes the tests to be abandoned, which is not usually desirable.
* Test suite: lib t-untar of an edited tartree: do not hardlinkIan Jackson2016-07-03
| | | | | | Some of the tools we use, it turns out, do not update properly: they overwrite in place. This can cause inadvertant changes to a tartree opened for editing.
* Tests: tartree-edit: gitfetchinfo: Better commit messages for dirty tressIan Jackson2016-07-03
|
* Test suite: tartree-edit: gitfetchinfo generates remote/TT-HEADIan Jackson2016-07-03
| | | | Simply HEAD is not displayed by gitk, which is rather a shame.
* Test suite: tartree-edit: gitfetchinfo: Remerge on fetchIan Jackson2016-07-02
| | | | | When we unmerged some old A+B merged refs, make a note to merge them again. This saves the user calling gitfetchinfo-merge again.
* Test suite: tartree-edit: gitfetchinfo: Be a bit more carefulIan Jackson2016-07-02
| | | | | | * Turn on perl warnings * Use strict * When removing old merged refs, insist that we aren't handling A+A
* Test suite: tartree-edit: gitfetchinfo: Unmerge merged refsIan Jackson2016-07-02
| | | | | | | | | | | | The sequence gitfetchinfo-merge A B gitfetchinfo A gitfetchinfo-merge A B might leave inappropriate A+B refs, because nothing would delete them. So, have gitfetchinfo A unmerge any A+B or B+A refs. (This does mean that the user of gitfetchinfo A is now promising that any remotes A+B or B+A were made with gitfetchinfo-merge.)
* Test suite: tartree-edit: gitfetchinfo: Specify commit timestampsIan Jackson2016-07-02
| | | | | | We want the commit timestamps to be predictable (ie, to depend on the source info only), so that we don't show spurious disagreement between two working trees. So, use the timestamp of the HEAD commit.
* Test suite: tartree-edit: Provide facility for comparing sets of git refsIan Jackson2016-07-02
|
* Test suite: tartree-edit: break out git_manip_play (nfc)Ian Jackson2016-07-02
|
* Test suite: Provide `tartree-edit gitfetchinfo'Ian Jackson2016-07-02
| | | | Help with comparing different test case git working tree tarballs.
* Test suite: Test build modes -g and -GIan Jackson2016-07-01
|
* Tests: Use --rm-old-changes in build-mode testsIan Jackson2016-07-01
| | | | | | Soon, we are going to be stricter about detecting ambiguity about which .changes file is intended when different build modes have been used.