On 4 May 2012 13:55, Jasha Joachimsthal <[email protected]> wrote:
> Hi, > > Marlon and I developed a basic set of integration tests for Apache Rave: > - create new user and log in > - log in with 3 default accounts (canonical, john.doe and openid) > - delete the new user > These tests assume you have a running portal. Currently I'm working with > colleagues to let the test project start up the portal, perform the tests > and then shut down the portal. > > When this is done, we'd like to move this code base from Github [1] into > the Apache Rave svn code base (Marlon I assume you don't mind transferring > your code). You should then be able to build the project and automatically > run the integration tests using a separate Maven profile (probably mvn -P > integration-tests). > > [1] https://github.com/jashaj/PortalTests > I migrated PortalTests project into the Apache Rave project in the module rave-integration-tests. Documentation is at [2] In the current setup the rave-integration-tests module is neither a part of the regular build nor an artifact that is produced in the release of the project. See the documentation [2] how to run the integration tests. It is ignored during regular builds because I have not added rave-integration-tests as module in the default Maven profile, only in the integration-tests profile. When doing the release in the current setup, the rave-integration-tests module should be updated manually. We can make it a part of the release, but then some additional work regarding L&N must be done (we have more than 3 weeks left for that). Also we should then decide whether running the actual tests is a part of the release goal or just producing the artifacts in rave-integration-tests. [2] http://rave.apache.org/integration-tests.html Jasha
