Cucumber+Serenity BDD with JIRA Two way Integration #525

Gurunathan5029 · 2016-09-13T06:35:48Z

Hi Liviu Carausu,

I am currently developing my Framework by integrating serenity with my cucumber scenarios and its in enhancement stage. But I am really held back because of following issues.

Issue1:
I am using Serenity with Cucumber and I am successfully able to integrate with JIRA [One Way Integration]. But Two way integration is not working, requirements are getting merged but not updated in JIRA.

Please find the POM, Console log and Property file

Console log.txt
Property File.txt
pom.txt

Groovy File Content :
when 'TO DO', {
'success' should: 'In Progress'
}

when 'IN PROGRESS', {
'success' should: 'DONE'
}

when 'DONE', {
'failure' should: 'TO DO'
}

Feature File
@issue:AMS-2
Scenario: Login
Given I navigate to XXX Login Page
When I provide XXXXame and XXXXord
And I Click on Login button
Then Home Page should be Displayed

@issue:AMS-3
Scenario: XXXXee Creation Form Verification
Given I am in XXX Home Page
When I clcik on XXXXXXes button
And I click on XXXXXyee button
Then Add New XXXXyee form should be displayed

JIRA Configuration:
JIRA Project Name :XXX ,
Issue: XXX-2, XXX-3
Version: Release1

Issue2:
I have installed JIRA in my local with sample project, Report is correctly fetching the reuirements but it doesnt have Automated Test and coverage too. Please find that screen shot below

Thanks,
Guru

cliviu · 2016-09-15T03:14:37Z

hi @Gurunathan5029 , I will take a look at your issue

Gurunathan5029 · 2016-09-16T08:24:29Z

Hi Liviu,

I have attached Groovy File Content as well for your reference. Any update on the issue resolution.

Regards,
Guru

cliviu · 2016-09-16T21:23:01Z

