- Jun 03, 2020
-
-
Georges Racinet authored
All they need are services management and rake capability, previously only available for Docker installations.
-
Georges Racinet authored
The `--heptapod-gdk` option declares the test to be launched in GDK context, leading to the new `GdkHeptapod` class to be instantiated, with the GDK root dir specified with `--heptapod-gdk-root`. The new `needs.services` decorator will allow to declare tests that need services (and rake) management, hence will be satisfied more broadly than the `docker` marker. Notably these tests won't be skipped in GDK context.
-
Georges Racinet authored
Just for readability
-
Georges Racinet authored
The only caller at the time being is its sibling method `apply_hashed_storage_setting()`, that will hence become available for all concrete subclasses that implement `ctl_services()`.
-
Georges Racinet authored
It derives from SourceHeptapod, only adding service management and rake capabilities, hence being able to support backup tests and other tests that require service management.
-
Georges Racinet authored
Instead of just declaring `backup_create()` and `backup_restore()`, we implement them generically, relying on a new set of primitives to be implemented in subclasses: - `ctl_services()`: service management - `RAILS_SERVICES`: class attribute listing the Rails app services (web and background). These will be different in the Docker and GDK cases. - `rake()` - `remove_all_backups()`
-
- Jun 02, 2020
-
-
Georges Racinet authored
Closes #9
-
- May 29, 2020
-
-
Georges Racinet authored
At this stage we only want to prevent unwanted publication. See heptapod#284 for future actual support.
-
- May 27, 2020
-
-
Georges Racinet authored
We simply build up on the test for fast-forward refusal, by performing the rebase after the refusal and proceeding up to the full merge.
-
Georges Racinet authored
It will wait automatically for the rebase to be finished and assert its success. We could later on add options to test bad rebases if we need to.
-
- May 09, 2020
-
-
Georges Racinet authored
This is to reproduce heptapod#243 We also add a counter test that only deploy tokens for the right project are accepted.
-
Georges Racinet authored
The API method won't work for a while, wrote them before noticing the version information in online documentation. So we had to make a lengthy webdriver_create_deploy_token, hoping the page structure won't change too much before we can rely on the API methods.
-
- May 24, 2020
-
-
Georges Racinet authored
Overlooked in merge Backed out changeset b1810ba7eb2b
-
- May 22, 2020
-
-
Georges Racinet authored
This will be necessary for tests about content that's not encoded with the current default encoding. Because of this, the output might not be utf-8 either. For now, just avoiding an error is good enough.
-
- May 23, 2020
-
-
Georges Racinet authored
-
- May 21, 2020
-
-
Georges Racinet authored
-
- May 14, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- May 19, 2020
-
-
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.
-
Georges Racinet authored
-
- May 18, 2020
-
-
Georges Racinet authored
This reproduces heptapod#260
-
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.
-
Georges Racinet authored
This is going to be a very recurring pattern.
-
- May 14, 2020
-
-
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)
-
- May 12, 2020
-
-
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.
-
- May 11, 2020
-
-
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.
-
- May 07, 2020
-
-
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.
-
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)
-
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
-
Georges Racinet authored
We'll have several tests using two linear topics on top of each other.
-
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()`
-
- May 06, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
Since this relies on the client having hg-evolve 9.3.1, we mark it explicitely in the CI configuration.
-
- Apr 23, 2020
-
-
Georges Racinet authored
Problems with stacked topics have been annoying for a long time (see heptapod#43). Here is a slightly different scenario, that shows that with hg-evolve 9.3.1 (see heptapod#242), we don't need to force-push but GitLab is confused.
-