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

Integrate Share Page Object (PO) Selenium webdrone capabilities to enable regression and functional testing #217

mindthegab opened this issue Sep 10, 2014 · 2 comments


Copy link

@mindthegab mindthegab commented Sep 10, 2014

Thanks to all the work done for Alfresco internal and community testing automation we have a now a very comprehensive library to run Share automated selenium based black box tests.

We want to:

  1. Integrate running of regression tests (-Pregression) in the all-in-one archetype to run vanilla Alfresco Share PO tests and ensure that developed / integrated customizations do not break Alfresco OOTB functionality
  2. We want to allow people to develop functional / regression tests based on the modular Share PO framework and integrate that in the share-amp and amp-archetype (and ultimately potentially augment the regression test suite run in the all-in-one)

This can be done using artifacts publicly available here;gav~~share-po~~~

@mindthegab mindthegab added this to the 2.0.0 milestone Sep 10, 2014
Copy link
Contributor Author

@mindthegab mindthegab commented Sep 10, 2014

First attempt to integrate share po in the amp archetype here #215 (still to be reviewed / merged)

mindthegab added a commit that referenced this issue Sep 10, 2014
-- added -Pregression profile to invoke Share PO / Selenium
functional/regression tests 
-- tested successfully with 'mvn clean install' -Prun,regression
(optionally -Dtest=LoginPageTests)
-- reports are produced in target
-- updates docs on available profiles
@mindthegab mindthegab modified the milestones: 2.0.0, 2.1.0 Dec 23, 2014
Copy link
Contributor Author

@mindthegab mindthegab commented May 21, 2015

This is fixed in 2.1.0, why wasn't it closed? (it missed the release notes)

@mindthegab mindthegab closed this May 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.