mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-12-01 21:54:04 +01:00
5ae2dbcb14
Some checks are pending
Integration tests for the release process / release-simulation (push) Waiting to run
/ release (push) Waiting to run
testing / backend-checks (push) Waiting to run
testing / frontend-checks (push) Waiting to run
testing / test-unit (push) Blocked by required conditions
testing / test-remote-cacher (map[image:docker.io/valkey/valkey:7.2.5-alpine3.19 port:6379]) (push) Blocked by required conditions
testing / test-remote-cacher (map[image:ghcr.io/microsoft/garnet-alpine:1.0.14 port:6379]) (push) Blocked by required conditions
testing / test-remote-cacher (map[image:redis:7.2 port:6379]) (push) Blocked by required conditions
testing / test-remote-cacher (map[image:registry.redict.io/redict:7.3.0-scratch port:6379]) (push) Blocked by required conditions
testing / test-mysql (push) Blocked by required conditions
testing / test-pgsql (push) Blocked by required conditions
testing / test-sqlite (push) Blocked by required conditions
testing / security-check (push) Blocked by required conditions
Now that my colleague just posted a wonderful blog post https://blog.datalad.org/posts/forgejo-runner-podman-deployment/ on forgejo runner, some time I will try to add that damn codespell action to work on CI here ;) meanwhile some typos managed to sneak in and this PR should address them (one change might be functional in a test -- not sure if would cause a fail or not) ### Release notes - [ ] I do not want this change to show in the release notes. - [ ] I want the title to show in the release notes with a link to this pull request. - [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/4857 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Co-authored-by: Yaroslav Halchenko <debian@onerussian.com> Co-committed-by: Yaroslav Halchenko <debian@onerussian.com>
41 lines
1.6 KiB
JavaScript
41 lines
1.6 KiB
JavaScript
// @ts-check
|
|
import {test, expect} from '@playwright/test';
|
|
import {login_user, load_logged_in_context} from './utils_e2e.js';
|
|
|
|
test('Follow actions', async ({browser}, workerInfo) => {
|
|
await login_user(browser, workerInfo, 'user2');
|
|
const context = await load_logged_in_context(browser, workerInfo, 'user2');
|
|
const page = await context.newPage();
|
|
|
|
await page.goto('/user1');
|
|
await page.waitForLoadState('networkidle');
|
|
|
|
// Check if following and then unfollowing works.
|
|
// This checks that the event listeners of
|
|
// the buttons aren't disappearing.
|
|
const followButton = page.locator('.follow');
|
|
await expect(followButton).toContainText('Follow');
|
|
await followButton.click();
|
|
await expect(followButton).toContainText('Unfollow');
|
|
await followButton.click();
|
|
await expect(followButton).toContainText('Follow');
|
|
|
|
// Simple block interaction.
|
|
await expect(page.locator('.block')).toContainText('Block');
|
|
|
|
await page.locator('.block').click();
|
|
await expect(page.locator('#block-user')).toBeVisible();
|
|
await page.locator('#block-user .ok').click();
|
|
await expect(page.locator('.block')).toContainText('Unblock');
|
|
await expect(page.locator('#block-user')).toBeHidden();
|
|
|
|
// Check that following the user yields in a error being shown.
|
|
await followButton.click();
|
|
const flashMessage = page.locator('#flash-message');
|
|
await expect(flashMessage).toBeVisible();
|
|
await expect(flashMessage).toContainText('You cannot follow this user because you have blocked this user or this user has blocked you.');
|
|
|
|
// Unblock interaction.
|
|
await page.locator('.block').click();
|
|
await expect(page.locator('.block')).toContainText('Block');
|
|
});
|