Commits

seccanj committed a480798

Release 1.5.2 (2012-10-14): Compatibility with Trac 1.0.

Comments (0)

Files changed (147)

  2) Unzip the source code distribution package
  3) Open a shell, cd into the root directory coming from the source code 
     distribution package
- 4) Build the source code using the provided buil.sh script:
+ 4) Build the source code using the provided build scripts:
+    
+    - To build for Trac 0.11:
  
-    . ./build.sh
+        . ./build_011.sh
+ 
+    - To build for Trac 0.12 and above:
+ 
+        . ./build.sh
  
     The build shell script can copy the resulting egg files into your desired 
     destination.
   On Windows:
 
  1), 2), 3) Same as for Linux
- 4) Build the source code using the provided buil.sh script:
+ 4) Build the source code using the provided build scripts:
  
-    build.cmd
+    - To build for Trac 0.11:
+ 
+        build_011.cmd
+ 
+    - To build for Trac 0.12 and above:
+ 
+        build.cmd
  
     The build shell script can copy the resulting egg files into your desired 
     destination.
 2) Open your Trac project's home page, go to the admin panel and select 
    "Plugins"
 
+Repeat steps 3) to 7) for each plugin, in the following order:
+     a) TracGenericClass
+     b) TracGenericWorkflow
+     c) TestManager
+
 3) Notice the "Install Plugin" section. Browse for your Egg file and click 
    "Install".
 
-4) Open a shell or command prompt on your Trac server machine and run the 
-   database upgrade command that will be displayed in the Trac's page.
+4) Restart your Trac server (e.g. Apache or tracd).
+
+5) Reload the Trac page in your browser.
+
+6) If Trac says that a database upgrade is needed, open a shell or 
+   command prompt on your Trac server machine and run the database 
+   upgrade command that will be displayed in the Trac's page.
    
-5) Restart your Trac server (e.g. Apache or tracd).
+7) Restart your Trac server (e.g. Apache or tracd).
 
+Check the tutorial on YouTube: http://www.youtube.com/watch?v=BIi3QMT0rT4 
+
 Test Manager plugin for Trac
 
-  Copyright 2010-2011 Roberto Longobardi
+  Copyright 2010-2012 Roberto Longobardi
   
   The Test Manager plugin for Trac is free software: you can 
   redistribute it and/or modify it under the terms of the GNU General 
   
   Project web page on Pypi: http://pypi.python.org/pypi/TestManager
 
+=======================================================================
 
 Refer to BUILD.txt for details about how to build.
 
-Refer to INSTALL.txt for installation details.
+Refer to INSTALL.txt or UPGRADE.txt for installation or upgrade 
+instructions.
 
+=======================================================================
+A Trac plugin to create Test Cases, organize them in catalogs, generate 
+test plans and track their execution status and outcome.
 
-A Trac plugin to create Test Cases, organize them in catalogs, generate test plans 
-and track their execution status and outcome.
+Since the release of Trac 1.0, I had to split the plugins code into two 
+versions:
+ - a version that works well with Trac 0.11
+ - a version that works well with Trac 0.12 and Trac 1.0
 
-The same code works well with Python 2.5, 2.6 and 2.7 and on Trac 0.11 and 0.12.
-The same egg file runs on both Trac 0.11 and 0.12.
+All the code works with Python 2.5, 2.6 and 2.7.
 All database backends are supported.
 
+***********************************************************************
+********************
+   IMPORTANT NOTE
+********************
+Starting with release 1.5.2, because of the code branch I had to do to 
+support Trac 1.0, all new features will only be developed for 
+Trac 0.12+. 
+
+The 0.11 branch will only be supported for bug fixes.
+
+***********************************************************************
+
 The Test Manager functionality is split up into three plugins:
 
 
     TracGenericClass:
     
-        This module provides a framework to help creating classes on Trac that:
+        This module provides a framework to help creating classes on 
+        Trac that:
          * Are persisted on the DB
          * Support change history
-         * Support extensibility through custom properties that the User can specify declaratively in the trac.ini file
-         * Support custom operations to be performed before and after the standard object lifecycle events.
-         * Listener interface for Components willing to be notified on any object lifecycle event (i.e. creation, modification, deletion).
+         * Support extensibility through custom properties that the User
+           can specify declaratively in the trac.ini file
+         * Support custom operations to be performed before and after 
+           the standard object lifecycle events.
+         * Listener interface for Components willing to be notified on 
+           any object lifecycle event (i.e. creation, modification, 
+           deletion).
 
-        Database tables are also automatically created by the framework as declaratively stated by the client Components.
+        Database tables are also automatically created by the framework 
+        as declaratively stated by the client Components.
          
-        Also provides an intermediate class to build objects that wrap Wiki pages and have additional properties.
+        Also provides an intermediate class to build objects that wrap 
+        Wiki pages and have additional properties.
 
 
         More details:
 
-        A generic object framework supporting programmatic and declarative definition of its standard fields, declarative definition of custom fields (in trac.ini) and keeping track of change history has been created, by generalizing the base Ticket code.
+        A generic object framework supporting programmatic and 
+        declarative definition of its standard fields, declarative 
+        definition of custom fields (in trac.ini) and keeping track of 
+        change history has been created, by generalizing the base Ticket
+        code.
 
-        The specific object "type" is specified during construction as the "realm" parameter.
-        This name must also correspond to the database table storing the corresponding objects, and is used as the base name for the custom fields table and the change tracking table (see below).
+        The specific object "type" is specified during construction as 
+        the "realm" parameter.
+        This name must also correspond to the database table storing the
+        corresponding objects, and is used as the base name for the 
+        custom fields table and the change tracking table (see below).
 
         Features:
             * Support for custom fields, specified in the trac.ini file
 
     TracGenericWorkflow:
     
-        Provides a framework to help creating workflows around any Trac Resource.
+        Provides a framework to help creating workflows around any Trac 
+        Resource.
 
         Features:
-            * Declarative definition of the workflow, specified in trac.ini.
-            * Same syntax as the basic Ticket workflow (I may have derived
-              some line of code from Trac itself... ;-))
+            * Declarative definition of the workflow, specified in 
+              trac.ini.
+            * Same syntax as the basic Ticket workflow (I may have 
+              derived some line of code from Trac itself... ;-))
             * Easy GUI integration support. You can expose the workflow 
               operation widgets anywhere in your application pages.
-            * Fine-grained authorization control. You can specify which role
-              is required to perform each state transition, and to execute
-              each corresponding action.
+            * Fine-grained authorization control. You can specify which 
+              role is required to perform each state transition, and to 
+              execute each corresponding action.
             * Custom actions. An open API allows you to program your own 
-              custom actions to be executed at any workflow state transition.
+              custom actions to be executed at any workflow state 
+              transition.
             * Out-of-the-box built-in actions are provided.
             * XML-RPC remote API.
 
         Provides the test management-related funcitonality.
         
         Features:
-            * Define test cases and organize in test catalogs (test suites).
-            * Define a hierarchy of catalogs and sub-catalogs, whatever deep.
+            * Define test cases and organize in test catalogs (test 
+              suites).
+            * Define a hierarchy of catalogs and sub-catalogs, whatever 
+              deep.
             * Test case and catalogs versioning and history of changes.
-            * Test cases and catalogs support Wiki formatting and attachments.
-            * Copy/move individual or a set of test cases among catalogs.
-            * Define one or more test plans (test rounds) based on all or a portion 
-              of the test cases in a (sub-)catalog. Specify whether the test 
-              case version should be freezed in the test plan, or always link 
-              to the latest version. 
+            * Test cases and catalogs support Wiki formatting and 
+              attachments.
+            * Copy/move individual or a set of test cases among 
+              catalogs.
+            * Define one or more test plans (test rounds) based on all 
+              or a portion of the test cases in a (sub-)catalog. Specify
+              whether the test case version should be freezed in the 
+              test plan, or always link to the latest version. 
             * One-click change status of a test case.
-            * Ticket integration: open tickets directly from a (failed) test case,
-              keep track of the relationship. Navigate froma a test case to its
-              related tickets and vice-versa.
-            * Test cases, catalogs and plans can have their own custom properties,
-              defined in trac.ini like tickets.
-            * Definition of custom test outcomes (statuses), in addition to the 
-              built-in "Untested", "Success", "Failed".
+            * Ticket integration: open tickets directly from a (failed)
+              test case, keep track of the relationship. Navigate from 
+              a test case to its related tickets and vice-versa.
+            * Test cases, catalogs and plans can have their own custom 
+              properties, defined in trac.ini like tickets.
+            * Definition of custom test outcomes (statuses), in addition
+              to the built-in "Untested", "Success", "Failed".
             * Test execution statistical charts. Export to CSV.
-            * Statistical charts about tickets related to test plans. Export to CSV.
-            * Tree and tabular view of the test catalogs or test plans, and the 
-              contained test cases.
-            * Type-ahead searching and filtering from the tree and tabular view.
-            * Breadcrumbs to easily navigate through test catalogs and plans.
+            * Statistical charts about tickets related to test plans. 
+              Export to CSV.
+            * Tree and tabular view of the test catalogs or test plans, 
+              and the contained test cases.
+            * Type-ahead searching and filtering from the tree and 
+              tabular view.
+            * Breadcrumbs to easily navigate through test catalogs and 
+              plans.
             * Integration with Trac search engine.
-            * Fina-grained security with six new Trac permissions.
-            * Create templates for test cases and test catalogs. Specify which default
-              template should be used for test cases in any particular catalog.
+            * Fine-grained security with six new Trac permissions.
+            * Create templates for test cases and test catalogs. Specify
+              which default template should be used for test cases in 
+              any particular catalog.
             * Import/export test cases from/to Excel in CSV format.
-            * National Language Support (NLS) and currently translated in Italian, 
-              French, German and Spanish.
+            * National Language Support (NLS) and currently translated 
+              in Italian, French, German and Spanish.
             * Remote APIs: XML-RPC, RESTful.
             * Python API.
               
         
-An additional plugin is only useful for debugging and should not be installed 
-in a production environment.
+An additional plugin is only useful for debugging and should not be 
+installed in a production environment.
 
     SQLExecutor:
     
-        Allows for running arbitrary SQL statements on the internal Trac database
-        from a simple web page, and see the results.
+        Allows for running arbitrary SQL statements on the internal Trac
+        database from a simple web page, and see the results.
 
 
-=================================================================================================  
+=======================================================================
 Change History:
 
