- 23 May, 2020 1 commit
-
-
Georges Racinet authored
-
- 21 May, 2020 1 commit
-
-
Georges Racinet authored
-
- 19 May, 2020 2 commits
-
-
Georges Racinet authored
First test is about switching from a topic to the real branch, second checks that everything goes fine in a push with plenty of topics and a named branch. --HG-- branch : heptapod-0-12
-
Georges Racinet authored
--HG-- branch : heptapod-0-12
-
- 18 May, 2020 3 commits
-
-
Georges Racinet authored
This reproduces heptapod#260 --HG-- branch : heptapod-0-12
-
Georges Racinet authored
That also will be useful for all tests involving the CI. In most of them we won't care about what the CI configuration says, we'll only need it to exist and be valid. --HG-- branch : heptapod-0-12
-
Georges Racinet authored
This is going to be a very recurring pattern. --HG-- branch : heptapod-0-12
-
- 14 May, 2020 4 commits
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
The scenarios that require a precise value for the hashed storage boolean are very useful, but they can for now only run in Docker context, which is quite late in our development nowadays. So we're adding a scenario that works on whatever the current storage strategy currently is, like we already did for transfers.
-
Georges Racinet authored
Some callers want to pass a system user name, and we have to accept that for uniformity ('git' is been used as meaning "the default user", which is lame but that's another story)
-
- 12 May, 2020 6 commits
-
-
Georges Racinet authored
It will be a long while before Heptapod's web UI can support both Git and Mercurial, but starting to write tests with Git this will be useful to - reach the point where only the UI is lacking and avoid breaking Git support more - better understand some Gitlab aspects by direct comparison with the Git case At this point, HTTP transport for Git is not expected to work at all.
-
Georges Racinet authored
-
Georges Racinet authored
We'll start soon to write basic tests for Git support, currently SSH would be the only transport expected to work.
-
Georges Racinet authored
and there was no assertion for the intermediate GET
-
Georges Racinet authored
previously we didn't test on empty repositories (could have been broken by changes in Heptapod 0.13), nor did we test errors such as re-creation attempt.
-
Georges Racinet authored
These will be useful in `test_repo_files`, but also in many places, notably if VCS independence is seeked.
-
- 11 May, 2020 1 commit
-
-
Georges Racinet authored
More inspection of the behaviour in the Git case indicate that going through the creation endpoint again for an update is incorrect. The proper verb for update is PUT, but the URL is the same one, which is a bit surprising for the creation. --HG-- branch : heptapod-0-12
-
- 07 May, 2020 5 commits
-
-
Georges Racinet authored
As we suspected, but didn't have time to test before release, heptapod#215 seems to be fixed in version 0.12.3. --HG-- branch : heptapod-0-12
-
Georges Racinet authored
At this stage of Heptapod, the API returns Git SHAs, so we have to use it again to get the details. Usually our tests are made so that a commit can be identified by its message (`'title'` key of the returned dict) --HG-- branch : heptapod-0-12
-
Georges Racinet authored
As we suspected, but did not have time to test, this confirms that heptapod#261 is fixed in Heptapod 0.12.3 --HG-- branch : heptapod-0-12
-
Georges Racinet authored
We'll have several tests using two linear topics on top of each other. --HG-- branch : heptapod-0-12
-
Georges Racinet authored
The docstring was actually for an earlier attempt where the first topic got to be rebased. That was more akin to `test_mergerquest_stacked_amend_publish_first()` --HG-- branch : heptapod-0-12
-
- 06 May, 2020 2 commits
-
-
Georges Racinet authored
--HG-- branch : heptapod-0-12
-
Georges Racinet authored
Since this relies on the client having hg-evolve 9.3.1, we mark it explicitely in the CI configuration. --HG-- branch : heptapod-0-12
-
- 01 May, 2020 6 commits
-
-
Georges Racinet authored
In a typicall MR situation (from a topic), the length run that is expected to fail is replaced by a short explanation and a failure. People are expected to relaunch manually once the Docker image is ready and only then, to merge.
-
Georges Racinet authored
The intermediate images are now called `testing` with `latest` being the latest *released* version.
-
Georges Racinet authored
we've had enough startup problems that we didn't look at this obvious until now.
-
Georges Racinet authored
This is the reproduction of heptapod#145. In truth, we should parametrize the fast forward as we did in anouther topic (no, de facto and required) --HG-- branch : heptapod-0-12
-
Georges Racinet authored
This demonstrates in particular our modification to GitLab's JobRequest API: `hgsha` and `repo_type` (in truth the latter conflicts semantically with GitLab's RepoType, which is `project` or `wiki`, and we should rename it to `vcs_type` at some point) --HG-- branch : heptapod-0-12
-
Georges Racinet authored
This will be the main facility for CI functional tests, see #7. --HG-- branch : heptapod-0-12
-
- 03 May, 2020 1 commit
-
-
Georges Racinet authored
The current heptapod:testing image is a preliminary Heptapod 0.13 version. The CI will have to run against the 0-12-testing image. --HG-- branch : heptapod-0-12
-
- 01 May, 2020 1 commit
-
-
Georges Racinet authored
For objects that are relative to different type of GitLab objects, such as Runners, it would be convenient to access the Heptapod instance uniformly.
-
- 29 Apr, 2020 3 commits
-
-
Georges Racinet authored
this time we parametrize our three fast-forward cases in a single test method
-
Georges Racinet authored
for example, will be used for squash params
-
Georges Racinet authored
- the link should be to create a MR for the natural target branch - the prompt should not fail if the natural target named branch doesn't exist – no prompt in that case
-
- 28 Apr, 2020 4 commits
-
-
Georges Racinet authored
Before that, we only tested that the actions were displayed, not that they worked. Also, this is with the default group selected in the "New project" page.
-
Georges Racinet authored
Amazing that it didn't exist before.
-
Georges Racinet authored
This one assumes the webdriver is already on the "New project" page. It will save time in some tests, and also does not require a permanent user (ie registered to the `Heptapod` instance) and can work with a fixture such as `external_user`
-
Georges Racinet authored
This is the counterpart of the fix for #256, we still musn't display that link if the external user has no group
-