serenity-reportportal-integration issues

Providing properties through Java class rather than .properties file

1

Hi, I would like to know if there is a functionality to set properties like baseUrl, apiKey and others through Java implmentation, rather than .properties file. Can such feature be...

asif-choudhari

wontfix

Test Metrics Count Incorrect in ReportPortal

21

Hi Team, We have a serenity bdd cucumber framework in which we are using ReportPortal v23.1 with below dependency version: Serenity - v3.3.10 Serenity-ReportPortal-Integration - v1.5.7 We are facing problem...

Priyanshu19992002

duplicate

Record data with Serenity.recordReportData().withTitle().andContents();

I'm seeking assistance with recording data into ReportPortal. I've been attempting to use the following steps to record some data into a report, but it doesn't seem to be transferring...

sumanguduru

investigation required

How to merge all scenaries in one feature?

4

I have one feature file. It has a few scenaries. But after running report portal divides feature for scenaries. So, I have a few the same features in the ReportPortal...

i-vasilev

investigation required

Retries are being added as duplicate tests for Serenity 3.1.15 version.

2

Hi, I just updated my serenity version and see that duplicate report publication gets published in report portal for retries. See below screenshot. Let me know, if there is a...

plokeshwar

investigation required

How to emit Log manually?

3

Hi, I'm configuring the Log Preset to send as much logs as possible to RP. But can't find anyway to send the information from Logger (INFO,WARN,...) onto RP as well,...

ntthaibk

feature

Failed serenity test isn't reported as 'FAILED' in ReportPortal

4

HI, I use serenity-reportportal-integration library for sending results of test execution to ReportPortal. I noticed strange behaviour. Run the following trivial test case : @Slf4j @ExtendWith(SerenityJUnit5Extension.class) class TestXXX { @Test...

divannn

serenity bug

waiting for release

Update integration versioning

Let's align integration versioning semantic to the real world things. Currently versioning uses 3 digits semantics x.y.z (e. g. 1.6.2). I propose to keep it as is, but repurpose numbers...

Invictum