-(Refer to the tickets on trac-hacks or SourceForge for complete descriptions.)
+(Refer to the tickets on trac-hacks or SourceForge for complete 
+descriptions.)
 
+Release 1.5.2 (2012-10-14):
+
+  This release makes the plugins compatible with Trac 1.0.
+  
+  Since the release of Trac 1.0, I had to split the plugins code into 
+  two versions:
+	 - a version that works well with Trac 0.11
+	 - a version that works well with Trac 0.12 and Trac 1.0
+	 
+  All the code still works with Python 2.5, 2.6 and 2.7.
+  All database backends are still supported.
+
+  To build from the source, refer to the updated BUILD.txt file.  
+
+  o Fixed Ticket #10293 (Track-Hacks): New install impossible on Trac 1.0beta1
+  
+  o Fixed Ticket #10295 (Track-Hacks): Trac detected an internal error: UnicodeError: source returned bytes, but no encoding specified
+
+  
 Release 1.5.1 (2012-08-12):
 
   This is somewhat of a major release, in that it includes several new interesting features and many bug fixes.
+Upgrade is supportred from release 1.4.7 and above only.
+
+If you have an earlier release, upgrade to 1.4.7 first and then upgrade 
+to the latest release.
+
+The functionalities are divided in three plugins, which must be installed in 
+this order:
+
+    1) Trac Generic Class => TracGenericClass
+
+    2) Trac Generic Workflow => TracGenericWorkflow
+
+    3) Test Manager => TestManager
+
+
+An additional plugin is only useful for debugging and should not be installed 
+in a production environment.
+
+    *  SQL Executor => SQLExecutor
+
+
+Upgrade:
+
+1) Download the Python Egg file (".egg" extension) which is RIGHT FOR YOUR 
+   PYTHON VERSION, or download the source code and build it.
+   Refer to BUILD.txt for instructions on how to build.
+   
+2) Open your Trac project's home page, go to the admin panel and select 
+   "Plugins"
+
+Repeat steps 3) to 7) for each plugin, in the following order:
+     a) TracGenericClass
+     b) TracGenericWorkflow
+     c) TestManager
+
+3) Notice the "Install Plugin" section. Browse for your Egg file and click 
+   "Install".
+
+4) Restart your Trac server (e.g. Apache or tracd).
+
+5) Reload the Trac page in your browser.
+
+6) If Trac says that a database upgrade is needed, open a shell or 
+   command prompt on your Trac server machine and run the database 
+   upgrade command that will be displayed in the Trac's page.
+   
+7) Restart your Trac server (e.g. Apache or tracd).
+
+8) Clear your browser's cache - needed to get the updated Javascript
+   code.
+
+mkdir bin
+
+cd tracgenericclass\0.11
+python setup.py bdist_egg
+xcopy /y dist\*.egg ..\..\bin
+
+cd ..\..\tracgenericworkflow\0.11
+python setup.py bdist_egg
+xcopy /y dist\*.egg ..\..\bin
+
+cd ..\..\sqlexecutor\trunk
+python setup.py bdist_egg
+xcopy /y dist\*.egg ..\..\bin
+
+cd ..\..\testman4trac\0.11
+
+rem python setup.py extract_messages
+rem python setup.py extract_messages_js
+rem python setup.py update_catalog -l it
+rem python setup.py update_catalog_js -l it
+rem python setup.py compile_catalog -f -l it
+rem python setup.py compile_catalog_js -f -l it
+rem python setup.py update_catalog -l es
+rem python setup.py update_catalog_js -l es
+rem python setup.py compile_catalog -f -l es
+rem python setup.py compile_catalog_js -f -l es
+rem python setup.py update_catalog -l de
+rem python setup.py update_catalog_js -l de
+rem python setup.py compile_catalog -f -l de
+rem python setup.py compile_catalog_js -f -l de
+rem python setup.py update_catalog -l fr
+rem python setup.py update_catalog_js -l fr
+rem python setup.py compile_catalog -f -l fr
+rem python setup.py compile_catalog_js -f -l fr
+
+python setup.py bdist_egg
+xcopy /y dist\*.egg ..\..\bin
+
+cd ..\..
+
+xcopy /y *.txt bin
+
+xcopy /y bin\*.egg %1\plugins
+project_path=$1
+
+mkdir bin
+
+cd tracgenericclass/0.11
+python setup.py bdist_egg
+cp dist/*.egg ../../bin
+
+cd ../../tracgenericworkflow/0.11
+python setup.py bdist_egg
+cp dist/*.egg ../../bin
+
+cd ../../sqlexecutor/trunk
+python setup.py bdist_egg
+cp dist/*.egg ../../bin
+
+cd ../../testman4trac/0.11
+
+#python setup.py extract_messages
+#python setup.py extract_messages_js
+#python ./setup.py update_catalog -l it
+#python ./setup.py update_catalog_js -l it
+#python ./setup.py compile_catalog -f -l it
+#python ./setup.py compile_catalog_js -f -l it
+#python ./setup.py update_catalog -l es
+#python ./setup.py update_catalog_js -l es
+#python ./setup.py compile_catalog -f -l es
+#python ./setup.py compile_catalog_js -f -l es
+#python ./setup.py update_catalog -l de
+#python ./setup.py update_catalog_js -l de
+#python ./setup.py compile_catalog -f -l de
+#python ./setup.py compile_catalog_js -f -l de
+#python ./setup.py update_catalog -l fr
+#python ./setup.py update_catalog_js -l fr
+#python ./setup.py compile_catalog -f -l fr
+#python ./setup.py compile_catalog_js -f -l fr
+
+python setup.py bdist_egg
+cp dist/*.egg ../../bin
+
+cd ../..
+
+cp *.txt bin
+
+cp bin/*.egg $project_path/plugins

build_wininst_011.cmd

+mkdir bin
+
+cd tracgenericclass\0.11
+python setup.py bdist_wininst
+
+cd ..\..\tracgenericworkflow\0.11
+python setup.py bdist_wininst
+
+cd ..\..\sqlexecutor\trunk
+python setup.py bdist_wininst
+
+cd ..\..\testman4trac\0.11
+python setup.py bdist_wininst
+
+cd ..\..
+
+xcopy /y *.txt bin
+
 rmdir /s /q dist 
 rmdir /s /q TracGenericClass.egg-info
 
-cd ..\..\tracgenericworkflow/trunk
+cd ..\0.11
+rmdir /s /q build 
+rmdir /s /q dist 
+rmdir /s /q TracGenericClass.egg-info
+
+cd ..\..\tracgenericworkflow\trunk
 rmdir /s /q build 
 rmdir /s /q dist 
 rmdir /s /q TracGenericWorkflow.egg-info
 
-cd ..\..\sqlexecutor/trunk
+cd ..\0.11
+rmdir /s /q build 
+rmdir /s /q dist 
+rmdir /s /q TracGenericWorkflow.egg-info
+
+cd ..\..\sqlexecutor\trunk
 rmdir /s /q build 
 rmdir /s /q dist 
 rmdir /s /q SQLExecutor.egg-info
 
-cd ..\..\testman4trac/trunk
+cd ..\..\testman4trac\trunk
+rmdir /s /q build 
+rmdir /s /q dist 
+rmdir /s /q TestManager.egg-info
+
+cd ..\0.11
 rmdir /s /q build 
 rmdir /s /q dist 
 rmdir /s /q TestManager.egg-info
 cd tracgenericclass/trunk
 rm -rf build dist *.egg-info
 
+cd ../0.11
+rm -rf build dist *.egg-info
+
 cd ../../tracgenericworkflow/trunk
 rm -rf build dist *.egg-info
 
+cd ../0.11
+rm -rf build dist *.egg-info
+
 cd ../../sqlexecutor/trunk
 rm -rf build dist *.egg-info
 
 cd ../../testman4trac/trunk
 rm -rf build dist *.egg-info
 
+cd ../0.11
+rm -rf build dist *.egg-info
+
 cd ../..

get_python_version.sh

+#!/bin/bash
+echo `python -c 'import sys; print sys.version[:3]'`
 set VER=%1
 
-zip -r testman4trac.%VER%.zip bin
+call clean.cmd
+call build_011.cmd
+zip -r testman4trac.%VER%.011.zip bin
+
+call clean.cmd
+call build.cmd
+zip -r testman4trac.%VER%.012-100.zip bin
+
+call clean.cmd
 
 mkdir testman4trac.%VER%
 
 VER=$1
 
+PY_VERSION=`./get_python_version.sh`
+
+echo $PY_VERSION
+
 . ./clean.sh
+
+. ./build_011.sh
+zip -r ../testman4trac.$VER-Py_$PY_VERSION-Trac_0.11.zip bin
+tar cvzf ../testmanager.$VER-Py_$PY_VERSION-Trac_0.11.tar.gz bin
+
+. ./clean.sh
+
 . ./build.sh
-
-zip -r ../testman4trac.$VER.zip bin
-tar cvzf ../testmanager.$VER.tar.gz bin
+zip -r ../testman4trac.$VER-Py_$PY_VERSION-Trac_0.12-1.0.zip bin
+tar cvzf ../testmanager.$VER-Py_$PY_VERSION-Trac_0.12-1.0.tar.gz bin
 
 . ./clean.sh
 

testman4trac/0.11/messages-js.cfg

+# mapping file for extracting messages from javascript files into
+# <path>/locale/messages-js.pot (see setup.cfg)
+[javascript: **.js]
+
+[extractors]
+javascript_script = trac.util.dist:extract_javascript_script
+
+[javascript_script: **.html]

testman4trac/0.11/setup.cfg

+[extract_messages]
+add_comments = TRANSLATOR:
+copyright_holder = Roberto Longobardi
+msgid_bugs_address = otrebor.dev@gmail.com
+output_file = testmanager/locale/messages.pot
+# Note: specify as 'keywords' the functions for which the messages
+#       should be extracted. This should match the list of functions
+#       that you've listed in the 'domain_functions()' call above.
+keywords = _ N_ tag_
+# Other example:
+#keywords = _ ngettext:1,2 N_ tag_
+width = 72
+
+[init_catalog]
+input_file = testmanager/locale/messages.pot
+output_dir = testmanager/locale
+domain = testmanager
+
+[compile_catalog]
+directory = testmanager/locale
+domain = testmanager
+
+[update_catalog]
+input_file = testmanager/locale/messages.pot
+output_dir = testmanager/locale
+domain = testmanager
+
+
+[extract_messages_js]
+add_comments = TRANSLATOR:
+copyright_holder = Roberto Longobardi
+msgid_bugs_address = otrebor.dev@gmail.com
+output_file = testmanager/locale/messages-js.pot
+keywords = _ N_ tag_
+mapping_file = messages-js.cfg
+
+[init_catalog_js]
+domain = testmanager-js
+input_file = testmanager/locale/messages-js.pot
+output_dir = testmanager/locale
+
+[compile_catalog_js]
+domain = testmanager-js
+directory = testmanager/locale
+
+[update_catalog_js]
+domain = testmanager-js
+input_file = testmanager/locale/messages-js.pot
+output_dir = testmanager/locale
+
+[generate_messages_js]
+domain = testmanager-js
+input_dir = testmanager/locale
+output_dir = testmanager/htdocs/js

testman4trac/0.11/setup.py

+# -*- coding: utf-8 -*-
+#
+# Copyright (C) 2010-2012 Roberto Longobardi
+# 
+# This file is part of the Test Manager plugin for Trac.
+# 
+# The Test Manager plugin for Trac is free software: you can 
+# redistribute it and/or modify it under the terms of the GNU 
+# General Public License as published by the Free Software Foundation, 
+# either version 3 of the License, or (at your option) any later 
+# version.
+# 
+# The Test Manager plugin for Trac is distributed in the hope that it 
+# will be useful, but WITHOUT ANY WARRANTY; without even the implied 
+# warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  
+# See the GNU General Public License for more details.
+# 
+# You should have received a copy of the GNU General Public License
+# along with the Test Manager plugin for Trac. See the file LICENSE.txt. 
+# If not, see <http://www.gnu.org/licenses/>.
+#
+
+from setuptools import setup
+
+extra = {} 
+
+try:
+    from trac.util.dist import get_l10n_js_cmdclass 
+    cmdclass = get_l10n_js_cmdclass() 
+    if cmdclass: # OK, Babel is there
+        extra['cmdclass'] = cmdclass 
+        extractors = [ 
+            ('**.py',                'python', None), 
+            ('**/templates/**.html', 'genshi', None), 
+            ('**/templates/**.txt',  'genshi', { 
+                'template_class': 'genshi.template:TextTemplate' 
+            }), 
+        ] 
+        extra['message_extractors'] = { 
+            'testmanager': extractors, 
+        }
+except ImportError: 
+    pass
+
+setup(
+    name='TestManager',
+    version='1.5.2',
+    packages=['testmanager','testmanager.upgrades'],
+    package_data={
+        'testmanager' : [
+            '*.txt', 
+            'templates/*.html', 
+            'htdocs/js/*.js', 
+            'htdocs/js/*.swf', 
+            'htdocs/css/*.css', 
+            'htdocs/css/blitzer/*.css', 
+            'htdocs/css/blitzer/images/*.*', 
+            'htdocs/css/images/*.*', 
+            'htdocs/images/*.*', 
+            'locale/*.*', 
+            'locale/*/LC_MESSAGES/*.mo',
+            'htdocs/testmanager/*.js'
+        ]
+    },
+    author = 'Roberto Longobardi',
+    author_email='otrebor.dev@gmail.com',
+    license='GPL v. 3. See the file LICENSE.txt contained in the package.',
+    url='http://trac-hacks.org/wiki/TestManagerForTracPlugin',
+    download_url='https://sourceforge.net/projects/testman4trac/files/',
+    description='Test management plugin for Trac',
+    long_description='A Trac plugin to create Test Cases, organize them in catalogs and track their execution status and outcome.',
+    keywords='trac plugin test case management project quality assurance statistics stats charts charting graph',
+    entry_points = {'trac.plugins': ['testmanager = testmanager']},
+    dependency_links=['http://svn.edgewall.org/repos/genshi/trunk#egg=Genshi-dev', 'http://trac-hacks.org/wiki/TestManagerForTracPluginGenericClass', 'http://trac-hacks.org/wiki/TracGenericWorkflowPlugin'],
+    install_requires=['Genshi >= 0.5', 'TracGenericClass >= 1.1.3', 'TracGenericWorkflow >= 1.0.3'],
+    **extra
+    )

testman4trac/0.11/testmanager/BUILD.txt

+
+To build the four plugins that make up the application:
+
+
+  On Linux:
+
+ 1) Make sure you have Trac installed and available in the Python lookup 
+    path. Genshi should also be available in the Python lookup path.
+    To make these libraries available to Python you can either install them
+    centrally, or reference them using the PYTHONLIB environment variable.
+ 2) Unzip the source code distribution package
+ 3) Open a shell, cd into the root directory coming from the source code 
+    distribution package
+ 4) Build the source code using the provided buil.sh script:
+ 
+    . ./build.sh
+ 
+    The build shell script can copy the resulting egg files into your desired 
+    destination.
+    If you wish to directly install the egg files under your Trac environment, 
+    you can do that
+    by providing your project root directory to the build.sh script:
+    
+    . ./build.sh path/to/your/project
+
+ 5) You will find the built egg files under the directory "bin".
+    
+    
+  On Windows:
+
+ 1), 2), 3) Same as for Linux
+ 4) Build the source code using the provided buil.sh script:
+ 
+    build.cmd
+ 
+    The build shell script can copy the resulting egg files into your desired 
+    destination.
+    If you wish to directly install the egg files under your Trac environment, 
+    you can do that by providing your project root directory to the build.sh 
+    script:
+    
+    build.cmd path\to\your\project
+    
+ 5) You will find the built egg files under the directory "bin".
+    
+
+==============================================================================
+Use the following command to clean up the build:
+
+  On Linux:
+
+    . ./clean.sh
+
+    
+  On Windows:
+    
+    clean.cmd

testman4trac/0.11/testmanager/INSTALLATION.txt

+The functionalities are divided in three plugins, which must be installed in 
+this order:
+
+    1) Trac Generic Class => TracGenericClass
+
+    2) Trac Generic Workflow => TracGenericWorkflow
+
+    3) Test Manager => TestManager
+
+
+An additional plugin is only useful for debugging and should not be installed 
+in a production environment.
+
+    *  SQL Executor => SQLExecutor
+
+
+Installation:
+
+1) Download the Python Egg file (".egg" extension) which is RIGHT FOR YOUR 
+   PYTHON VERSION, or download the source code and build it.
+   Refer to BUILD.txt for instructions on how to build.
+   
+2) Open your Trac project's home page, go to the admin panel and select 
+   "Plugins"
+
+3) Notice the "Install Plugin" section. Browse for your Egg file and click 
+   "Install".
+
+4) Open a shell or command prompt on your Trac server machine and run the 
+   database upgrade command that will be displayed in the Trac's page.
+   
+5) Restart your Trac server (e.g. Apache or tracd).
+

testman4trac/0.11/testmanager/LICENSE.txt

+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.

testman4trac/0.11/testmanager/README.txt

+Check the tutorial on YouTube: http://www.youtube.com/watch?v=BIi3QMT0rT4 
+
+Test Manager plugin for Trac
+
+  Copyright 2010-2012 Roberto Longobardi
+  
+  The Test Manager plugin for Trac is free software: you can 
+  redistribute it and/or modify it under the terms of the GNU General 
+  Public License as published by the Free Software Foundation, either 
+  version 3 of the License, or (at your option) any later version.
+  
+  The Test Manager plugin for Trac is distributed in the hope that it 
+  will be useful, but WITHOUT ANY WARRANTY; without even the implied 
+  warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  
+  See the GNU General Public License for more details.
+  
+  You should have received a copy of the GNU General Public License
+  along with he Test Manager plugin for Trac. See LICENSE.txt.
+  If not, see <http://www.gnu.org/licenses/>.
+
+
+  Project web page on TracHacks: http://trac-hacks.org/wiki/TestManagerForTracPlugin
+  
+  Project web page on SourceForge.net: http://sourceforge.net/projects/testman4trac/
+  
+  Project web page on Pypi: http://pypi.python.org/pypi/TestManager
+
+=======================================================================
+
+Refer to BUILD.txt for details about how to build.
+
+Refer to INSTALL.txt or UPGRADE.txt for installation or upgrade 
+instructions.
+
+=======================================================================
+A Trac plugin to create Test Cases, organize them in catalogs, generate 
+test plans and track their execution status and outcome.
+
+Since the release of Trac 1.0, I had to split the plugins code into two 
+versions:
+ - a version that works well with Trac 0.11
+ - a version that works well with Trac 0.12 and Trac 1.0
+
+All the code works with Python 2.5, 2.6 and 2.7.
+All database backends are supported.
+
+***********************************************************************
+********************
+   IMPORTANT NOTE
+********************
+Starting with release 1.5.2, because of the code branch I had to do to 
+support Trac 1.0, all new features will only be developed for 
+Trac 0.12+. 
+
+The 0.11 branch will only be supported for bug fixes.
+
+***********************************************************************
+
+The Test Manager functionality is split up into three plugins:
+
+
+    TracGenericClass:
+    
+        This module provides a framework to help creating classes on 
+        Trac that:
+         * Are persisted on the DB
+         * Support change history
+         * Support extensibility through custom properties that the User
+           can specify declaratively in the trac.ini file
+         * Support custom operations to be performed before and after 
+           the standard object lifecycle events.
+         * Listener interface for Components willing to be notified on 
+           any object lifecycle event (i.e. creation, modification, 
+           deletion).
+
+        Database tables are also automatically created by the framework 
+        as declaratively stated by the client Components.
+         
+        Also provides an intermediate class to build objects that wrap 
+        Wiki pages and have additional properties.
+
+
+        More details:
+
+        A generic object framework supporting programmatic and 
+        declarative definition of its standard fields, declarative 
+        definition of custom fields (in trac.ini) and keeping track of 
+        change history has been created, by generalizing the base Ticket
+        code.
+
+        The specific object "type" is specified during construction as 
+        the "realm" parameter.
+        This name must also correspond to the database table storing the
+        corresponding objects, and is used as the base name for the 
+        custom fields table and the change tracking table (see below).
+
+        Features:
+            * Support for custom fields, specified in the trac.ini file
+              with the same syntax as for custom Ticket fields. Custom
+              fields are kept in a "<schema>_custom" table
+            * Keeping track of all changes to any field, into a separate
+              "<schema>_change" table
+            * A set of callbacks to allow for subclasses to control and 
+              perform actions pre and post any operation pertaining the 
+              object's lifecycle
+            * Registering listeners, via the ITestObjectChangeListener
+              interface, for object creation, modification and deletion.
+            * Searching objects by similarity, i.e. matching any set of 
+              valorized fields (even non-key fields), applying the 
+              "dynamic record" pattern.
+              See the method list_matching_objects.
+            * Integration with the Trac Search page.
+            * Integration with the Trac Resource API.
+            * Support for declarative specification of the database 
+              backing a particular class. The tables are created 
+              automatically.
+            * Fine-grained security access control to any operation on 
+              any resource type or instance.
+
+
+    TracGenericWorkflow:
+    
+        Provides a framework to help creating workflows around any Trac 
+        Resource.
+
+        Features:
+            * Declarative definition of the workflow, specified in 
+              trac.ini.
+            * Same syntax as the basic Ticket workflow (I may have 
+              derived some line of code from Trac itself... ;-))
+            * Easy GUI integration support. You can expose the workflow 
+              operation widgets anywhere in your application pages.
+            * Fine-grained authorization control. You can specify which 
+              role is required to perform each state transition, and to 
+              execute each corresponding action.
+            * Custom actions. An open API allows you to program your own 
+              custom actions to be executed at any workflow state 
+              transition.
+            * Out-of-the-box built-in actions are provided.
+            * XML-RPC remote API.
+
+
+    TestManager:
+        
+        Provides the test management-related funcitonality.
+        
+        Features:
+            * Define test cases and organize in test catalogs (test 
+              suites).
+            * Define a hierarchy of catalogs and sub-catalogs, whatever 
+              deep.
+            * Test case and catalogs versioning and history of changes.
+            * Test cases and catalogs support Wiki formatting and 
+              attachments.
+            * Copy/move individual or a set of test cases among 
+              catalogs.
+            * Define one or more test plans (test rounds) based on all 
+              or a portion of the test cases in a (sub-)catalog. Specify
+              whether the test case version should be freezed in the 
+              test plan, or always link to the latest version. 
+            * One-click change status of a test case.
+            * Ticket integration: open tickets directly from a (failed)
+              test case, keep track of the relationship. Navigate from 
+              a test case to its related tickets and vice-versa.
+            * Test cases, catalogs and plans can have their own custom 
+              properties, defined in trac.ini like tickets.
+            * Definition of custom test outcomes (statuses), in addition
+              to the built-in "Untested", "Success", "Failed".
+            * Test execution statistical charts. Export to CSV.
+            * Statistical charts about tickets related to test plans. 
+              Export to CSV.
+            * Tree and tabular view of the test catalogs or test plans, 
+              and the contained test cases.
+            * Type-ahead searching and filtering from the tree and 
+              tabular view.
+            * Breadcrumbs to easily navigate through test catalogs and 
+              plans.
+            * Integration with Trac search engine.
+            * Fine-grained security with six new Trac permissions.
+            * Create templates for test cases and test catalogs. Specify
+              which default template should be used for test cases in 
+              any particular catalog.
+            * Import/export test cases from/to Excel in CSV format.
+            * National Language Support (NLS) and currently translated 
+              in Italian, French, German and Spanish.
+            * Remote APIs: XML-RPC, RESTful.
+            * Python API.
+              
+        
+An additional plugin is only useful for debugging and should not be 
+installed in a production environment.
+
+    SQLExecutor:
+    
+        Allows for running arbitrary SQL statements on the internal Trac
+        database from a simple web page, and see the results.
+
+
+=======================================================================
+Change History:
+
+(Refer to the tickets on trac-hacks or SourceForge for complete 
+descriptions.)
+
+Release 1.5.2 (2012-10-14):
+
+  This release makes the plugins compatible with Trac 1.0.
+  
+  Since the release of Trac 1.0, I had to split the plugins code into 
+  two versions:
+	 - a version that works well with Trac 0.11
+	 - a version that works well with Trac 0.12 and Trac 1.0
+	 
+  All the code still works with Python 2.5, 2.6 and 2.7.
+  All database backends are still supported.
+
+  To build from the source, refer to the updated BUILD.txt file.  
+
+  o Fixed Ticket #10293 (Track-Hacks): New install impossible on Trac 1.0beta1
+  
+  o Fixed Ticket #10295 (Track-Hacks): Trac detected an internal error: UnicodeError: source returned bytes, but no encoding specified
+
+  
+Release 1.5.1 (2012-08-12):
+
+  This is somewhat of a major release, in that it includes several new interesting features and many bug fixes.
+  See the list below for more details.
+  
+  In addition to that, I realized a VIDEO TUTORIAL showing out the main features of this Test Manager, to 
+  help new and existing users take confidence with recent changes, new features and so on.
+  
+  Check the tutorial on YouTube: http://www.youtube.com/watch?v=BIi3QMT0rT4 
+  
+  Also the trac-hacks user manual has been restructured, updated and enriched with the recent changes and features.
+
+  o Enhancement #353771 (SourceForge): Time tracking capability. 
+                                       
+                                       This is now possible by means of the enhancements to the tabular views of
+                                       both test catalogs and test plans and the addition of a custom field.
+                                       See the comments to the feature request and the video tutorial, where this
+                                       customization example is fully explored.
+
+  o Enhancement #3537704 (SourceForge): Possibility to select columns for the table view. 
+                                        
+                                        This is now possible from the administration panel.
+                                        
+                                        I also added an interesting feature that allows for adding a statistical
+                                        row to the test catalog and test plan tabular views, with the option to have
+                                        the sum, average or count of the values in any column, being it a standard
+                                        or a custom property of test cases or catalogs.
+                                        
+                                        This feature is also used to realize the feature #353771 above.
+                                        See the video tutorial for an interesting use of this one to track test
+                                        execution effort estimation of an entire test plan  and compare it to actual 
+                                        execution time.
+                                       
+  o Enhancement #3537700 (SourceForge): Option to select table view as default view. 
+                                        This is now possible from the administration panel.
+                                   
+  o Enhancement #3537696 (SourceForge): Possibility to change test plans. 
+                                        
+                                        This is now possible by means of several new actions available on test cases:
+                                         - On a test case definition page, you have a new action button to add the 
+                                           test case to a plan. A dialog box appears showing you the suitable plans 
+                                           (the ones not containing all test cases).
+                                         - On a test case instance (a test case inside a plan) page, you have a new 
+                                           action button to remove the test case from the plan.
+                                         - On a test case instance (a test case inside a plan) page, in case the plan
+                                           is containing an old snapshot of the test case and you wish to update its text 
+                                           description to the latest version, you have a new action button to do that.
+                                       
+  o Fixed Ticket #8932 (Track-Hacks): The test plan tabular view has been enhanced to also 
+                                      show test case full text description
+
+  o Fixed Ticket #10131 and #10217 (Track-Hacks): Deleting a Test Case, deleting Test Catalogs containing Test items.
+                                                  This only happened on PosgreSQL.
+
+  o Fixed some bugs that I found ad which were not reported:
+    - The quick search in test catalogs was not working.
+    - Indentation of test cases in tabular views for both catalogs and plans was incorrect.
+    - Localization (i.e. translation) did not work for some parts of the Administration panel, 
+      the Statistical charts page and several dialog boxes.
+    - Some more I can't recall :D
+
+Release 1.4.11 (2012-06-03):
+
+  The data referential integrity in case of test catalog, test case and test plan deletion has been enhanced.
+  Deleting a test catalog now also deletes all of the contained sub-catalogs, test cases and test plans, as well
+  as the corresponding status change history.
+
+  o Fixed Ticket #9857 (Track-Hacks): Deleted test plan is still shown in Test Stats
+
+  o Fixed Ticket #9953 (Track-Hacks): Changing a testcase custom field value gives and error
+
+  o Fixed Ticket #10043 (Track-Hacks): Deleting "zombie" TestPlans
+
+Release 1.4.10 (2012-03-03):
+
+  o Enhancement #9751 (Track-Hacks): Ability to sort catalogs.
+                                     Test Catalogs are now sorted by title in the tree and table views.
+
+  o Fixed Ticket #9776 (Track-Hacks): Testplans not visible with latest Agilo Plugin.
+
+  o Fixed Ticket #9530 (Track-Hacks): Expand all / Collapse all is not running.
+                                      This only happened with the Agilo plugin installed.
+
+  o Fixed Ticket #9754 (Track-Hacks): Setting test result seemingly succeeds with expired login.
+                                      Now operations such as setting a test case status and updating a custom field,
+                                      when failing will display a dialog box with an error message.
+  o Fixed Ticket #9758 (Track-Hacks): Can't delete Test Case in v1.4.9.
+
+Release 1.4.9 (2012-01-04):
+
+  o Enhancement #8958 (Track-Hacks): An ability to export test data to CSV format needed.
+                                     You can now export to CSV a test catalog or a test plan.
+                                     In the test catalog and test plan pages you will find an "Export ..." button.
+                                     The export format is designed to eventually import the stuff back into another 
+                                     Test Manager plugin evironment, as soon as a compatible import feature will be 
+                                     implemented :D (the current import feature is simpler than that.)
+
+  o Enhancement #9287 (Track-Hacks): New browser tab for existing testcases. Now you have an option in trac.ini to choose what
+                                     to do when clicking on a test case in the catalog/plan. 
+                                     The default is to NOT open it in a new window, but you can change that from the admin panel,
+                                     under Testmanage->Settings, or directly in the trac.ini file like this:
+                                     
+                                        [testmanager]
+                                        testcase.open_new_window = True
+
+  o Fixed Ticket #9297 (Track-Hacks): Can't print testplan table overview. There was a problem with the default print css from Trac.
+
+  o Fixed Ticket #9510 (Track-Hacks): TestStats for single Testplans at 1.4.8 not working - patched. 
+                                      Thanks so much Andreas for finding it and for patching it!!!
+
+  o Fixed Ticket #9654 (Track-Hacks): Error when creating test plans
+
+Release 1.4.8 (2011-10-23):