Skip to content

Autotests for navbar buttons. #4982

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Conversation

solarday
Copy link
Contributor

No description provided.

@@ -0,0 +1,70 @@
import { test, expect } from '@playwright/test';

test.describe('Navbar buttons', () => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest renaming the test: this part of navigation we call "header".
Also, there is a test in the master branch, api navigation. What do you think about unifying them into one file and calling it header.spec.ts? I would expect to have all the header tests related to it in one place.

});

test('Kotlin logo opens the homepage', async ({ page }) => {
const kotlinLogo = page.locator('.ktl-logo-large-module_link_AOGas');
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The locators should be change to not use classes and especially classes with hashes like "_AOGas". They may change after an update, and we'll be forced to update the tests.
My suggestion: we need to add data-testid for the header elements.

@nikpachoo nikpachoo marked this pull request as draft August 6, 2025 14:16
@nikpachoo
Copy link
Collaborator

@solarday, i changed the status of PR, until we add the data-selectors to the head

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants