loading up the forgejo repo on tangled to test page performance
chore: use dynamic id (#7396)
- Follow up forgejo/forgejo#7378
- See https://codeberg.org/forgejo/forgejo/pulls/7378#issuecomment-3167157
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7396
Reviewed-by: 0ko <0ko@noreply.codeberg.org>
Reviewed-by: Otto <otto@codeberg.org>
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-committed-by: Gusted <postmaster@gusted.xyz>
+2
-2
+2
-2
tests/e2e/repo-migrate.test.e2e.ts
+2
-2
tests/e2e/repo-migrate.test.e2e.ts
···
3
3
// @watch end
4
4
5
5
import {expect} from '@playwright/test';
6
-
import {test, save_visual, test_context} from './utils_e2e.ts';
6
+
import {test, save_visual, test_context, dynamic_id} from './utils_e2e.ts';
7
7
8
8
test.use({user: 'user2'});
9
9
···
38
38
test('Migration Progress Page', async ({page, browser}, workerInfo) => {
39
39
test.skip(workerInfo.project.name === 'Mobile Safari', 'Flaky actionability checks on Mobile Safari');
40
40
41
-
const repoName = `invalidrepo-${globalThis.crypto.randomUUID()}`;
41
+
const repoName = dynamic_id();
42
42
expect((await page.goto(`/user2/${repoName}`))?.status(), 'repo should not exist yet').toBe(404);
43
43
44
44
await page.goto('/repo/migrate?service_type=1');