summaryrefslogtreecommitdiff
path: root/tests.branching/edit-works-after-branch-root-was-renamed.script
Commit message (Collapse)AuthorAgeFilesLines
* Fix tests for new `morph edit` syntaxPaul Sherwood2014-06-091-2/+2
|
* Revert "Merge branch 'liw/restore-old-cmds'"Richard Maw2013-08-291-1/+1
| | | | | | | | | | | | | | | This reverts commit 2dc382a2a9ae977b1158002cd2631ec5593959c1, reversing changes made to 89a019af088ff62459699a6efdadf8ac8fe35dd9. We decided to restore the old commands for the release, as we weren't confident the new implementations were correct yet. To gain that confidence we need to use them, so the old versions are no longer available, and the new edit code is used when the edit subcommand is invoked. Doing so also requires the test suite to use the edit command instead of new-edit.
* Use new edit instead of old one in testsLars Wirzenius2013-08-191-1/+1
| | | | | | | The test suite got adapted so it requires the new edit instead of the old one. So use the new edit instead of the old one in the test. This is a kluge, and needs to be reverted after the BR10 release.
* Disable tests broken by "morph edit"Lars Wirzenius2013-08-141-1/+1
| | | | | | | | | | | | | | To the best of my ability to understand the old "morph build" code, these tests fail with this error: Conflicting versions of stratum 'hello-stratum' appear in the build. because of how the old "morph build" code creates temporary build refs, and gets them wrong. I believe the new "morph edit" is correct, but have not been able to find out what the root problem in "morph build" is, because the code is beyond my ability to understand it within two hours. Since I have a deadline for "morph edit", I reluctantly disable these tests, temporarily, rather than back out of all "morph edit" changes.
* Disable test cases (lack of time, may not need feature)Lars Wirzenius2013-08-141-0/+5
| | | | | | | We don't know if we want to support keeping system and stratum morphologies in different git repositories, and adding the support is too much work for this deadline. I'm keeping the tests, but disabling them, in case we want to enable it again.
* Tidy up command testsSam Thursfield2012-11-141-3/+5
| | | | Be consistent about placement of test description, blank lines, etc.
* tests: Use test: URL prefix instead of baserock: throughoutSam Thursfield2012-11-071-2/+2
| | | | | | | | | | Some tests already used test: and in order to be able to share the scripts/setup-3rd-party-strata script they need to all use the same prefix. Using baserock: implies that we are using real code from Baserock, so I picked test: because the tests only ever use mock morphologies and no real code.
* Rework the blackbox tests for bare caches.Daniel Silverstone2012-09-141-1/+2
| | | | | | This reworks the blackbox tests to work with the bare repository caches. For the most part it's slight changes to error messages and tweaks to ignore the repository caches during file listing.
* Rewrite edit command to expect SYSTEM STRATUM [CHUNK] parametersJannis Pohlmann2012-09-041-1/+1
| | | | | | | | | | | | | | | | | Editing no longer requires a repository to be specified, neither does it require a branch. It now starts off from a system morphology that is required to exist in the branch root repository. Relative to this system, "morph edit" realises the repository of a stratum and, optionally, a chunk, creates edit branches named after the system branch, if necessary, and update the references in the system and stratum morphology accordingly. The changes made to any of the repositories in the system branch are not committed. All existing changes are updated to work with this new input syntax for "morph edit".
* Find branch root using the morph.repository option in .git/configJannis Pohlmann2012-09-031-0/+34
This is more flexible than relying on the branch root repository directory to have the original name. The user might rename the branch root directory and we still want to be able to find it. Add a test that this new functionality works.
View Lorry Controller Status