Changes between Version 15 and Version 16 of WikiEditorForEclipsePlugin

Timestamp:

May 22, 2009, 6:39:06 PM (15 years ago)

Author:

Ivan

Comment:

Running tests section

WikiEditorForEclipsePlugin

@@ -59 +59 @@
 This plugin is composed by:
 
-        * Java Wiki RPC Client Library: this library features a !WikiClient high level API to access
+        * Java !WikiRPC client library: including a high level API to access the [http://www.jspwiki.org/wiki/WikiRPCInterface WikiRPCInterface] and a batch of automated tests to test default implementation against a Trac server (see [#RunningTests Running Tests] below).
 
         * Set of Eclipse plugins: Eclipse wiki source editor and management capabilities.
@@ -92 +92 @@
 [INFO] Reactor Summary:
 [INFO] ------------------------------------------------------------------------
-[INFO] Trac WikiEditor 4 Eclipse ............................. SUCCESS [26.222s]
-[INFO] Trac WikiEditor 4 Eclipse ~ Core ...................... SUCCESS [23.628s]
-[INFO] Trac WikiEditor 4 Eclipse ~ Eclipse Modules ........... SUCCESS [1.014s]
-[INFO] Trac WikiEditor 4 Eclipse ~ org.trachacks.wikieditor.eclipse.core  SUCCESS [51.335s]
-[INFO] Trac WikiEditor 4 Eclipse ~ org.trachacks.wikieditor.eclipse.plugin  SUCCESS [12.982s]
-[INFO] Trac WikiEditor 4 Eclipse ~ org.trachacks.wikieditor.eclipse.feature  SUCCESS [3.986s]
-[INFO] Trac WikiEditor 4 Eclipse ~ org.trachacks.wikieditor.eclipse.site  SUCCESS [9.239s]
+[INFO] Trac WikiEditor 4 Eclipse ............................. SUCCESS [26.864s]
+[INFO] Trac WikiEditor 4 Eclipse ~ Core ...................... SUCCESS [1:05.127s]
+[INFO] Trac WikiEditor 4 Eclipse ~ Eclipse Modules ........... SUCCESS [1.083s]
+[INFO] Trac WikiEditor 4 Eclipse ~ org.trachacks.wikieditor.eclipse.core  SUCCESS [47.909s]
+[INFO] Trac WikiEditor 4 Eclipse ~ org.trachacks.wikieditor.eclipse.plugin  SUCCESS [13.284s]
+[INFO] Trac WikiEditor 4 Eclipse ~ org.trachacks.wikieditor.eclipse.feature  SUCCESS [2.595s]
+[INFO] Trac WikiEditor 4 Eclipse ~ org.trachacks.wikieditor.eclipse.site  SUCCESS [8.048s]
 [INFO] ------------------------------------------------------------------------
 [INFO] ------------------------------------------------------------------------
 [INFO] BUILD SUCCESSFUL
 [INFO] ------------------------------------------------------------------------
-[INFO] Total time: 2 minutes 25 seconds
-[INFO] Finished at: Sun May 17 20:11:30 CEST 2009
-[INFO] Final Memory: 27M/50M
+[INFO] Total time: 2 minutes 57 seconds
+[INFO] Finished at: Thu May 21 22:14:13 CEST 2009
+[INFO] Final Memory: 29M/52M
 [INFO] ------------------------------------------------------------------------
 }}}
@@ -111 +111 @@
 This will create a local eclipse update site at ''!WikiEditor4Eclipse/source/eclipse/org.trachacks.wikieditor.eclipse.site/target/site'' you can point Eclipse Update Manager to. 
 
-== Runing Tests ==
-
-In order to run automated tests against a Trac server you will need to setup a local server
-
-TODO: how to set up tests prerequisites
-
+== Running Tests ==
+
+In order to run automated tests against a Trac server you will need to setup a local server. These are the prerequisites in order to run the test suit included in the ''core'' library:
+
+        * Set up a test project on a local Trac server of hand. This Trac server must support BASIC authentication on the standard Trac url location.
+        
+        * Set up an user for that project with (at least) the following permissions:
+                        - WIKI_VIEW
+                        - WIKI_CREATE
+                        - WIKI_MODIFY
+                        - XML_RPC
+                
+        * Set up another user with also the following permission:
+                        - WIKI_DELETE
+
+Default username/password for these users are:
+
+        * user/user
+        
+        * admin/admin
+        
+Default url for local Trac test project is:
+
+        *  !http://localhost/trac/test
+
+
+Those settings are actually configured on source file [source:wikieditorforeclipseplugin/trunk/source/core/pom.xml#L111].
+
+Probably the best way to override these setting values is using the standard maven $HOME/.m2/settings.xml file. You can use the following snipet as base:
+
+{{{
+#!text/xml
+<settings>
+        <profiles>
+                <profile>
+                        <id>test-properties</id>
+                        <activation>
+                                <property><name>!maven.test.skip</name></property>
+                        </activation>
+                        <properties>
+                                <server.url>http://localhost/trac/test</server.url>
+                                <credentials.admin.username>admin</credentials.admin.username>
+                                <credentials.admin.password>admin</credentials.admin.password>
+                                <credentials.user.username>user</credentials.user.username>
+                                <credentials.user.password>user</credentials.user.password>                     
+                        </properties>
+                </profile>      
+        </profiles>     
+</settings>
+}}}
+
+NOTE: some TestSuites need to be run in particular order but this is not guaranteed by unit testing technology used. This is something I would like to address at some point, as it is a potential test failure cause in some particular environments. 
+
+If after setting up testing prerequisites as mentioned in this guide, automated tests still fail to run in your particular environment you can open a [http://trac-hacks.org/newticket?component=WikiEditorForEclipsePlugin&owner=ivangsa ticket] for support.
+
+Happy Hacking!!
 
 == Recent Changes ==
@@ -139 +189 @@
 {{{
 #!html
+<!-- scripts seems to be stripped -->
 <script type="text/javascript">
 var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");