Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for dusty integration tests #69

Merged
merged 1 commit into from
Dec 30, 2020

Conversation

mbien
Copy link
Member

@mbien mbien commented Oct 19, 2020

integration tests should be working again.

commit msg:

  • the pom was broken possibly from a merge conflict from some time ago
  • fixed some paths and dependencies
  • adapted for firefox driver api changes
  • some tests needed minor updates due to the new bootstrap UI
  • some tests threw StaleElementReference exceptions when they tried to access elements after
    clicking a hyperlink which reloaded the page; fixed that too

tested with:
cd it-selenium
mvn clean integration-test -Dwebdriver.gecko.driver=/path/to/geckodriver

used:
geckodriver v0.26.0 on 64bit linux, latest firefox, jdk 14 and everything worked fine.

note:
do a mvn install of the roller root project first. Doing this for ./app is not sufficient
since the tests look for the project pom/war in local repo, not roller.war.
note2:
the test will display a few meters of jetty "class scanned from multiple locations" warnings
since the classpath is apperently set to target/ and the local copy in the maven repo.
Isn't convention over configuration great? I did not further attempt to fix this after trying
out some different dependency scopes without any effect.

 - the pom was broken possibly from a merge conflict from some time ago
 - fixed some paths and dependencies
 - adapted for firefox driver api changes
 - some tests needed minor updates due to the new bootstrap UI
 - some tests threw StaleElementReference exceptions when they tried to access elements after
   clicking a hyperlink which reloaded the page; fixed that too

tested with:
 cd it-selenium
 mvn clean integration-test -Dwebdriver.gecko.driver=/path/to/geckodriver

used:
 geckodriver v0.26.0 on 64bit linux, latest firefox, jdk 14 and everything worked fine.

note:
 do a mvn install of the roller root project first. Doing this for ./app is not sufficient
 since the tests look for the project pom/war in local repo, not roller.war.
note2:
 the test will display a few meters of jetty "class scanned from multiple locations" warnings
 since the classpath is apperently set to target/ and the local copy in the maven repo.
 Isn't convention over configuration great? I did not further attempt to fix this after trying
 out some different dependency scopes without any effect.
@mbien
Copy link
Member Author

mbien commented Oct 19, 2020

@snoopdave forgot to ping :-)

@snoopdave snoopdave merged commit f70b8d5 into apache:master Dec 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants