Test

build(deps-dev): bump typescript-eslint from 8.14.0 to 8.15.0 #2870

Sign in to view logs

GitHub Actions / Test Results failed Nov 19, 2024 in 0s

1 fail, 2 pass in 2m 11s

8 files 8 suites 2m 11s ⏱️
3 tests 2 ✅ 0 💤 1 ❌
14 runs 12 ✅ 0 💤 2 ❌

Results for commit 0abb4d5.

Annotations

Check warning on line 0 in Account Lockout (Throttling)

github-actions / Test Results

All 2 runs failed: User account gets locked out after multiple failed login attempts (Account Lockout (Throttling))

test-results/test-results-quarkus-node(18)-java(17)-firefox/cucumber-reports/Cucumber.xml [took 42s]
test-results/test-results-quarkus-node(18)-java(21)-firefox/cucumber-reports/Cucumber.xml [took 23s]

Raw output


            Element should be clickable: interactable and enabled {.pf-v5-c-modal-box/footer button.pf-m-primary}
Element: '<button aria-disabled="true" class="pf-v5-c-button pf-m-primary pf-m-disabled" data-ouia-component-id="OUIA-Generated-Button-primary-4" data-ouia-component-type="PF5/Button" data-ouia-safe="true" disabled type="button">Log in</button>'
Actual value: disabled
Screenshot: file:/hawtio-test-suite/tests/hawtio-test-suite/build/reports/tests/1731974760378.7.png
Page source: file:/hawtio-test-suite/tests/hawtio-test-suite/build/reports/tests/1731974760378.7.html
Timeout: 20 s.
	at com.codeborne.selenide.impl.WebElementSource.handleError(WebElementSource.java:147)
	at com.codeborne.selenide.impl.WebElementSource.checkConditionAndReturnElement(WebElementSource.java:125)
	at com.codeborne.selenide.impl.WebElementSource.findAndAssertElementIsClickable(WebElementSource.java:171)
	at com.codeborne.selenide.commands.Click.findElement(Click.java:50)
	at com.codeborne.selenide.commands.Click.execute(Click.java:31)
	at com.codeborne.selenide.commands.Click.execute(Click.java:23)
	at com.codeborne.selenide.commands.Commands.execute(Commands.java:162)
	at com.codeborne.selenide.impl.SelenideElementProxy.dispatchAndRetry(SelenideElementProxy.java:132)
	at com.codeborne.selenide.impl.SelenideElementProxy.invoke(SelenideElementProxy.java:84)
	at jdk.proxy2/jdk.proxy2.$Proxy32.click(Unknown Source)
	at io.hawt.tests.features.pageobjects.pages.ConnectPage.login(ConnectPage.java:79)
	at io.hawt.tests.features.setup.LoginLogout.login(LoginLogout.java:47)
	at io.hawt.tests.features.hooks.LoginLogoutHooks.before(LoginLogoutHooks.java:22)

Given User is on Login page.................................................skipped
When the user attempts to log in with incorrect credentials 5 times.........skipped
Then the user should see a message indicating account lockout for 1 second..skipped
When the user attempts to log in with incorrect credentials 2 times.........skipped
Then the user should see a message indicating account lockout for 3 seconds.skipped

Check notice on line 0 in .github

github-actions / Test Results

3 tests found

There are 3 tests, see "Raw output" for the full list of tests.

Raw output


            Account Lockout (Throttling) ‑ User account gets locked out after multiple failed login attempts
Checking the functionality of a Camel Specific Component page. ‑ Check that the Attributes table under Attribute tab on Camel Specific Component page is not empty - Attributes and values - #1.1
Checking the functionality of a Camel Specific Component page. ‑ Check that the Attributes table under Attribute tab on Camel Specific Component page is not empty - Attributes and values - #1.2

View more details on GitHub Actions