Return-Path: X-Original-To: apmail-incubator-isis-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-isis-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F2A7ECDA3 for ; Sun, 20 May 2012 07:30:41 +0000 (UTC) Received: (qmail 54311 invoked by uid 500); 20 May 2012 07:30:41 -0000 Delivered-To: apmail-incubator-isis-dev-archive@incubator.apache.org Received: (qmail 54292 invoked by uid 500); 20 May 2012 07:30:41 -0000 Mailing-List: contact isis-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: isis-dev@incubator.apache.org Delivered-To: mailing list isis-dev@incubator.apache.org Received: (qmail 54277 invoked by uid 99); 20 May 2012 07:30:41 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 May 2012 07:30:41 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 16620141887 for ; Sun, 20 May 2012 07:30:40 +0000 (UTC) Date: Sun, 20 May 2012 07:30:40 +0000 (UTC) From: "Dan Haywood (JIRA)" To: isis-dev@incubator.apache.org Message-ID: <1342140036.883.1337499041094.JavaMail.jiratomcat@issues-vm> In-Reply-To: <789523005.18457.1337421136831.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (ISIS-228) Use JUnit categories to distinguish between tests that can be run on CI server and those that cannot. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ISIS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279687#comment-13279687 ] Dan Haywood commented on ISIS-228: ---------------------------------- This technique fails because JUnit attempts to load the classes defined as categories. Since the definition of surefire is in the top-level POM, these classes (which I had defined in core.testsupport) do not exist. A quick search on google shows others hitting the same issue, eg https://github.com/KentBeck/junit/issues/400. So instead, am using a naming convention: * by default, exclude all *IntegrationTest* classes * if specify -P integtest-mongo, then run only the *Mongo*IntegrationTest* classes * if specify -P integtest-sql, then run only the *Sql*IntegrationTest* classes I haven't yet figured out a way to be able to run both the mongo and sql integration tests in a single run. > Use JUnit categories to distinguish between tests that can be run on CI server and those that cannot. > ----------------------------------------------------------------------------------------------------- > > Key: ISIS-228 > URL: https://issues.apache.org/jira/browse/ISIS-228 > Project: Isis > Issue Type: Improvement > Reporter: Dan Haywood > Assignee: Dan Haywood > Priority: Minor > > eg using technique as described in http://johndobie.blogspot.co.uk/2012/04/unit-and-integration-tests-with-maven.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira