openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Curtis <curti...@gmail.com>
Subject Re: Tests are ignored
Date Mon, 17 May 2010 17:08:45 GMT
I'm guessing that you didn't look at the proper test result summary. Try
running this command [1] which will aggregate all test results into a single
web page.

You don't want to have the WARNING messages interpreted as exceptions,
because they are truly WARNING messages. They indicate that OpenJPA
encountered XML mapping information that is going to override mapping
information that was supposed as annotations. I supposed it is debatable
whether or not this should be a WARNING... but for the time being it is
there.

Thanks,
Rick

[1]
cd trunk/openjpa-parent
mvn surefire-report:report-only -Daggregate=true
-- The results of this run can be found at
trunk/openjpa-parent/target/site/surefire-report.html


On Mon, May 17, 2010 at 11:57 AM, Web developer <webautomator2@gmail.com>wrote:

> Here is the end of trace output:
> ....
> /root/openjpa/openjpa-integration/validation/target/surefire-reports
>
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> There are no tests to run.
>
> Results :
>
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] OpenJPA Parent POM .................................... SUCCESS
> [12.491s]
> [INFO] OpenJPA Utilities Library ............................. SUCCESS
> [2:37.916s]
> [INFO] OpenJPA Kernel ........................................ SUCCESS
> [5:06.648s]
> [INFO] OpenJPA JDBC .......................................... SUCCESS
> [2:15.165s]
> [INFO] OpenJPA Persistence ................................... SUCCESS
> [1:02.926s]
> [INFO] OpenJPA Persistence JDBC .............................. SUCCESS
> [18:41.375s]
> [INFO] OpenJPA Persistence Locking Tests ..................... SUCCESS
> [8:21.789s]
> [INFO] OpenJPA XML Store ..................................... SUCCESS
> [2:39.756s]
> [INFO] OpenJPA Slice ......................................... SUCCESS
> [27.167s]
> [INFO] OpenJPA Aggregate Jar ................................. SUCCESS
> [13.436s]
> [INFO] OpenJPA Aggregate Jar with Dependencies ............... SUCCESS
> [1:37.557s]
> [INFO] OpenJPA Project Docs and Assemblies ................... SUCCESS
> [17.748s]
> [INFO] OpenJPA Examples ...................................... SUCCESS
> [7.545s]
> [INFO] OpenJPA Integration Tests ............................. SUCCESS
> [0.132s]
> [INFO] OpenJPA Integration Tests - Daytrader ................. SUCCESS
> [35.845s]
> [INFO] OpenJPA Integration Tests - Examples .................. SUCCESS
> [0.646s]
> [INFO] OpenJPA Integration Tests - JPA TCK ................... SUCCESS
> [0.163s]
> [INFO] OpenJPA Integration Tests - Bean Validation ........... SUCCESS
> [1:00.259s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 45 minutes 28 seconds
> [INFO] Finished at: Mon May 17 19:53:09 EEST 2010
> [INFO] Final Memory: 126M/488M
> [INFO]
> ------------------------------------------------------------------------
>
> According to output some tests are ignored. How can I force a test runner
> to
> interpret warnings as exceptions? Otherwise test are useless in case of
> deployment. John
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message