Hi Guru, Please try with the attached pom.xml (or at least extract the significant serenity libraries
pom.xml.zip ,
I hope it will work

Gurunathan5029 · 2016-09-19T13:33:06Z

Hi Cliviu,

Thanks for the file.

Now the JIRA issue comments are updating not the Status. And the Epic and Stories links in the Serenity report is not available now [Merging JIRA Issues with Serenity report is not working].

What might be went wrong , In am trying with different versions of serenity but could not able to achieve what I expect. Please help me out.

Updating Comments:
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - Updating JIRA issue: XXX-2
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - JIRA server: Connection to JIRA instance at http://localhost:8081 with user GXXX
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - Updating comments for issue XXX-2
[pool-1-thread-4] INFO net.serenitybdd.plugins.jira.JiraListener - Updating JIRA issue: XXX-3
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - WIKI Rendering activated: true
[pool-1-thread-4] INFO net.serenitybdd.plugins.jira.JiraListener - JIRA server: Connection to JIRA instance at http://localhost:8081 with user GXXX
[pool-1-thread-4] INFO net.serenitybdd.plugins.jira.JiraListener - Updating comments for issue XXX-3
[pool-1-thread-4] INFO net.serenitybdd.plugins.jira.JiraListener - WIKI Rendering activated: true
[pool-1-thread-1] INFO net.serenitybdd.plugins.jira.JiraListener - Updating JIRA issue: XXX-4
[pool-1-thread-1] INFO net.serenitybdd.plugins.jira.JiraListener - JIRA server: Connection to JIRA instance at http://localhost:8081 with user GXXX
[pool-1-thread-1] INFO net.serenitybdd.plugins.jira.JiraListener - Updating comments for issue XXX-4
[pool-1-thread-1] INFO net.serenitybdd.plugins.jira.JiraListener - WIKI Rendering activated: true
[pool-1-thread-1] INFO net.serenitybdd.plugins.jira.JiraListener - Updating JIRA issue: XXX-3
[pool-1-thread-2] INFO net.serenitybdd.plugins.jira.JiraListener - Updating JIRA issue: XXX-2
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - Updating JIRA issue: XXX-4
[pool-1-thread-1] INFO net.serenitybdd.plugins.jira.JiraListener - JIRA server: Connection to JIRA instance at http://localhost:8081 with user GXXX
[pool-1-thread-2] INFO net.serenitybdd.plugins.jira.JiraListener - JIRA server: Connection to JIRA instance at http://localhost:8081 with user GXXX
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - JIRA server: Connection to JIRA instance at http://localhost:8081 with user GXXX
[pool-1-thread-1] INFO net.serenitybdd.plugins.jira.JiraListener - Updating comments for issue XXX-3
[pool-1-thread-2] INFO net.serenitybdd.plugins.jira.JiraListener - Updating comments for issue XXX-2
[pool-1-thread-1] INFO net.serenitybdd.plugins.jira.JiraListener - WIKI Rendering activated: true
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - Updating comments for issue XXX-4
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - WIKI Rendering activated: true
[pool-1-thread-2] INFO net.serenitybdd.plugins.jira.JiraListener - WIKI Rendering activated: true

Serenity Report Sections:

Regards,
Guru

cliviu · 2016-09-19T21:28:11Z

hi Guru,
Please try this pom.xml
pom.xml.zip

Regarding updating the issues, please be aware that the states from the groovy file are case-sensitive. The states from groovy file should correspond exactly with the ones defined in JIRA.

Gurunathan5029 · 2016-09-20T09:01:27Z

Hi Cliviu,

Thanks a lot for the POM File . Now I can able to see the Stories and Epic in the report.

But the status in JIRA is still not changing. I don't know what I am doing wrong.
Even I have tried with difference cases in groovy file .

JIRA Workflow

Groovy File Content
when 'TO DO', {
'SUCCESS' should: 'IN PROGRESS'
}

when 'IN PROGRESS', {
'SUCCESS' should: 'DONE'
}

when 'DONE', {
'FAILURE' should: 'TO DO'
}

Groovy Location \cucumber-webtests\src\test\resources
Serenity.properties
serenity.jira.workflow.active=true
serenity.jira.workflow=jira-workflow.groovy

Please correct me if anything is wrongly configured or done here.

Regards,
Guru

cliviu · 2016-09-22T04:53:42Z

Hey Guru, everything looks good configured... please try small letters for 'success' , 'failure'

Gurunathan5029 · 2016-09-22T07:25:51Z

Hi liviu,

Nothing benefited by changing the workflow letters in groovy file to 'success'
, 'failure'.

Now the comments are updated successfully without any error but WorkFlow is
not updated.

I am really struck up with this issue for last 5 days, I don't know how to
fix it.

Regards,
Guru

On Thu, Sep 22, 2016 at 10:23 AM, Liviu Carausu notifications@github.com
wrote:

Hey Guru, everything looks good configured... please try small letters for
'success' , 'failure'

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#525 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS_9HKPf1XL26I33UxcuISb6j_aENUlHks5qsgnZgaJpZM4J7VjK
.

cliviu · 2016-09-22T20:29:29Z

hi guru,
please search in the log file for the following lines :
DEBUG n.s.plugins.jira.JiraUpdater - JIRA LISTENER STATUS
....
DEBUG n.s.plugins.jira.JiraUpdater - WORKFLOW ACTIVE:

cliviu · 2016-09-22T20:33:06Z

If you have problems to see the debug messages, add following dependencies to your pom.xml

   <dependency>
        <groupId>ch.qos.logback</groupId>
        <artifactId>logback-classic</artifactId>
        <version>1.1.3</version>
    </dependency>

    <dependency>
        <groupId>ch.qos.logback</groupId>
        <artifactId>logback-core</artifactId>
        <version>1.1.3</version>
    </dependency>

and add the logback.xml in the same directory as your pom.xml
logback.xml.zip

Gurunathan5029 · 2016-09-23T09:30:18Z

Hi Liviu,

I am not getting log file back . Where to find it out and what has to be
mentioned in xml file you shared ,

%-4relative [%thread] %-5level %logger{35} - %msg %n junit.log true %-4r %-5level %logger{35}: %msg%n

Regards,
Guru

On Fri, Sep 23, 2016 at 2:03 AM, Liviu Carausu notifications@github.com
wrote:

If you have problems to see the debug messages, add following dependencies
to your pom.xml

ch.qos.logback
logback-classic
1.1.3
<dependency>
    <groupId>ch.qos.logback</groupId>
    <artifactId>logback-core</artifactId>
    <version>1.1.3</version>
</dependency>
and add the logback.xml in the same directory as your pom.xml
logback.xml.zip
https://github.com/serenity-bdd/serenity-core/files/488305/logback.xml.zip

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#525 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS_9HLAkT4-4Ay2cYuzz8_KIOCp3CuT-ks5qsuYFgaJpZM4J7VjK
.

cliviu · 2016-09-23T11:20:03Z

Hi, normally it should be logged on CONSOLE. Just redirect the output to a file

Gurunathan5029 · 2016-09-23T12:01:30Z

Yes Workflow Active is set as true and listener has the value : upadate,

[INFO] serenity.browser,width=1200
[INFO] serenity.dry.run=false
[INFO] serenity.jira.workflow.active=true
[INFO] serenity.project.name=XXX Automation
[INFO] jira.project=XXX
[INFO] serenity.project.key=AMS
[INFO] serenity.browser,height=1200
[INFO] serenity.take.screenshots=AFTER_EACH_STEP
[INFO] jira.password=Iceman1!
[INFO] serenity.release.types=milestone, release, version
[INFO] serenity.use.unique.browser=false
[INFO] jira.url=http://localhost:8081
[INFO] serenity.public.url=http://localhost:8080/job/XXX-XXX/HTML_Report/
[INFO] webdriver.chrome.driver=C:\chromedriver.exe
[INFO] jira.username=XXXXXX
[INFO] serenity.test.root=net.thucydides.showcase.cucumber.junit
[INFO] webdriver.driver=chrome
[INFO] webdriver.timeouts.implicitlywait=10000
[INFO] serenity.jira.workflow=jira-workflow.groovy

[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - Updating
JIRA issue: XXX-2

On Fri, Sep 23, 2016 at 4:50 PM, Liviu Carausu notifications@github.com
wrote:

Hi, normally it should be logged on CONSOLE. Just redirect the output to a
file

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#525 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS_9HKNS3sey9Nsok0EvO_9D7MGV4K9gks5qs7XmgaJpZM4J7VjK
.

cliviu · 2016-09-23T16:03:39Z

I still do not see the DEBUG channel ... is important to see this line

DEBUG n.s.plugins.jira.JiraUpdater - WORKFLOW ACTIVE:

Gurunathan5029 · 2016-09-26T07:07:12Z

Hi Liviu,

I am not getting the debug logs for,

DEBUG n.s.plugins.jira.JiraUpdater - WORKFLOW ACTIVE:

Please find the below debug channel report I am receiving:

[INFO] serenity.browser,width=1200

[INFO] serenity.dry.run=false

[INFO] serenity.jira.workflow.active=true

[INFO] serenity.project.name=XXX Automation

[INFO] jira.project=XXX

[INFO] serenity.project.key=XXX

[INFO] serenity.browser,height=1200

[INFO] serenity.take.screenshots=AFTER_EACH_STEP

[INFO] jira.password=Iceman1!

[INFO] serenity.release.types=milestone, release, version

[INFO] serenity.use.unique.browser=false

[INFO] jira.url=http://localhost:8081

[INFO] serenity.public.url=http://localhost:8080/job/YYY-XXX/HTML_Report/

[INFO] webdriver.chrome.driver=C:\chromedriver.exe

[INFO] jira.username=XXXXXXXXX

[INFO] serenity.test.root=net.thucydides.showcase.cucumber.junit

[INFO] webdriver.driver=chrome

[INFO] webdriver.timeouts.implicitlywait=10000

[INFO] serenity.jira.workflow=jira-workflow.groovy

[INFO] project.build.directory :
C:\Users\ggunase\Desktop\YYYFrameworkShare-master\YYYFrameworkShare-master\cucumber-webtests

[INFO] project.reporting.OutputDirectory : null

[INFO] OutputDirectory :
C:\Users\ggunase\Desktop\YYYFrameworkShare-master\YYYFrameworkShare-master\cucumber-webtests\target\site\serenity

[INFO] current_project.base.dir:
C:\Users\ggunase\Desktop\YYYFrameworkShare-master\YYYFrameworkShare-master\cucumber-webtests

Generating HTML Story Reports from
C:\Users\ggunase\Desktop\YYYFrameworkShare-master\YYYFrameworkShare-master\cucumber-webtests\target\site\serenity

Generating HTML Story Reports to
C:\Users\ggunase\Desktop\YYYFrameworkShare-master\YYYFrameworkShare-master\cucumber-webtests\target\site\serenity

[INFO] LOADING LOCAL PROPERTIES FROM
C:\Users\ggunase\Desktop\YYYFrameworkShare-master\YYYFrameworkShare-master\cucumber-webtests\serenity.properties

[DEBUG] JIRA URL: http://localhost:8081

[DEBUG] JIRA project: XXX

[DEBUG] JIRA user: XXXXXXXXX

[INFO] project.build.directory :
C:\Users\ggunase\Desktop\YYYFrameworkShare-master\YYYFrameworkShare-master\cucumber-webtests

[INFO] project.reporting.OutputDirectory : null

[INFO] OutputDirectory :
C:\Users\ggunase\Desktop\YYYFrameworkShare-master\YYYFrameworkShare-master\cucumber-webtests\target\site\serenity

[DEBUG] Find parent requirement in JIRA for Login

[DEBUG] Parent found: IssueSummary{key='XXX-2', summary='LoginXXX'}

[DEBUG] Reading requirements from
net.serenitybdd.plugins.jira.requirements.JIRARequirementsProvider@6ac83e67

[DEBUG] Loading root requirements: issuetype = epic and project=XXX

[DEBUG] Count by JQL for issuetype = epic and project=XXX

[DEBUG] Loading root requirements done: 1

[DEBUG] Loading 1 requirements

[DEBUG] Load children for requirement Create XXX XXXXYYYYs After Login

[DEBUG] Loading child requirements for: Create XXX XXXXYYYYs After Login

[DEBUG] Loading child requirements for Create XXX XXXXYYYYs After Login
done: 4

[DEBUG] 4 child requirements loaded in: 42 ms

[DEBUG] Child requirements: [Requirement{name='Login using valid
credentials ', type='Task' parent = 'null', cardNumber='XXX-5'},
Requirement{name='XXXXYYYY Creation With Valid Details ', type='Story'
parent = 'null', cardNumber='XXX-4'}, Requirement{name='XXXXYYYY Creation
Form Verification ', type='Story' parent = 'null', cardNumber='XXX-3'},
Requirement{name='LoginXXX', type='Story' parent = 'null',
cardNumber='XXX-2'}]

[DEBUG] Load children for requirement Create XXX XXXXYYYYs After Login done

[DEBUG] 1 requirements loaded in 44 ms

[DEBUG] Requirements: [Requirement{name='Create XXX XXXXYYYYs After Login',
type='Epic' parent = 'null', cardNumber='XXX-1'}]

[DEBUG] Requirement ancestors for:Requirement{name='Create XXX XXXXYYYYs
After Login', type='Epic' parent = 'null', cardNumber='XXX-1'} =
[Requirement{name='Create XXX XXXXYYYYs After Login', type='Epic' parent =
'null', cardNumber='XXX-1'}]

[DEBUG] Requirement ancestors for:Requirement{name='Login using valid
credentials ', type='Task' parent = 'Create XXX XXXXYYYYs After Login',
cardNumber='XXX-5'} = [Requirement{name='Create XXX XXXXYYYYs After Login',
type='Epic' parent = 'null', cardNumber='XXX-1'}, Requirement{name='Login
using valid credentials ', type='Task' parent = 'Create XXX XXXXYYYYs After
Login', cardNumber='XXX-5'}]

[DEBUG] Requirement ancestors for:Requirement{name='XXXXYYYY Creation With
Valid Details ', type='Story' parent = 'Create XXX XXXXYYYYs After Login',
cardNumber='XXX-4'} = [Requirement{name='Create XXX XXXXYYYYs After Login',
type='Epic' parent = 'null', cardNumber='XXX-1'},
Requirement{name='XXXXYYYY Creation With Valid Details ', type='Story'
parent = 'Create XXX XXXXYYYYs After Login', cardNumber='XXX-4'}]

[DEBUG] Requirement ancestors for:Requirement{name='XXXXYYYY Creation Form
Verification ', type='Story' parent = 'Create XXX XXXXYYYYs After Login',
cardNumber='XXX-3'} = [Requirement{name='Create XXX XXXXYYYYs After Login',
type='Epic' parent = 'null', cardNumber='XXX-1'},
Requirement{name='XXXXYYYY Creation Form Verification ', type='Story'
parent = 'Create XXX XXXXYYYYs After Login', cardNumber='XXX-3'}]

[DEBUG] Requirement ancestors for:Requirement{name='LoginXXX', type='Story'
parent = 'Create XXX XXXXYYYYs After Login', cardNumber='XXX-2'} =
[Requirement{name='Create XXX XXXXYYYYs After Login', type='Epic' parent =
'null', cardNumber='XXX-1'}, Requirement{name='LoginXXX', type='Story'
parent = 'Create XXX XXXXYYYYs After Login', cardNumber='XXX-2'}]

[DEBUG] Requirements found:[Requirement{name='Create XXX XXXXYYYYs After
Login', type='Epic' parent = 'null', cardNumber='XXX-1'}]

[DEBUG] Requirement found for test outcome Login-[XXX-2]:
Optional.of(Requirement{name='LoginXXX', type='Story' parent = 'Create XXX
XXXXYYYYs After Login', cardNumber='XXX-2'})

[DEBUG] Find parent requirement in JIRA for XXXXYYYY Creation Form
Verification

[DEBUG] Parent found: IssueSummary{key='XXX-3', summary='XXXXYYYY Creation
Form Verification '}

[DEBUG] Requirement found for test outcome XXXXYYYY Creation Form
Verification-[XXX-3]: Optional.of(Requirement{name='XXXXYYYY Creation Form
Verification ', type='Story' parent = 'Create XXX XXXXYYYYs After Login',
cardNumber='XXX-3'})

[DEBUG] Find parent requirement in JIRA for Login

[DEBUG] Parent found: IssueSummary{key='XXX-2', summary='LoginXXX'}

[DEBUG] Requirement found for test outcome Login-[XXX-2]:
Optional.of(Requirement{name='LoginXXX', type='Story' parent = 'Create XXX
XXXXYYYYs After Login', cardNumber='XXX-2'})

[DEBUG] Find parent requirement in JIRA for XXXXYYYY Creation With Valid
Details

[DEBUG] Parent found: IssueSummary{key='XXX-4', summary='XXXXYYYY Creation
With Valid Details '}

[DEBUG] Requirement found for test outcome XXXXYYYY Creation With Valid
Details-[XXX-4]: Optional.of(Requirement{name='XXXXYYYY Creation With Valid
Details ', type='Story' parent = 'Create XXX XXXXYYYYs After Login',
cardNumber='XXX-4'})

[DEBUG] Requirement found for test outcome Login-[XXX-2]:
Optional.of(Requirement{name='LoginXXX', type='Story' parent = 'Create XXX
XXXXYYYYs After Login', cardNumber='XXX-2'})

[DEBUG] Requirement found for test outcome XXXXYYYY Creation Form
Verification-[XXX-3]: Optional.of(Requirement{name='XXXXYYYY Creation Form
Verification ', type='Story' parent = 'Create XXX XXXXYYYYs After Login',
cardNumber='XXX-3'})

[DEBUG] Requirement found for test outcome Login-[XXX-2]:
Optional.of(Requirement{name='LoginXXX', type='Story' parent = 'Create XXX
XXXXYYYYs After Login', cardNumber='XXX-2'})

[DEBUG] Requirement found for test outcome XXXXYYYY Creation With Valid
Details-[XXX-4]: Optional.of(Requirement{name='XXXXYYYY Creation With Valid
Details ', type='Story' parent = 'Create XXX XXXXYYYYs After Login',
cardNumber='XXX-4'})

[DEBUG] Merging requirements = [Requirement{name='Create XXX XXXXYYYYs
After Login', type='Epic' parent = 'null', cardNumber='XXX-1'}]

[DEBUG] Merged requirements set = [Requirement{name='Create XXX XXXXYYYYs
After Login', type='Epic' parent = 'null', cardNumber='XXX-1'}]

[DEBUG] Shutting down Test outcome reports generation

[DEBUG] Aggregate reports generated in 722 ms

[DEBUG] Loaded Releases: []

[DEBUG] Requirement found for test outcome Login-[XXX-2]:
Optional.of(Requirement{name='LoginXXX', type='Story' parent = 'Create XXX
XXXXYYYYs After Login', cardNumber='XXX-2'})

[DEBUG] Requirement found for test outcome XXXXYYYY Creation Form
Verification-[XXX-3]: Optional.of(Requirement{name='XXXXYYYY Creation Form
Verification ', type='Story' parent = 'Create XXX XXXXYYYYs After Login',
cardNumber='XXX-3'})

[DEBUG] Requirement found for test outcome Login-[XXX-2]:
Optional.of(Requirement{name='LoginXXX', type='Story' parent = 'Create XXX
XXXXYYYYs After Login', cardNumber='XXX-2'})

[DEBUG] Requirement found for test outcome XXXXYYYY Creation With Valid
Details-[XXX-4]: Optional.of(Requirement{name='XXXXYYYY Creation With Valid
Details ', type='Story' parent = 'Create XXX XXXXYYYYs After Login',
cardNumber='XXX-4'})

[DEBUG] Test outcome reports generated in 1810 ms

On Fri, Sep 23, 2016 at 9:33 PM, Liviu Carausu notifications@github.com
wrote:

I still do not see the DEBUG channel ... is important to see this line

DEBUG n.s.plugins.jira.JiraUpdater - WORKFLOW ACTIVE:

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#525 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS_9HOW7axWBof6Uk7404JR78F6DMC11ks5qs_hegaJpZM4J7VjK
.

cliviu · 2016-09-26T22:41:33Z

I'm really not sure what is wrong with the output.. Do you have the two dependencies in the pom.xml ?

Gurunathan5029 · 2016-09-27T09:42:11Z

yes Liviu, I have in POM.

com.googlecode.lambdaj lambdaj 2.3.3 net.serenity-bdd serenity-jira-plugin 1.1.2-rc.1 org.codehaus.groovy groovy-all 1.8.6 net.serenity-bdd serenity-jira-requirements-provider 1.1.3-rc.1 But I am not seeing what u said. Any other thing has to be corrected like version or some other dependencies.

On Tue, Sep 27, 2016 at 4:11 AM, Liviu Carausu notifications@github.com
wrote:

I'm really not sure what is wrong with the output.. Do you have the two
dependencies in the pom.xml ?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#525 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS_9HFsgaVXI5A8lsM4_O8pfuWTtWhOyks5quEoggaJpZM4J7VjK
.

cliviu · 2016-09-27T10:23:20Z

Hi, I mean the logback

   <dependency>
        <groupId>ch.qos.logback</groupId>
        <artifactId>logback-classic</artifactId>
        <version>1.1.3</version>
    </dependency>

    <dependency>
        <groupId>ch.qos.logback</groupId>
        <artifactId>logback-core</artifactId>
        <version>1.1.3</version>
    </dependency>

In the first log that you have posted you have something like
"INFO net.serenitybdd.plugins.jira.JiraListener - Updating comments for issue "

the log entry DEBUG n.s.plugins.jira.JiraUpdater - JIRA LISTENER STATUS should be actually visible always on DEBUG channel..

Please attach once more your pom, serenity.properties and complete log

Gurunathan5029 · 2016-09-27T11:47:26Z

yes I have both the dependency in place [Core and Classic]

On Tue, Sep 27, 2016 at 3:53 PM, Liviu Carausu notifications@github.com
wrote:

Hi, I mean the logback

ch.qos.logback
logback-classic
1.1.3
<dependency>
    <groupId>ch.qos.logback</groupId>
    <artifactId>logback-core</artifactId>
    <version>1.1.3</version>
</dependency>
In the first log that you have posted you have something like
"INFO net.serenitybdd.plugins.jira.JiraListener - Updating comments for
issue "

the log entry DEBUG n.s.plugins.jira.JiraUpdater - JIRA LISTENER STATUS
should be actually visible always on DEBUG channel..

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#525 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS_9HK72YTf3nY5hR_BBV9wXY_ZkLGboks5quO6agaJpZM4J7VjK
.

Gurunathan5029 · 2016-09-29T08:57:50Z

Any finding on this issue, Liviu, Please have a look at the issue 543[New One] with respect to JIRA integration

cliviu · 2016-09-29T21:55:24Z

hi Guru, I think you should remove the slf4j-simple entry from your pom.xml. Please try again and tell me if you see the output with JIRA LISTENER STATUS

Gurunathan5029 · 2016-09-30T11:30:53Z

Hi Liviu,

Now I am getting following things,

16:51:38.785 [main] DEBUG n.s.plugins.jira.JiraListener - JIRA LISTENER
STATUS
16:51:38.785 [main] DEBUG n.s.plugins.jira.JiraListener - JIRA URL:
http://localhost:8081
16:51:38.785 [main] DEBUG n.s.plugins.jira.JiraListener - REPORT URL:
http://localhost/XXX
16:51:38.785 [main] DEBUG n.s.plugins.jira.JiraListener - WORKFLOW ACTIVE:
true

16:52:36.823 [main] DEBUG n.s.plugins.jira.JiraListener - WORKFLOW
TRANSITIONS: [SUCCESS:[TO DO:[IN PROGRESS], IN PROGRESS:[DONE]],
FAILURE:[DONE:[TO DO]]]

But still the Workflow is not updated.

Thanks,
Guru

On Fri, Sep 30, 2016 at 3:25 AM, Liviu Carausu notifications@github.com
wrote:

hi Guru, I think you should remove the slf4j-simple entry from your
pom.xml. Please try again and tell me if you see the output with JIRA
LISTENER STATUS

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#525 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS_9HO7w8eL_W6OrcpQVLw64P4nnwMxqks5qvDPPgaJpZM4J7VjK
.

Gurunathan5029 · 2016-10-03T12:21:01Z

Any update on this Liviu

cliviu · 2016-10-03T21:46:13Z

actually it should work, you should see some entry like this in your log file file :

Updating status for issue ....

Basically there are two conditions to activate the state workflow :

serenity.jira.workflow.active=true
2)serenity.jira.workflow=jira-workflow.groovy (or any other file) which should be in the classpath (src/test/resources) works for me ....
So I'm really as stucked as you with this problem ...

cliviu · 2016-10-06T20:25:19Z

can you try to set also thucydides.public.url=http://localhost:8080/job/YYY-XXX/HTML_Report/

Gurunathan5029 · 2016-10-11T11:48:56Z

No , Nothing happening in favor Liviu

cliviu · 2016-10-12T22:11:54Z

Guru, the last chance is that I post a test project for you, please adjust the values in the serenity.properties and the issues in the cucumber features to your values, let me know if it helps..
You should see in the log file some entries like "Updating status for issue"
jira-example-guru.zip

Gurunathan5029 · 2016-11-25T09:46:53Z

I have referred the examples Cliviu but I am not seeing any update on the Wrokflows ,

Please see the logs I am getting
TEST PASSED: Build Validation

[main] INFO net.serenitybdd.plugins.jira.JiraListener - Updating JIRA issue: QAAUTO-13
[main] INFO net.serenitybdd.plugins.jira.JiraListener - JIRA server: Connection to JIRA instance at http://corp-jira.XXXXXXXX.com:8080/ with user gguXXXX
[main] INFO net.serenitybdd.plugins.jira.JiraListener - Updating comments for issue QAAUTO-13
[main] INFO net.serenitybdd.plugins.jira.JiraListener - WIKI Rendering activated: true
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - Updating JIRA issue: QAAUTO-13
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - JIRA server: Connection to JIRA instance at http://corp-jira.XXXXXXXXXs.com:8080/ with user ggunaXXX
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - Updating comments for issue QAAUTO-13
[pool-1-thread-3] INFO net.serenitybdd.plugins.jira.JiraListener - WIKI Rendering activated: true

Gurunathan5029 · 2016-12-02T07:30:42Z

Is there any update on this issue

cliviu · 2016-12-04T07:18:56Z

Hi @Gurunathan5029 , with the sample project that I have attached for you you should see the "Updating status for issue" log entry

Gurunathan5029 · 2016-12-15T11:18:50Z

Yes Liviu, I can see the "Updating Status" but why I am not getting that in my project.

…

On Sun, Dec 4, 2016 at 12:48 PM, Liviu Carausu ***@***.***> wrote: Hi @Gurunathan5029 <https://github.com/Gurunathan5029> , with the sample project that I have attached for you you should see the "Updating status for issue" log entry — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#525 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AS_9HADebzXnfXZqxLOmyOAjg_oUhiO8ks5rEmlhgaJpZM4J7VjK> .

cliviu · 2016-12-15T22:33:50Z

Hi, It should be more than Updating Status ... . something like :
"Updating status for issue {issueId} with test result {testResult} ..."
"Issue {issueId} currently has status '{currentStatus}'"
"Found transitions {transitions} for issue {issueId}"

can you please post more output containing the above mentioned lines ?

shankar4a1 · 2020-04-01T14:52:43Z

Hi @cliviu ,
I have a question on serenity-JIRA integration .Could you please help .

I have downloaded "jira-example-guru.zip" and it is working as expected while pulling the requirements from JIRA .I can see below log on the console while it is pulling the requirements .

15:25:37.923 [pool-2-thread-2] DEBUG n.s.p.j.r.JIRARequirementsProvider - Loading root requirements: issuetype = "User Story" and project="DEMO"
15:25:39.633 [pool-2-thread-2] DEBUG n.s.p.jira.client.JerseyJiraClient - Count by JQL for issuetype = "User Story" and project="DEMO"

Question : Is it possible to pass jql query/different serenity properties to retrieve specific requirements example to retrieve user stories which are part of DEMO1.0 release and user stories whihc are tagged as automation in JIRA

issuetype = "User Story" and project="DEMO" and AND fixVersion = "DEMO1.0" AND labels in ("Automation")

Gurunathan5029 mentioned this issue Sep 13, 2016

Updating comments for issue in Jira fails... but Merging requirements works fine. #504

Closed

cliviu mentioned this issue Nov 24, 2016

Serenity With JIRA Integration fails with Error: JIRA query failed: error 500 serenity-bdd/serenity-jira#59

Closed

wakaleo closed this as completed Feb 12, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cucumber+Serenity BDD with JIRA Two way Integration #525

Cucumber+Serenity BDD with JIRA Two way Integration #525

Gurunathan5029 commented Sep 13, 2016 •

edited

cliviu commented Sep 15, 2016

Gurunathan5029 commented Sep 16, 2016

cliviu commented Sep 16, 2016 •

edited

Gurunathan5029 commented Sep 19, 2016

cliviu commented Sep 19, 2016

Gurunathan5029 commented Sep 20, 2016

cliviu commented Sep 22, 2016

Gurunathan5029 commented Sep 22, 2016

cliviu commented Sep 22, 2016

cliviu commented Sep 22, 2016 •

edited

Gurunathan5029 commented Sep 23, 2016

cliviu commented Sep 23, 2016

Gurunathan5029 commented Sep 23, 2016

cliviu commented Sep 23, 2016

Gurunathan5029 commented Sep 26, 2016

cliviu commented Sep 26, 2016

Gurunathan5029 commented Sep 27, 2016

cliviu commented Sep 27, 2016 •

edited

Gurunathan5029 commented Sep 27, 2016

Gurunathan5029 commented Sep 29, 2016

cliviu commented Sep 29, 2016

Gurunathan5029 commented Sep 30, 2016

Gurunathan5029 commented Oct 3, 2016

cliviu commented Oct 3, 2016

cliviu commented Oct 6, 2016

Gurunathan5029 commented Oct 11, 2016

cliviu commented Oct 12, 2016

Gurunathan5029 commented Nov 25, 2016 •

edited

Gurunathan5029 commented Dec 2, 2016

cliviu commented Dec 4, 2016

Gurunathan5029 commented Dec 15, 2016 via email

cliviu commented Dec 15, 2016

shankar4a1 commented Apr 1, 2020

Cucumber+Serenity BDD with JIRA Two way Integration #525

Cucumber+Serenity BDD with JIRA Two way Integration #525

Comments

Gurunathan5029 commented Sep 13, 2016 • edited

cliviu commented Sep 15, 2016

Gurunathan5029 commented Sep 16, 2016

cliviu commented Sep 16, 2016 • edited

Gurunathan5029 commented Sep 19, 2016

cliviu commented Sep 19, 2016

Gurunathan5029 commented Sep 20, 2016

cliviu commented Sep 22, 2016

Gurunathan5029 commented Sep 22, 2016

cliviu commented Sep 22, 2016

cliviu commented Sep 22, 2016 • edited

Gurunathan5029 commented Sep 23, 2016

cliviu commented Sep 23, 2016

Gurunathan5029 commented Sep 23, 2016

cliviu commented Sep 23, 2016

Gurunathan5029 commented Sep 26, 2016

cliviu commented Sep 26, 2016

Gurunathan5029 commented Sep 27, 2016

cliviu commented Sep 27, 2016 • edited

Gurunathan5029 commented Sep 27, 2016

Gurunathan5029 commented Sep 29, 2016

cliviu commented Sep 29, 2016

Gurunathan5029 commented Sep 30, 2016

Gurunathan5029 commented Oct 3, 2016

cliviu commented Oct 3, 2016

cliviu commented Oct 6, 2016

Gurunathan5029 commented Oct 11, 2016

cliviu commented Oct 12, 2016

Gurunathan5029 commented Nov 25, 2016 • edited

Please see the logs I am getting TEST PASSED: Build Validation

Gurunathan5029 commented Dec 2, 2016

cliviu commented Dec 4, 2016

Gurunathan5029 commented Dec 15, 2016 via email

cliviu commented Dec 15, 2016

shankar4a1 commented Apr 1, 2020

Gurunathan5029 commented Sep 13, 2016 •

edited

cliviu commented Sep 16, 2016 •

edited

cliviu commented Sep 22, 2016 •

edited

cliviu commented Sep 27, 2016 •

edited

Gurunathan5029 commented Nov 25, 2016 •

edited

Please see the logs I am getting
TEST PASSED: Build Validation