chore(deps): bump @testing-library/jest-dom from 6.1.2 to 6.1.3 #325
This check has been archived and is scheduled for deletion.
Learn more about checks retention
GitHub Actions / Test Results
failed
Sep 9, 2023 in 0s
3 fail, 5 skipped, 48 pass in 52m 53s
Annotations
Check warning on line 0 in Checking the functionality of a Camel Specific Component page.
github-actions / Test Results
2 out of 8 runs failed: Check that the Attributes table under Attribute tab on Camel Specific Component page is not empty - Attributes and values - Example #1.1 (Checking the functionality of a Camel Specific Component page.)
test-results/results-springboot-node(18)-java(11)-firefox/Cucumber.xml [took 40s]
test-results/results-springboot-node(18)-java(17)-firefox/Cucumber.xml [took 39s]
Raw output
Expected condition failed: waiting for number of open windows to be 2 (tried for 20 second(s) with 200 milliseconds interval) Build info: version: '4.10.0', revision: 'c14d967899' System info: os.name: 'Linux', os.arch: 'amd64', os.version: '5.15.0-1041-azure', java.version: '11.0.20.1' Driver info: driver.version: unknown
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for number of open windows to be 2 (tried for 20 second(s) with 200 milliseconds interval)
Build info: version: '4.10.0', revision: 'c14d967899'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '5.15.0-1041-azure', java.version: '11.0.20.1'
Driver info: driver.version: unknown
at org.openqa.selenium.support.ui.FluentWait.timeoutException(FluentWait.java:262)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:230)
at io.hawt.tests.features.pageobjects.pages.ConnectPage.connectTo(ConnectPage.java:71)
at io.hawt.tests.features.setup.LoginLogout.login(LoginLogout.java:41)
at io.hawt.tests.features.hooks.LoginLogoutHooks.before(LoginLogoutHooks.java:31)
Given User is on "Camel" page...............................................skipped
And User is on Camel "mock" item of "components" folder of "SampleCamel" context.skipped
When User clicks on Camel "Attributes" tab..................................skipped
Then Camel table "Attribute" column is not empty............................skipped
And Camel table has "ComponentName" key and "mock" value....................skipped
Check warning on line 0 in Checking the functionality of a specific camel context page.
github-actions / Test Results
1 out of 8 runs failed: Check to view and edit chart of Specific Context (Checking the functionality of a specific camel context page.)
test-results/results-quarkus-node(18)-java(17)-firefox/Cucumber.xml [took 34s]
Raw output
Element should be enabled {By.xpath: //button[@aria-label='Remove selected']}
Element: '<button aria-disabled="true" aria-label="Remove selected" class="pf-c-button pf-m-plain pf-m-disabled" data-ouia-component-id="OUIA-Generated-Button-plain-30" data-ouia-component-type="PF4/Button" data-ouia-safe="true" disabled tabindex="-1" type="button"></button>'
Actual value: disabled
Screenshot: file:/hawtio-test-suite/tests/hawtio-test-suite/build/reports/tests/1694252512011.0.png
Page source: file:/hawtio-test-suite/tests/hawtio-test-suite/build/reports/tests/1694252512011.0.html
Timeout: 20 s.
at com.codeborne.selenide.impl.WebElementSource.handleError(WebElementSource.java:149)
at com.codeborne.selenide.impl.WebElementSource.checkConditionAndReturnElement(WebElementSource.java:127)
at com.codeborne.selenide.impl.WebElementSource.checkCondition(WebElementSource.java:104)
at com.codeborne.selenide.commands.Should.execute(Should.java:30)
at com.codeborne.selenide.commands.Should.execute(Should.java:14)
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 com.sun.proxy.$Proxy24.shouldBe(Unknown Source)
at io.hawt.tests.features.pageobjects.fragments.camel.tabs.common.CamelChart.watch(CamelChart.java:63)
at io.hawt.tests.features.stepdefinitions.camel.CamelChartStepDefs.userWatchesAnAttribute(CamelChartStepDefs.java:32)
at ✽.User watches "TotalRoutes" attribute(classpath:io/hawt/tests/features//camel/contexts/camel_specific_context.feature:47)
Given User is on "Camel" page...............................................passed
And User is on Camel "SampleCamel" context..................................passed
When User clicks on Camel "Chart" tab.......................................passed
And User switches to Edit watches mode of Camel Chart.......................passed
And User unwatch all "SampleCamel" attributes...............................passed
And User watches "TotalRoutes" attribute....................................failed
And User closes Edit watches mode of Camel Chart............................skipped
Then Camel Attribute "SampleCamel TotalRoutes" and its value "2" are displayed in Camel Chart.skipped
And Camel Attribute "SampleCamel ExchangesFailed" is not displayed in Camel Chart.skipped
Check warning on line 0 in Checking the functionality of Camel Specific Route page.
github-actions / Test Results
1 out of 8 runs failed: Check to view and edit chart of Specific Context (Checking the functionality of Camel Specific Route page.)
test-results/results-springboot-node(18)-java(11)-firefox/Cucumber.xml [took 34s]
Raw output
Element should be enabled {By.xpath: //button[@aria-label='Remove selected']}
Element: '<button aria-disabled="true" aria-label="Remove selected" class="pf-c-button pf-m-plain pf-m-disabled" data-ouia-component-id="OUIA-Generated-Button-plain-30" data-ouia-component-type="PF4/Button" data-ouia-safe="true" disabled tabindex="-1" type="button"></button>'
Actual value: disabled
Screenshot: file:/hawtio-test-suite/tests/hawtio-test-suite/build/reports/tests/1694252720850.0.png
Page source: file:/hawtio-test-suite/tests/hawtio-test-suite/build/reports/tests/1694252720850.0.html
Timeout: 20 s.
at com.codeborne.selenide.impl.WebElementSource.handleError(WebElementSource.java:149)
at com.codeborne.selenide.impl.WebElementSource.checkConditionAndReturnElement(WebElementSource.java:127)
at com.codeborne.selenide.impl.WebElementSource.checkCondition(WebElementSource.java:104)
at com.codeborne.selenide.commands.Should.execute(Should.java:30)
at com.codeborne.selenide.commands.Should.execute(Should.java:14)
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 com.sun.proxy.$Proxy24.shouldBe(Unknown Source)
at io.hawt.tests.features.pageobjects.fragments.camel.tabs.common.CamelChart.watch(CamelChart.java:63)
at io.hawt.tests.features.stepdefinitions.camel.CamelChartStepDefs.userWatchesAnAttribute(CamelChartStepDefs.java:32)
at ✽.User watches "MaxProcessingTime" attribute(classpath:io/hawt/tests/features//camel/routes/camel_specific_route.feature:42)
Given User is on "Camel" page...............................................passed
And User is on Camel "simple" item of "routes" folder of "SampleCamel" context.passed
When User clicks on Camel "Operations" tab..................................passed
And User executes operation with name "getMaxProcessingTime()"..............passed
And The result of the "getMaxProcessingTime()" operation is stored..........passed
And User clicks on Camel "Chart" tab........................................passed
And User switches to Edit watches mode of Camel Chart.......................passed
And User unwatch all "simple" attributes....................................passed
And User watches "MaxProcessingTime" attribute..............................failed
And User closes Edit watches mode of Camel Chart............................skipped
Then Camel Attribute "simple MaxProcessingTime" has the same value as stored one.skipped
And Camel Attribute "simple UptimeMillis" is not displayed in Camel Chart...skipped
Check notice on line 0 in .github
github-actions / Test Results
5 skipped tests found
There are 5 skipped tests, see "Raw output" for the full list of skipped tests.
Raw output
Check whether all data is presented and displayed correctly in About modal window. ‑ Check that the titles are presented in Quarkus About modal window - Names of Hawtio's Components - Example #1.1
Check whether all data is presented and displayed correctly in About modal window. ‑ Check that the titles are presented in Quarkus About modal window - Names of Hawtio's Components - Example #1.2
Check whether all data is presented and displayed correctly in About modal window. ‑ Check that the titles are presented in Spring Boot About modal window - Names of Hawtio's Components - Example #1.1
Check whether all data is presented and displayed correctly in About modal window. ‑ Check that the titles are presented in Spring Boot About modal window - Names of Hawtio's Components - Example #1.2
Checking the functionality of Plugin page. ‑ Check that Sample Plugin got installed and accessible
Check notice on line 0 in .github
github-actions / Test Results
56 tests found
There are 56 tests, see "Raw output" for the full list of tests.
Raw output
Check whether all data is presented and displayed correctly in About modal window. ‑ Check that the titles are presented in Quarkus About modal window - Names of Hawtio's Components - Example #1.1
Check whether all data is presented and displayed correctly in About modal window. ‑ Check that the titles are presented in Quarkus About modal window - Names of Hawtio's Components - Example #1.2
Check whether all data is presented and displayed correctly in About modal window. ‑ Check that the titles are presented in Spring Boot About modal window - Names of Hawtio's Components - Example #1.1
Check whether all data is presented and displayed correctly in About modal window. ‑ Check that the titles are presented in Spring Boot About modal window - Names of Hawtio's Components - Example #1.2
Checking the changes of states after performing some operation on Camel Contexts page. ‑ Check the operations on Camel Context - Context actions and states - Example #1.1
Checking the changes of states after performing some operation on Camel Contexts page. ‑ Check the operations on Camel Context - Context actions and states - Example #1.2
Checking the functionality of Camel Endpoints page. ‑ Check that Endpoints table on Camel Endpoints page is not empty - Columns - Example #1.1
Checking the functionality of Camel Endpoints page. ‑ Check that Endpoints table on Camel Endpoints page is not empty - Columns - Example #1.2
Checking the functionality of Camel Endpoints page. ‑ Check to add an Endpoint from Data
Checking the functionality of Camel Endpoints page. ‑ Check to add an Endpoint from URI
Checking the functionality of Camel Routes page. ‑ Check that Camel Routes diagram is presented
Checking the functionality of Camel Routes page. ‑ Check that Camel Source is not empty
Checking the functionality of Camel Routes page. ‑ Check that Routes table on Camel Routes page is not empty - Columns - Example #1.1
Checking the functionality of Camel Routes page. ‑ Check that Routes table on Camel Routes page is not empty - Columns - Example #1.2
Checking the functionality of Camel Routes page. ‑ Check the delete operation on Camel route
Checking the functionality of Camel Routes page. ‑ Check the operations on Camel Routes page - Routes actions and states - Example #1.1
Checking the functionality of Camel Routes page. ‑ Check the operations on Camel Routes page - Routes actions and states - Example #1.2
Checking the functionality of Camel Specific Route page. ‑ Check specific endpoint attribute's detail information
Checking the functionality of Camel Specific Route page. ‑ Check that Camel Route diagram is presented
Checking the functionality of Camel Specific Route page. ‑ Check that Camel Route diagram is presented - Attributes and values - Example #1.1
Checking the functionality of Camel Specific Route page. ‑ Check that Camel Route diagram is presented - Attributes and values - Example #1.2
Checking the functionality of Camel Specific Route page. ‑ Check that Camel Source is not empty
Checking the functionality of Camel Specific Route page. ‑ Check to add a breakpoint while debugging
Checking the functionality of Camel Specific Route page. ‑ Check to execute operation of Specific Endpoint
Checking the functionality of Camel Specific Route page. ‑ Check to remove a breakpoint while debugging
Checking the functionality of Camel Specific Route page. ‑ Check to start the debugging
Checking the functionality of Camel Specific Route page. ‑ Check to stop the debugging
Checking the functionality of Camel Specific Route page. ‑ Check to view and edit chart of Specific Context
Checking the functionality of Help page. ‑ Check that the tabs contain data - Standard Help page tabs - Example #1.1
Checking the functionality of Help page. ‑ Check that the tabs contain data - Standard Help page tabs - Example #1.2
Checking the functionality of Help page. ‑ Check that the tabs contain data - Standard Help page tabs - Example #1.3
Checking the functionality of Help page. ‑ Check that the tabs contain data - Standard Help page tabs - Example #1.4
Checking the functionality of Help page. ‑ Check that the tabs contain data - Standard Help page tabs - Example #1.5
Checking the functionality of Help page. ‑ Check that the titles are presented - Link texts and URLs - Example #1.1
Checking the functionality of Help page. ‑ Check that the titles are presented - Link texts and URLs - Example #1.2
Checking the functionality of Help page. ‑ Check that the titles are presented - Link texts and URLs - Example #1.3
Checking the functionality of Plugin page. ‑ Check that Sample Plugin got installed and accessible
Checking the functionality of a Camel Specific Component page. ‑ Check specific endpoint attribute's detail information
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 - Example #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 - Example #1.2
Checking the functionality of a Camel Specific Component page. ‑ Check to execute operation of Specific Endpoint
Checking the functionality of a Camel Specific Endpoint page. ‑ Check details of the message
Checking the functionality of a Camel Specific Endpoint page. ‑ Check forwarding the message
Checking the functionality of a Camel Specific Endpoint page. ‑ Check sending a message
Checking the functionality of a Camel Specific Endpoint page. ‑ Check specific endpoint attribute's detail information
Checking the functionality of a Camel Specific Endpoint page. ‑ Check that the Attributes table under Attribute tab on Camel Specific Endpoint page is not empty - Attributes and values - Example #1.1
Checking the functionality of a Camel Specific Endpoint page. ‑ Check that the Attributes table under Attribute tab on Camel Specific Endpoint page is not empty - Attributes and values - Example #1.2
Checking the functionality of a Camel Specific Endpoint page. ‑ Check to execute operation of Specific Endpoint
Checking the functionality of a specific camel context page. ‑ Check that table of Attribute tab in Camel Specific Context page is not empty - Attributes and values - Example #1.1
Checking the functionality of a specific camel context page. ‑ Check that table of Attribute tab in Camel Specific Context page is not empty - Attributes and values - Example #1.2
Checking the functionality of a specific camel context page. ‑ Check the start action with Camel Specific Context.
Checking the functionality of a specific camel context page. ‑ Check the suspend action with Camel Specific Context.
Checking the functionality of a specific camel context page. ‑ Check to execute operation of Specific Context and returned result of Integer type
Checking the functionality of a specific camel context page. ‑ Check to execute operation of Specific Context and returned result of String type
Checking the functionality of a specific camel context page. ‑ Check to execute operation of Specific Context and returned result of boolean type
Checking the functionality of a specific camel context page. ‑ Check to view and edit chart of Specific Context
Loading