[opencms-dev] Running Unit test cases (was: [PATCH]PostgreSQLSupport for OpenCms 6.x (CVS))
Antonio Core
antonio at starsolutions.it
Fri Dec 24 13:32:14 CET 2004
Alex,
you are right..
I executed all tests without test on "Legacy Tables".
Attached at this email, you can find:
1. the UnitTests log file TestLog.txt (with lastest result rows) :
- these three testCases failed:
1. testPublishScenarioA ( I Know that it's ok...)
2. testISO
3. testUTF8
that's right??
2. the lastest patches released for PostgreSQL
(opencms_postgresql_03.patch)
files changed:
- ./test/data/WEB-INF/config.postgresql/opencms.properties
- ./test/org/opencms/test/OpenCmsTestCase.java
Added the C_DB_POSTGRESQL string
- ./test/test.properties
Added the postgres choice
- ./webapp/setup/database/postgresql/create_db.sql
- ./webapp/setup/database/postgresql/drop_tables.sql
Wish you a Merry Christmas.
Best Regards,
Antonio.
On Mon, 2004-12-20 at 18:55 +0100, Alexander Kandzior wrote:
> Antonio,
>
> Regarding the "legacy tables" support - you should make sure that all other
> tests work first. Legacy support for a new installation with Postgres is not
> really something people will miss, it's more intended for users who have a
> OpenCms 5.0 version that actually use legacy stuff and want to upgrade to
> 6.0. Now since there is no Postgres in 5.0 this is something not really
> required.
>
> Best Regards,
> Alex.
>
> Alexander Kandzior
> Alkacon Software - The OpenCms Experts
> http://www.alkacon.com
>
>
>
> > -----Original Message-----
> > From: opencms-dev-bounces at opencms.org
> > [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Antonio Core
> > Sent: Monday, December 20, 2004 6:10 PM
> > To: The OpenCms mailing list
> > Subject: RE: [opencms-dev] Running Unit test cases (was:
> > [PATCH]PostgreSQLSupport for OpenCms 6.x (CVS))
> >
> > Alex,
> >
> > you can download the PostgreSQL JDBC driver from here:
> >
> > http://jdbc.postgresql.org/download/pg74.215.jdbc3.jar
> >
> > Regarding tests:
> >
> > You are right, I executed the
> > org.opencms.xml.content.AllTests; Now, I'm executing the
> > right one (org.opencms.test.AllTests). :-|
> >
> > For this reason, may you wait to include my patches released
> > yesterday?
> > I'll send you the right one asap.
> >
> > Running unittests with the right class, I receive this error:
> >
> > Testcase: testLegacyInitialization took 2.672 sec
> > FAILED
> > Master tables not created!
> > junit.framework.AssertionFailedError: Master tables not created!
> > at
> > org.opencms.module.TestModuleLegacy.testLegacyInitialization(T
> > estModuleLegacy.java:143)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> > orImpl.java:39)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> > odAccessorImpl.java:25)
> > at
> > junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> > at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> > at junit.extensions.TestSetup.run(TestSetup.java:23)
> > at
> > junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> > at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> > at junit.extensions.TestSetup.run(TestSetup.java:23)
> >
> >
> > To resolve this problem, I created the file 'postgresql.sql'
> > with specific PostgreSQL commands, but I don't know how to
> > proceed to insert it into the
> > "org.opencms.legacy.compatibility" module.
> >
> > May be, do I have to follow these steps? :
> >
> > - Create the 'postgresql.sql' directly inside OpenCMS
> > database (using OpenCms Application);
> > - Export the module changed;
> > - change the source code of module in my source tree using
> > the source code generated by export.
> >
> > Is it the right way to proceed?
> > May you support me??
> >
> >
> > Regards,
> >
> > Antonio
> >
> >
> >
> > On Mon, 2004-12-20 at 12:44 +0100, Alexander Kandzior wrote:
> > > Antonio,
> > >
> > > I'll include your patch in the CVS later today or tomorrow.
> > >
> > > Please send me the download URL for the ProstgreSQL
> > > pg74.215.jdbc3.jar, I'll then include this in the
> > distribution as well.
> > >
> > > Regarding yout tests: Did you execute
> > org.opencms.test.AllTests? The
> > > output you attached was only regarding
> > > org.opencms.xml.content.AllTests, so there's a lot missing.
> > In fact,
> > > if you did execute the right test, you must have exactly one test
> > > failing, this is the "publish project scenario A", since
> > this currently always fails.
> > >
> > > Best Regards,
> > > Alex.
> > >
> > > Alexander Kandzior
> > > Alkacon Software - The OpenCms Experts http://www.alkacon.com
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: opencms-dev-bounces at opencms.org
> > > > [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Antonio Core
> > > > Sent: Sunday, December 19, 2004 2:33 AM
> > > > To: The OpenCms mailing list
> > > > Subject: Re: [opencms-dev] Running Unit test cases (was:
> > > > [PATCH] PostgreSQLSupport for OpenCms 6.x (CVS))
> > > >
> > > > Alex,
> > > >
> > > > I regret for the late response, but I had problems with my Pc...
> > > >
> > > > I prepared the configurations file for unit tests on PostgreSQL
> > > > following your instructions.
> > > > The tests have been executed without errors; please, find
> > attached
> > > > at this email the log file
> > > > (TEST-org.opencms.xml.content.AllTests.txt).
> > > >
> > > > Attached at this email there is the "opencms_postgresql_02.patch"
> > > > file with these changes:
> > > >
> > > > File changed:
> > > >
> > > > - opencms/build.xml
> > > > the postgresql lines have been added.
> > > >
> > > > - opencms/test/test.properties
> > > > the setup for postgresql has been added.
> > > >
> > > > - opencms/test/data/WEB-INF/config/opencms-vfs.xml
> > > > the unittests failed because the class
> > > >
> > > >
> > > > org.opencms.workplace.xmlwidgets.CmsXmlVfsImageWidget
> > > >
> > > > doesn't exist anymore in the CVS tree.
> > > > Reading in the CVS log, I thought taht this class
> > > > has been replaced by
> > > >
> > > >
> > > > org.opencms.workplace.xmlwidgets.CmsXmlImageGalleryWidget
> > > >
> > > > For this reason, I replaced the line:
> > > >
> > > > <widget
> > class="org.opencms.workplace.xmlwidgets.CmsXmlVfsImageWidget"
> > > > alias="VfsImageWidget"/>
> > > >
> > > > whit that one:
> > > >
> > > > <widget
> > > > class="org.opencms.workplace.xmlwidgets.CmsXmlImageGalleryWidget"
> > > > alias="ImageWidget" />
> > > >
> > > > This is the same value as in the
> > > >
> > opencms/webapp/WEB-INF/config/opencms-vfs.xml
> > > > file.
> > > > I hope that it is correct.
> > > >
> > > >
> > > > -
> > opencms/webapp/setup/database/postgresql/create_db.sql
> > > > - opencms/webapp/setup/database/postgresql/drop_db.sql
> > > > -
> > opencms/webapp/setup/database/postgresql/drop_tables.sql
> > > > -
> > > > opencms/webapp/setup/database/postgresql/step_4_database_setup.jsp
> > > > Changed the PostgreSQL setup file, according
> > > > unittests results.
> > > >
> > > > File Added:
> > > > -
> > > > opencms/test/data/WEB-INF/config.postgresql/opencms-modules.xml
> > > > -
> > > > opencms/test/data/WEB-INF/config.postgresql/opencms.properties
> > > > Configuration files to use in unittests with
> > > > PostgreSQL database
> > > >
> > > > Moreover, in the CVS source tree the file
> > pg74.215.jdbc3.jar is not
> > > > present yet...
> > > >
> > > > Best Regards,
> > > > Antonio
> > > >
> > > >
> > > > On Mon, 2004-12-06 at 12:36 +0100, Alexander Kandzior wrote:
> > > > > Antonio,
> > > > >
> > > > > It took me a couple of days, but I actually "repaired" the
> > > > "unittests"
> > > > > target in the build.xml file. Turns out there was a library
> > > > missing.
> > > > >
> > > > > Let's assume you are able to run "ant war" and generate the
> > > > > OpenCms war file.
> > > > >
> > > > > Try running "ant unittests". This will run all the
> > Junit tests and
> > > > > write the output to a file. The location of the file is ant
> > > > specific
> > > > > and may depend on your setup. Also, the optional "junit" target
> > > > > support for ant is required, this usually comes in a
> > > > "ant-junit.jar".
> > > > > Please check the ant homepage on how to configure these since.
> > > > >
> > > > > OpenCms configuration for unit tests:
> > > > >
> > > > > The unit tests run with a pre-configured database
> > > > configuration. The
> > > > > file "/test/test.properties" contains the main test settings.
> > > > > Basically you must configure the database you want to
> > test here,
> > > > > as well as the local path configuration where the data
> > is located.
> > > > >
> > > > > Each database must come with it's own set of pre-configured
> > > > > "opencms.properties". In the folder "/test/data/WEB-INF"
> > > > you will find
> > > > > one config.xxx folder for each supported database.
> > These files are
> > > > > copied automatically to "/test/data/WEB-INF/config" during
> > > > test setup.
> > > > >
> > > > > For example, mySQL is configured by default in
> > > > "test.propeties" with
> > > > > the "db.product=mysql" setting. So the mySQL secific
> > settings are
> > > > > taken form the folder "/test/data/WEB-INF/config.mysql". So in
> > > > > the mySQL example, it's assumed that there is a local mysql
> > > > installation, the user name is "root"
> > > > > and the user has no password. All of this is located in
> > > > > "opencms.properties". In case the test cases can't
> > connect to the
> > > > > database, you must modify these parameters.
> > > > >
> > > > > Best Regards,
> > > > > Alex.
> > > > >
> > > > > Alexander Kandzior
> > > > > Alkacon Software - The OpenCms Experts http://www.alkacon.com
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: opencms-dev-bounces at opencms.org
> > > > > > [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Antonio
> > > > > > Core
> > > > > > Sent: Thursday, December 02, 2004 2:56 PM
> > > > > > To: The OpenCms mailing list
> > > > > > Subject: RE: [opencms-dev] [PATCH] PostgreSQL Support for
> > > > > > OpenCms 6.x (CVS)
> > > > > >
> > > > > > Alex,
> > > > > >
> > > > > > Normally, I use jEdit as my development tool.
> > > > > >
> > > > > > Anyway, I've already installed Eclipse (ver 3.1M3) and I'm
> > > > > > trying it. ;)
> > > > > >
> > > > > > May you send me more informations about how proceed
> > to setup and
> > > > > > perform JUnit tests with Eclipse?
> > > > > >
> > > > > > Best Regards,
> > > > > >
> > > > > > Antonio
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, 2004-12-02 at 10:36, Alexander Kandzior wrote:
> > > > > > > Are you using Eclipse for development?
> > > > > > > If so, I can yout tell how we do it, since we are
> > using Eclipse.
> > > > > > > If not, there's also an ant task, but this may
> > > > currently be broken.
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > Alex.
> > > > > > >
> > > > > > > Alexander Kandzior
> > > > > > > Alkacon Software - The OpenCms Experts
> > http://www.alkacon.com
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: opencms-dev-bounces at opencms.org
> > > > > > > > [mailto:opencms-dev-bounces at opencms.org] On Behalf Of
> > > > > > > > Antonio Core
> > > > > > > > Sent: Thursday, December 02, 2004 10:19 AM
> > > > > > > > To: The OpenCms mailing list
> > > > > > > > Subject: RE: [opencms-dev] [PATCH] PostgreSQL Support for
> > > > > > > > OpenCms 6.x (CVS)
> > > > > > > >
> > > > > > > > Alex,
> > > > > > > >
> > > > > > > > No, i didn't, sorry.
> > > > > > > >
> > > > > > > > I think that it will be necessary too.
> > > > > > > >
> > > > > > > > Thank you very much if you support me with that.
> > > > > > > >
> > > > > > > > Best Regards,
> > > > > > > >
> > > > > > > > Antonio
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, 2004-12-02 at 09:51, Alexander Kandzior wrote:
> > > > > > > > > I applied these fixes to the CVS version.
> > > > > > > > >
> > > > > > > > > Antonio, did you run the Junit tests for
> > Postgessql? These
> > > > > > > > are really
> > > > > > > > > helpful since they have quite a broad range of daabase
> > > > > > operation
> > > > > > > > > covered already. If not I can support you in
> > getting these
> > > > > > > > up and running.
> > > > > > > > >
> > > > > > > > > Best Regards,
> > > > > > > > > Alex.
> > > > > > > > >
> > > > > > > > > Alexander Kandzior
> > > > > > > > > Alkacon Software - The OpenCms Experts
> > > > http://www.alkacon.com
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: opencms-dev-bounces at opencms.org
> > > > > > > > > > [mailto:opencms-dev-bounces at opencms.org] On Behalf Of
> > > > > > > > > > Antonio Core
> > > > > > > > > > Sent: Wednesday, December 01, 2004 10:14 PM
> > > > > > > > > > To: OpenCms
> > > > > > > > > > Subject: [opencms-dev] [PATCH] PostgreSQL Support for
> > > > > > > > > > OpenCms 6.x
> > > > > > > > > > (CVS)
> > > > > > > > > >
> > > > > > > > > > Dear all,
> > > > > > > > > >
> > > > > > > > > > here is a patch for postgreSQL database support.
> > > > > > > > > >
> > > > > > > > > > The files changed:
> > > > > > > > > >
> > > > > > > > > >
> > > > opencms/src/org/opencms/db/postgresql/CmsBackupDriver.java
> > > > > > > > > > (specialized method deleteBackups of class
> > > > > > > > > >
> > > > opencms.src.org.opencms.db.generic.CmsBackupDriver)
> > > > > > > > > >
> > > > > > > > > > opencms/src/org/opencms/db/postgresql/query.properties
> > > > > > > > > > (added queries:
> > > > > > > > > > C_POSTGRESQL_BACKUP_DELETE_CONTENT
> > > > > > > > > > C_POSTGRESQL_BACKUP_DELETE_RESOURCES
> > > > > > > > > > C_POSTGRESQL_BACKUP_DELETE_STRUCTURE
> > > > > > > > > > removed query:
> > > > > > > > > > C_BACKUP_DELETE_RESOURCE
> > > > > > > > > > )
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Having a CVS checkout of the opencms source, go into
> > > > > > the opencms
> > > > > > > > > > directory and launch the following command:
> > > > > > > > > >
> > > > > > > > > > patch -p0 < ....path.../opencms_postgresql_01.patch
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Best Regards,
> > > > > > > > > >
> > > > > > > > > > Antonio
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > This mail is send to you from the opencms-dev
> > mailing list
> > > > > > > > To change
> > > > > > > > > your list options, or to unsubscribe from the list,
> > > > > > please visit
> > > > > > > > > http://mail.opencms.org/mailman/listinfo/opencms-dev
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > This mail is send to you from the opencms-dev mailing
> > > > > > list To change
> > > > > > > > your list options, or to unsubscribe from the list,
> > > > please visit
> > > > > > > > http://mail.opencms.org/mailman/listinfo/opencms-dev
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > This mail is send to you from the opencms-dev mailing list
> > > > > > To change
> > > > > > > your list options, or to unsubscribe from the list,
> > > > please visit
> > > > > > > http://mail.opencms.org/mailman/listinfo/opencms-dev
> > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > This mail is send to you from the opencms-dev mailing
> > > > list To change
> > > > > > your list options, or to unsubscribe from the list,
> > please visit
> > > > > > http://mail.opencms.org/mailman/listinfo/opencms-dev
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > This mail is send to you from the opencms-dev mailing list
> > > > To change
> > > > > your list options, or to unsubscribe from the list,
> > please visit
> > > > > http://mail.opencms.org/mailman/listinfo/opencms-dev
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > This mail is send to you from the opencms-dev mailing list
> > To change
> > > your list options, or to unsubscribe from the list, please visit
> > > http://mail.opencms.org/mailman/listinfo/opencms-dev
> >
> >
> >
> > _______________________________________________
> > This mail is send to you from the opencms-dev mailing list To
> > change your list options, or to unsubscribe from the list,
> > please visit http://mail.opencms.org/mailman/listinfo/opencms-dev
> >
> >
>
>
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: opencms_postgresql_03.patch
Type: text/x-patch
Size: 4843 bytes
Desc: not available
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20041224/83e7f0ef/attachment.bin>
-------------- next part --------------
Shutting down OpenCms, version 6.0 alpha 2 Caladan in web application 'data'
Shutdown completed, total uptime was 00:01:08.
Shutting down OpenCms, version 6.0 alpha 2 Caladan in web application 'data'
Shutdown completed, total uptime was 00:00:35.
Shutting down OpenCms, version 6.0 alpha 2 Caladan in web application 'data'
Shutdown completed, total uptime was 00:00:05.
Shutting down OpenCms, version 6.0 alpha 2 Caladan in web application 'data'
Shutdown completed, total uptime was 00:00:04.
Shutting down OpenCms, version 6.0 alpha 2 Caladan in web application 'data'
Shutdown completed, total uptime was 00:00:07.
Shutting down OpenCms, version 6.0 alpha 2 Caladan in web application 'data'
Shutdown completed, total uptime was 00:00:43.
org.opencms.util.TestCmsStringUtil.testCmsContentReplacement():
<html><body>
See <a href="http://www.opencms.org/opencms/opencms/opencms/index.html">
http://www.opencms.org/opencms/opencms/opencms/index.html</a>
or <a href="${OpenCmsContext}/opencms/index.html">
${OpenCmsContext}/opencms/index.html</a>
<img src="${OpenCmsContext}/system/galleries/pics/test/test.gif">
<img src="http://www.othersite.org/opencms/opencms/system/galleries/pics/test/test.gif">
Some URL in the Text: http://www.thirdsite.org/opencms/opencms/some/url.html.
Another URL in the Text: ${OpenCmsContext}/some/url.html.
</body></html>
Shutting down OpenCms, version 6.0 alpha 2 Caladan in web application 'data'
Shutdown completed, total uptime was 00:00:31.
Shutting down OpenCms, version 6.0 alpha 2 Caladan in web application 'data'
Shutdown completed, total uptime was 00:00:34.
Shutting down OpenCms, version 6.0 alpha 2 Caladan in web application 'data'
Shutdown completed, total uptime was 00:00:39.
------------- ---------------- ---------------
Testcase: testLoadXmlConfiguration took 5.323 sec
Testcase: testConfiguredSites took 0.001 sec
Testcase: testChaccFileGroup took 0.408 sec
Testcase: testChaccFileUser took 0.249 sec
Testcase: testChaccAddRemove took 1.387 sec
Testcase: testCopySingleResourceAsNew took 0.294 sec
Testcase: testCopyFolderAsNew took 6.755 sec
Testcase: testCopyOverwriteDeletedFile took 1.596 sec
Testcase: testChtypNewFile took 0.181 sec
Testcase: testImportResource took 0.299 sec
Testcase: testImportResourceAgain took 0.409 sec
Testcase: testImportSibling took 1.092 sec
Testcase: testImportFolder took 0.278 sec
Testcase: testImportFolderAgain took 0.386 sec
Testcase: testCreateResource took 0.301 sec
Testcase: testCreateResourceAgain took 0.497 sec
Testcase: testCreateFolder took 0.271 sec
Testcase: testCreateFolderAgain took 0.434 sec
Testcase: testExistsForExistingFile took 0.023 sec
Testcase: testExistsForUnexistingFile took 0.111 sec
Testcase: testExistsForUnauthorizedFile took 1.217 sec
Testcase: testLockForFile took 0.213 sec
Testcase: testLockForFolder took 0.78 sec
Testcase: testLockForFolderPrelockedShared took 0.857 sec
Testcase: testLockForFolderPrelockedExclusive took 0.813 sec
Testcase: testLockSteal took 0.341 sec
Testcase: testLockRequired took 0.677 sec
Testcase: testLockInherit took 0.185 sec
Testcase: testLockForSiblings took 0.575 sec
Testcase: testLockForBaseOperations took 0.548 sec
Testcase: testMoveSingleResource took 0.484 sec
Testcase: testMoveSingleNewResource took 0.337 sec
Testcase: testMultipleMoveResource took 0.955 sec
Testcase: testPublishPermissions took 0.958 sec
Testcase: testVisiblePermission took 0.202 sec
Testcase: testVisiblePermissionForFolder took 0.282 sec
Testcase: testFilterForFolder took 0.033 sec
Testcase: testDefaultPermissions took 0.202 sec
Testcase: testPermissionOverwrite took 0.163 sec
Testcase: testPermissionInheritance took 0.467 sec
Testcase: testUserDeletion took 0.129 sec
Testcase: testCreateDeleteProject took 0.089 sec
Testcase: testCopyResourceToProject took 0.048 sec
Testcase: testDeleteProjectWithResources took 25.957 sec
Testcase: testWriteProperty took 0.248 sec
Testcase: testWriteProperties took 0.228 sec
Testcase: testRemoveProperty took 0.223 sec
Testcase: testRemoveProperties took 0.228 sec
Testcase: testCreateProperty took 0.276 sec
Testcase: testCreateProperties took 0.226 sec
Testcase: testWritePropertyOnFolder took 1.579 sec
Testcase: testCreatePropertyDefinition took 0.079 sec
Testcase: testCreateReadDeletePropertyDefinition took 0.049 sec
Testcase: testGetResourcesWithProperty took 0.046 sec
Testcase: testPublishNewFiles took 1.966 sec
Testcase: testPublishNewFilesInNewFolder took 2.179 sec
Testcase: testPublishChangedFiles took 1.824 sec
Testcase: testPublishLockedFiles took 0.524 sec
Testcase: testPublishDeletedFiles took 0.998 sec
Testcase: testPublishProjectLastmodified took 0.945 sec
Testcase: testPublishScenarioA took 0.278 sec
FAILED
expected:<1> but was:<0>
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at org.opencms.file.TestPublishIssues.testPublishScenarioA(TestPublishIssues.java:182)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
Testcase: testPublishScenarioB took 0.721 sec
Testcase: testPublishScenarioC took 1.498 sec
Testcase: testMultipleProjectCreation took 0.095 sec
Testcase: testDirectPublishWithSiblings took 9.981 sec
Testcase: testReadBeforeReleaseDate took 0.87 sec
Testcase: testReadInValidTimeRange took 0.195 sec
Testcase: testReadAfterExpirationDate took 0.189 sec
Testcase: testReadBeforeReleaseDateIgnore took 0.467 sec
Testcase: testReadInValidTimeRangeIgnore took 0.168 sec
Testcase: testReadAfterExpirationDateIgnore took 0.175 sec
Testcase: testReadSubtree took 0.911 sec
Testcase: testReadChildren took 0.541 sec
Testcase: testReadFolders took 0.527 sec
Testcase: testReadFiles took 2.159 sec
Testcase: testReadResources took 0.051 sec
Testcase: testReadModifiedResources took 0.702 sec
Testcase: testReadResourcesInTimerange took 0.348 sec
Testcase: testReplaceResourceContent took 0.195 sec
Testcase: testGetFolderPath took 0 sec
Testcase: testGetName took 0.001 sec
Testcase: testGetParentFolder took 0 sec
Testcase: testGetPathLevel took 0 sec
Testcase: testGetPathPart took 0 sec
Testcase: testIsFolder took 0 sec
Testcase: testGetFolderPath took 0 sec
Testcase: testResourceNames took 0.073 sec
Testcase: testCreateResources took 0.146 sec
Testcase: testCreateReadFile took 0.063 sec
Testcase: testPublishFile took 0.305 sec
Testcase: testCreateSibling took 0.133 sec
Testcase: testCreateAccessFolders took 0.117 sec
Testcase: testRestoreResource took 1.608 sec
Testcase: testRestoreDeletedResource took 0.764 sec
Testcase: testHistoryOverflow took 7.786 sec
Testcase: testSiblingsCopy took 0.413 sec
Testcase: testSiblingsCreate took 0.365 sec
Testcase: testSiblingIssueAfterImport took 5.66 sec
Testcase: testTouchFile took 0.244 sec
Testcase: testTouchFolder took 4.051 sec
Testcase: testTouchFolderRecursive took 3.475 sec
Testcase: testUndoChangesResource took 4.939 sec
Testcase: testUndoChangesOnNewResource took 0.08 sec
Testcase: testUndoChangesFolder took 10.513 sec
Testcase: testUndoChangesFolderRecursive took 20.426 sec
Testcase: testUndoChangesAfterCopyNewOverDeleted took 4.489 sec
Testcase: testUndoChangesAfterCopySiblingOverDeleted took 0.755 sec
Testcase: testUndoChangesWithAce took 0.843 sec
Testcase: testSetDateLastModifiedToPreviousTimeout took 0.073 sec
Testcase: testEncodeForHtml took 0.033 sec
Testcase: testDecodeHtmlEntities took 0.003 sec
Testcase: testLookupEncoding took 0 sec
Testcase: testSetDirectories took 0.018 sec
Testcase: testConvertDigestEncoding took 0 sec
Testcase: testUserImport took 0.104 sec
Testcase: testImportResourceTranslator took 4.339 sec
Testcase: testImportResourceTranslatorMultipleSite took 3.043 sec
Testcase: testCmsSetup took 29.627 sec
Testcase: testCmsShell took 27.259 sec
Testcase: testInitCmsObject took 0.03 sec
Testcase: testLog took 0.004 sec
Testcase: testEncoding took 0.001 sec
Testcase: testNameGeneration took 0.001 sec
Testcase: testVersionIncrement took 0 sec
Testcase: testVersionGeneration took 0.002 sec
Testcase: testModuleImport took 0.188 sec
Testcase: testModuleExport took 0.537 sec
Testcase: testOldModuleImport took 0.222 sec
Testcase: testModuleDependencies took 2.331 sec
Testcase: testModuleAdditionalResourcesWorkaround took 0.043 sec
Testcase: testModuleActionClass took 1.697 sec
Testcase: testAdditionalSystemFolder took 1.584 sec
Testcase: testShutdownMethod took 0.53 sec
Testcase: testMemoryMonitor took 19.391 sec
Testcase: testBasicJobExecution took 8.042 sec
Testcase: testCmsJobLaunch took 8.026 sec
Testcase: testJobInOpenCmsScheduler took 8.022 sec
Testcase: testPersitentJobInOpenCmsScheduler took 8.023 sec
Testcase: testDefaultConfiguration took 8.034 sec
Testcase: testCmsSearchIndexer took 6.951 sec
Testcase: testCmsSearchXmlContent took 0.549 sec
Testcase: testPasswordValidation took 0.001 sec
Testcase: testSetResetPassword took 0.172 sec
Testcase: testSaveProperties took 0.073 sec
Testcase: testCreateDatabase took 0.054 sec
Testcase: testCreateTables took 0.454 sec
Testcase: testDropTables took 1.361 sec
Testcase: testDropDatabase took 0 sec
Testcase: testToAbsolute took 0.001 sec
Testcase: testStaticexportFile took 0.589 sec
Testcase: testSynchronize took 15.997 sec
Testcase: testTranslateResource took 0.006 sec
Testcase: testSubstitute took 0.001 sec
Testcase: testSubstituteMacros took 0.136 sec
Testcase: testEscapePattern took 0.001 sec
Testcase: testCombined took 0 sec
Testcase: testLine took 0 sec
Testcase: testComplexPatternForImport took 0.001 sec
Testcase: testCmsContentReplacement took 0.016 sec
Testcase: testExtractXmlEncoding took 0.001 sec
Testcase: testExtractHtmlBody took 0.001 sec
Testcase: testMatchBrowser took 0.007 sec
Testcase: testRegex took 0.001 sec
Testcase: testUUID took 0 sec
Testcase: testTranslateResource took 0.002 sec
Testcase: testValidateResourceName took 0.001 sec
Testcase: testISO took 0.338 sec
FAILED
expected:<......> but was:<...
...>
junit.framework.ComparisonFailure: expected:<......> but was:<...
...>
at org.opencms.util.TestCmsHtmlConverter.testISO(TestCmsHtmlConverter.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
Testcase: testUTF8 took 0.008 sec
FAILED
expected:<...äöüÄÖÜß...> but was:<...�������
...>
junit.framework.ComparisonFailure: expected:<...äöüÄÖÜß...> but was:<...�������
...>
at org.opencms.util.TestCmsHtmlConverter.testUTF8(TestCmsHtmlConverter.java:86)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
Testcase: testremoveWordTags took 0.1 sec
Testcase: testGalleryClassCreation took 0.05 sec
Testcase: testCreateXpath took 0 sec
Testcase: testUnmarshalFromString took 0.048 sec
Testcase: testCmsXmlContentDefiniton took 0.006 sec
Testcase: testCreateXmlContent took 0.073 sec
Testcase: testAddRemoveElements took 0.094 sec
Testcase: testContentHandler took 0.062 sec
Testcase: testNestedSchema took 0.11 sec
Testcase: testAddRemoveNestedElements took 0.348 sec
Testcase: testAccessNestedElements took 0.322 sec
Testcase: testValueIndex took 0.014 sec
Testcase: testLayoutWidgetMapping took 0.027 sec
Testcase: testLinkResolver took 0.021 sec
Testcase: testValidation took 0.27 sec
Testcase: testValidationExtended took 0.491 sec
Testcase: testValidationLocale took 0.039 sec
Testcase: testMappings took 0.2 sec
Testcase: testResourceBundle took 0.015 sec
Testcase: testMacros took 0.195 sec
Testcase: testXmlPageRenameElement took 0.039 sec
Testcase: testXmlPageElementNames took 0.023 sec
Testcase: testXmlPageCreateMinimal took 0.005 sec
Testcase: testXmlPageWriteOldVersion took 0.007 sec
Testcase: testXmlPageWriteFinalVersion took 0.006 sec
Testcase: testXmlPageLocaleAccess took 0.003 sec
Testcase: testXmlPageReadFinalVersion took 0.011 sec
Testcase: testXmlPageReadOldVersion took 0.012 sec
Testcase: testValidateXmlPageWithSchema took 0.039 sec
Testcase: testXmlPageAsXmlContentDefinition took 0.016 sec
Testcase: testUpdateXmlPageLink took 0.011 sec
Testcase: testSchemaCachePublishIssue took 1 sec
Testcase: testLinkReplacement took 0.357 sec
Testcase: testCommentInSource took 0.119 sec
Testcase: testXmlPageRenameElement took 3.653 sec
Testcase: testMalformedPage took 0.337 sec
More information about the opencms-dev
mailing list