trouble running Serenity tests

[Sumana Harihareswara]

Ben,

I can't seem to run the Serenity tests. I'd love some help figuring out why. I'm on Debian Linux.

I ran   env XVFB_DISPLAY=":10" ./gradlew test aggregate   and still got several of these:

 gov.medicaid.features.IntegrationTests > Scenario: Validate Tax ID Number.classMethod FAILED
net.thucydides.core.webdriver.UnsupportedDriverException
Caused by: net.thucydides.core.webdriver.UnsupportedDriverException
Caused by: org.openqa.selenium.WebDriverException

My integration-tests/serenity.properties is:

#webdriver.driver=phantomjs
webdriver.driver=chrome
#webdriver.driver=firefox
serenity.project.name =  Medicare/Medicaid Provider Enrollment Screening Portal

# This needs to be customized to find your installed version of phantom js driver
phantomjs.binary.path= ../../../phantomjs-2.1.1-linux-x86_64/bin/phantomjs

# Likewise, this should be modified to find the installed version
# of the chrome driver
webdriver.chrome.driver=/usr/bin/chromedriver

I don't think the shell should have trouble finding chrome, chromium, and chromedriver:

$ which chromedriver
/usr/bin/chromedriver
$ which chrome
/usr/bin/chrome
$ which chromium
/usr/bin/chromium

I'd love assistance so I can run the tests. Thanks!

best,

Sumana Harihareswara

Open Tech Strategies

[Ben Galewsky]

Sumana —

The best first step is to visit the test result HTML file placed in

psm-app/integration-tests/build/reports/tests/test

There will be a stack trace in there that should help us debug what is going on.

See you on IRC.

--
You received this message because you are subscribed to the Google Groups "psm-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to psm-dev+u...@googlegroups.com.
To post to this group, send email to psm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/psm-dev/CAPrEM3e4%2BP-nhHg%2B2qREpF0Z7J%2BTd-K8GEFzhDth%3DS4UoWA7Gg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Sumana Harihareswara]

Today I tried again and, with the updated psm-app/integration-tests/README.md documentation, plus Jason's help, I got the tests to run on my machine!

A slightly tricky set of prerequisites that I'm still getting used to:

1. As someone running Serenity interactively with Chrome on Linux, I need to take out a line in build.gradle to get the tests to run. (Details in the README.) Since build.gradle is version-controlled, I'm yanked back every time I need to switch branches; git complains that I have uncommitted changes. So I stash the change and reapply it to my checked-out branch. Jason might comment out that block, since it's for CI we don't have set up yet, but in the interim:

$ git stash save "integration test headless fix"

$ git checkout branchname

$ git stash pop

2. I need to remember to have WildFly running in a separate terminal in order for the tests to run.

3. I need to remember to tell Gradle to build and to clean before running the test & aggregate tasks; otherwise, Gradle doesn't recognize that there's something new to test.

$ ./gradlew cms-portal-services:build integration-tests:{clean,test,aggregate}

Does that work for folks well enough that I could update the documentation to suggest that command?

best,

Sumana

On Thu, Aug 10, 2017 at 9:25 AM, Ben Galewsky <be...@opentechstrategies.com> wrote:

Sumana —

The best first step is to visit the test result HTML file placed in

psm-app/integration-tests/build/reports/tests/test

There will be a stack trace in there that should help us debug what is going on.

See you on IRC.

To unsubscribe from this group and stop receiving emails from it, send an email to psm-dev+unsubscribe@googlegroups.com.

To post to this group, send email to psm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/psm-dev/CAPrEM3e4%2BP-nhHg%2B2qREpF0Z7J%2BTd-K8GEFzhDth%3DS4UoWA7Gg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "psm-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to psm-dev+unsubscribe@googlegroups.com.

To post to this group, send email to psm...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/psm-dev/310CFB38-D20E-4A11-93C7-C1FD6B0FE7F6%40opentechstrategies.com.

[Sumana Harihareswara]

3., revised: I have to build, and deploy the build, before testing.

$ ./gradlew cms-portal-services:build
$ ../../wildfly-10.1.0.Final/bin/jboss-cli.sh --connect --command="deploy --force cms-portal-services/build/libs/cms-portal-services.ear"
$ ./gradlew integration-tests:{clean,test,aggregate}

Iteratively,

Sumana Harihareswara

Open Tech Strategies

On Fri, Sep 8, 2017 at 3:18 PM, Sumana Harihareswara <sum...@opentechstrategies.com> wrote:

Today I tried again and, with the updated psm-app/integration-tests/README.md documentation, plus Jason's help, I got the tests to run on my machine!

A slightly tricky set of prerequisites that I'm still getting used to:

1. As someone running Serenity interactively with Chrome on Linux, I need to take out a line in build.gradle to get the tests to run. (Details in the README.) Since build.gradle is version-controlled, I'm yanked back every time I need to switch branches; git complains that I have uncommitted changes. So I stash the change and reapply it to my checked-out branch. Jason might comment out that block, since it's for CI we don't have set up yet, but in the interim:

$ git stash save "integration test headless fix"

$ git checkout branchname

$ git stash pop

2. I need to remember to have WildFly running in a separate terminal in order for the tests to run.

3. I need to remember to tell Gradle to build and to clean before running the test & aggregate tasks; otherwise, Gradle doesn't recognize that there's something new to test.

$ ./gradlew cms-portal-services:build integration-tests:{clean,test,aggregate}

Does that work for folks well enough that I could update the documentation to suggest that command?

best,

Sumana

On Thu, Aug 10, 2017 at 9:25 AM, Ben Galewsky <be...@opentechstrategies.com> wrote:

Sumana —

The best first step is to visit the test result HTML file placed in

psm-app/integration-tests/build/reports/tests/test

There will be a stack trace in there that should help us debug what is going on.

See you on IRC.