From: Jonas Fonseca <fonseca@diku.dk>
To: Imran M Yousuf <imran@smartitengineering.com>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org,
Imran M Yousuf <imyousuf@smartitengineering.com>
Subject: [JGIT PATCH] Configure the maven surefire plugin to specifically include all tests
Date: Fri, 12 Sep 2008 10:40:30 +0200 [thread overview]
Message-ID: <20080912084030.GA4964@diku.dk> (raw)
In-Reply-To: <9e85b2570809111851y756fdb3en2c17c69bf5ac444e@mail.gmail.com>
By default, the test cases named T000* were not included. With this
patch maven reports that 508 tests have been run.
Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
---
jgit-maven/jgit/pom.xml | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
Imran M Yousuf <imran@smartitengineering.com> wrote Fri, Sep 12, 2008:
> On Fri, Sep 12, 2008 at 6:00 AM, Jonas Fonseca <fonseca@diku.dk> wrote:
> > When I run all the tests using maven (inside
> > NetBeans or from the command line) it tells me:
> >
> > Tests run: 428, Failures: 0, Errors: 0, Skipped: 0
> >
> > From the output it looks like the tests in the files named T000* are
> > never run. However, where the breakage is (could be my setup) I don't
> > know. Imran?
> >
>
> Hmm, I will have to check it. Will come back with some feedback after
> checking. Usually if a class is a TestCase then it should have run.
I started looking for possible bug reports at jira.codehaus.org and
found an issue for extendeding the default path patterns used for
including and excluding tests. Maybe something like this patch is clean
enough, at least it increases "my coverage" to 508 tests.
diff --git a/jgit-maven/jgit/pom.xml b/jgit-maven/jgit/pom.xml
index a64f53c..a123470 100644
--- a/jgit-maven/jgit/pom.xml
+++ b/jgit-maven/jgit/pom.xml
@@ -158,6 +158,17 @@ ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<encoding>UTF-8</encoding>
</configuration>
</plugin>
+ <plugin>
+ <artifactId>maven-surefire-plugin</artifactId>
+ <version>2.4.2</version>
+ <configuration>
+ <includes>
+ <include>**/*Test.java</include>
+ <include>**/*TestCase.java</include>
+ <include>**/T000*.java</include>
+ </includes>
+ </configuration>
+ </plugin>
</plugins>
</build>
<dependencies>
--
1.6.0.1.451.gc8d31
--
Jonas Fonseca
next prev parent reply other threads:[~2008-09-12 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 21:39 [JGIT PATCH 1/2] Issue 23: Resolve tag^0 as tag^{commit} Jonas Fonseca
2008-09-11 22:47 ` Robin Rosenberg
2008-09-12 0:00 ` Jonas Fonseca
2008-09-12 1:51 ` Imran M Yousuf
2008-09-12 8:40 ` Jonas Fonseca [this message]
2008-09-12 14:47 ` [JGIT PATCH] Configure the maven surefire plugin to specifically include all tests Shawn O. Pearce
2008-09-12 6:47 ` [JGIT PATCH 1/2] Issue 23: Resolve tag^0 as tag^{commit} Robin Rosenberg
2008-09-12 10:57 ` [JGIT PATCH 1/3] Fix IncorrectObjectTypeException thrown for incorrect ^{blob} Jonas Fonseca
2008-09-12 10:57 ` [JGIT PATCH 2/3] Fix off by one distance during resolving of commit~N Jonas Fonseca
2008-09-12 10:57 ` [JGIT PATCH 3/3] Tests and fixes for dereferencing tags in Repository.resolve() Jonas Fonseca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080912084030.GA4964@diku.dk \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=imran@smartitengineering.com \
--cc=imyousuf@smartitengineering.com \
--cc=robin.rosenberg.lists@dewire.com \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).