dependabot[bot] on maven
Bump gson from 2.8.4 to 2.8.9 … (compare)
wakaleo on master
Added some unit tests (compare)
wakaleo on master
Enhanced the Upload task (compare)
Hi, I'm having an issue with that an important line is missing in the Serenity when an exception occurs:
In the Azure DevOps pipeline output I have:
[31morg.springframework.dao.EmptyResultDataAccessException: Incorrect result size: expected 1, actual 0
at org.springframework.dao.support.DataAccessUtils.nullableSingleResult(DataAccessUtils.java:97)
at org.springframework.jdbc.core.namedparam.NamedParameterJdbcTemplate.queryForObject(NamedParameterJdbcTemplate.java:244)
at org.springframework.jdbc.core.namedparam.NamedParameterJdbcTemplate.queryForObject(NamedParameterJdbcTemplate.java:260)
But in the Serenity report the first line (most meaningful) is missing:
org.springframework.dao.support.DataAccessUtils.nullableSingleResult(DataAccessUtils.java:97)
org.springframework.jdbc.core.namedparam.NamedParameterJdbcTemplate.queryForObject(NamedParameterJdbcTemplate.java:244)
org.springframework.jdbc.core.namedparam.NamedParameterJdbcTemplate.queryForObject(NamedParameterJdbcTemplate.java:260)
I have barely any configuration for Serenity, so I don't know why this line is missing.
Hello everyone. I have started to include manual test cases in my serenity reports using @Manual and @Manual:Passed. I have 24 test cases (22 automated and 2 manuals) but the serenity report is showing 17 automated and 7 manual (the 2 manual plus 5 automated). Any idea what is happening? This is the feature file containing the manual definitions:
Feature: SATK-2885 Out of the box workflows
@SATK-2885
@SATK-2885-Scenario1
@Workflows
Scenario: Scenario1 - Check out of the box workflows options
Given Mike logins into Spotfire as sdk
When Mike opens analysis PerkinElmer Signals Apps in SATK
Then Mike should see that 'InVivo_test_IP,Basic Screening Workflow' workflows exist
When Mike selects the 'InVivo_test_IP' workflow
Then Mike should see that 'Run' button is enabled
And Mike should see that 'Edit' button not exist
And Mike should see that the workflow owner is 'Unknown'
When Mike selects the 'Basic Screening Workflow' workflow
Then Mike should see that 'Run' button is enabled
And Mike should see that 'Edit' button not exist
And Mike should see that the workflow owner is 'Unknown'
When Mike clones 'Basic Screening Workflow' workflow in 60 seconds with
|Workflow Name|
|SATK-2885|
Then Mike should see that 'Run' button is enabled
And Mike should see that 'Edit' button exist
And Mike should see that the workflow owner is 'sdk'
And Mike deletes the saved workflow
@SATK-2885
@SATK-2885-Scenario2
@Workflows
@Manual
@Manual:Passed
Scenario: Scenario2 - Check out of the box workflows options offline
Given Mike open Spotfire client in offline mode
When Mike opens analysis PerkinElmer Signals Apps in SATK
Then Mike should see that 'InVivo_test_IP,Basic Screening Workflow' workflows exist
When Mike selects the 'InVivo-test-IP' workflow
Then Mike should see that 'Run' button is enabled
And Mike should see that 'Edit' button not exist
And Mike should see that the workflow owner is 'Unknown'
When Mike selects the 'Basic Screening Workflow' workflow
Then Mike should see that 'Run' button is enabled
And Mike should see that 'Edit' button not exist
And Mike should see that the workflow owner is 'Unknown'
When Mike clones 'Basic Screening Workflow' workflow in 60 seconds with
|Workflow Name|
|SATK-2885|
Then Mike should see that appears the message 'Sorry, you cannot clone a workflow whilst offline'
@SATK-2885
@SATK-2885-Scenario3
@Workflows
@Manual
@Manual:Passed
Scenario: Scenario3 - Check out of the box workflows without workflow folder defined
Given Mike logins into Spotfire as admin
And Mike sets to empty the Protocol Library Folder for the SDK group
And Mike logs out from Spotfire
When Mike logins into Spotfire as sdk
And Mike opens analysis PerkinElmer Signals Apps in SATK
Then Mike should see that appears the warning 'Workflows folder preference is empty, only out of the box workflows will be available.'
And Mike should see that 'InVivo_test_IP,Basic Screening Workflow' workflows exist
While running the test in Azure build pipeline in headless mode,
all UI tests are failing with below error..
What could be the possible reason.. locally it runs fine..
The following error occurred: unknown error: session deleted because of page crash
from unknown error: cannot determine loading status
from tab crashed
(Session info: headless chrome=101.0.4951.54)
gradle-wrapper.properties
across serenity-core, with versions as disparate as old: 4.9, 3.5, 2.10
Under the root dir, even a gradle init fails:
$ ./gradlew init
Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain
Caused by: java.lang.ClassNotFoundException: org.gradle.wrapper.GradleWrapperMain
I'm using a pretty recent jvm (almost sure incompatible, but there is no serenity doc regarding required jvm):
$ java -version
openjdk version "17.0.2" 2022-01-18
@wakaleo https://github.com/serenity-bdd/serenity-core/releases Unable to find latest release notes for 3.2.5.
We only do release notes for major or important releases.
After @wakaleo 's comment to one PR addressing the gradle build https://github.com/serenity-bdd/serenity-core/pull/2816#issuecomment-1122712720
serenity-core no longer uses the Gradle build, so it is not maintained - will probably be deleted at some point.
, I wonder if there is any gain in keeping the gradle files yet... What would be lost, if we delete them right now?
I'm raising the question because I'm still stuck with one issue using the serenity-gradle-plugin that I'm trying to debug. For this, I have invested some effort bringing the gradle build aligned with the maven build, but it apparently needs even more dedication. Devoting more efforts into it doesn't seem sensible though, as the plan is to delete the gradle build.
when running selenium grid on pipelines(azure) do we need to change this URL "http://localhost:4444" as of now i am getting error when the serenity-bdd tests are run
Getting below error
Could not instantiate class org.openqa.selenium.remote.RemoteWebDriver
Tests when run for firefox for selenium grid stucks after browser is open. Works well with chrome.. using this configuration
webdriver {
driver = remote
remote {
url="http://localhost:4444"
driver=firefox
}
}
below is the error,, can someone please help with this
11:55:30.333 INFO [ProxyNodeWebsockets.createWsEndPoint] - Establishing connection to ws://localhost:59603/devtools/browser/df0dd2ea-3f50-476d-b9ca-addbdb736a6c
JavaScript error: chrome://remote/content/server/WebSocketHandshake.jsm, line 182: Error: The handshake request has incorrect Origin header http://localhost:59603
11:55:30.338 WARN [ProxyNodeWebsockets$ForwardingListener.onError] - Error proxying websocket command
java.io.IOException: Invalid Status code=400 text=Bad Request
at org.asynchttpclient.netty.handler.WebSocketHandler.abort(WebSocketHandler.java:92)
Hi -
I'm trying to use grid version 3.141.59 with appium(with serenity-jbhevae). The issue I'm facing is that it is not routing the request to grid.
request goes directly to appium instance running on localhost:4723 and not to grid running locally localhost:4444
(it runs through grid when we i use custom class/browser -
WebDriver driver = new RemoteWebDriver(new URL("http://127.0.0.1:4444/wd/hub"),cap))
Serenity.property -
webdriver.driver=remote
webdriver.remote.driver=appium
appium.remote.hub=http://127.0.0.1:4444/wd/hub
public class AcceptanceTestSuite extends SerenityStories {
@Managed(uniqueSession = false)
public WebDriver webdriver;
}
I have a problem with waiting for element invisibility:
Step failed
net.thucydides.core.webdriver.exceptions.ElementShouldBeVisibleException: Expected condition failed: waiting for [[ChromeDriver: chrome on WINDOWS (0e9a492f32a53ca564ae1bb46ff04d0d)] -> css selector: [data-test='dashboard-view-button-continue']] to be displayed (tried for 10 second(s) with 100 milliseconds interval)
Driver info: driver.version: unknown
at net.serenitybdd.core.pages.WebElementFacadeImpl.throwShouldBeVisibleErrorWithCauseIfPresent(WebElementFacadeImpl.java:1009)
at net.serenitybdd.core.pages.WebElementFacadeImpl.checkPresenceOfWebElement(WebElementFacadeImpl.java:974)
at net.serenitybdd.core.pages.WebElementFacadeImpl.getValue(WebElementFacadeImpl.java:1053)
at net.serenitybdd.core.pages.WebElementFacadeImpl.valueAttributeSupportedAndDefinedIn(WebElementFacadeImpl.java:1170)
at net.serenitybdd.core.pages.WebElementFacadeImpl.getTextValue(WebElementFacadeImpl.java:1143)
at net.serenitybdd.screenplay.matchers.statematchers.WebElementStateDescription.forElement(WebElementStateDescription.java:9)
at net.serenitybdd.screenplay.matchers.statematchers.IsNotCurrentlyVisibleMatcher.describeMismatchSafely(IsNotCurrentlyVisibleMatcher.java:23)
at net.serenitybdd.screenplay.matchers.statematchers.IsNotCurrentlyVisibleMatcher.describeMismatchSafely(IsNotCurrentlyVisibleMatcher.java:7)
As pasted above, the step fails on ElementShouldBeVisibleException
although the IsNotCurrentlyVisibleMatcher
matcher is used. Isn't it a bug?