Changes between Version 115 and Version 116 of TestManagerForTracPlugin

Timestamp:

May 9, 2015, 2:49:13 PM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes

TestManagerForTracPlugin

@@ -7 +7 @@
 == Summary
 
-A full test management life-cycle: definition, planning, execution, statistics.
+This plugin implements a full test management life-cycle: definition, planning, execution, statistics.
 
 This test management Trac plugin can be used to create '''[wiki:TestManagerForTracPlugin#TestCases Test Cases]''', organize them in [wiki:TestManagerForTracPlugin#TestCatalogs Catalogs] and generate '''[wiki:TestManagerForTracPlugin#TestPlans Test Plans]''' to track their execution status and outcome.
@@ -25 +25 @@
  * Copy/move individual or a set of test cases among catalogs, or organize the catalogs contents easily using drag and drop.
  * '''Defining one or more test plans (test rounds) '''for each test (sub-)catalog, based on all or a portion of the test cases in a (sub-)catalog. Specifying whether the textual contents of the test cases in a plan should be frozen at the current version, or will always be linked to the latest version.
- * '''One-click changing status of a test case''' - i.e. marking a test case in a particular test plan as successful or failed.
+ * '''One-click changing status of a test case''', ie marking a test case in a particular test plan as successful or failed.
  * '''Ticket integration''': opening tickets directly from a (usually failed) test case, keeping track of the relationship. Navigating 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. All property types are supported: text, text area, listbox, radio buttons, checkbox.
@@ -59 +59 @@
  * All of the test objects, i.e. catalogs, test cases, test plans and test cases in a plan (i.e. with a status and a status change history), support:
    * '''[#Customfields Custom properties]''', which can be declared in the trac.ini file and will be available to the User for change, stored in the database and available to change listeners.
-   * Property and status change history
-   * Listener interface to be notified of object creation, modification and deletion
-   * '''[TestManagerForTracPluginWorkflow Customizable Workflow]''' state machine, declared in the trac.ini file, with the same syntax as for Ticket workflows (I may have reused some existing code here :-)
+   * Property and status change history.
+   * Listener interface to be notified of object creation, modification and deletion.
+   * '''[TestManagerForTracPluginWorkflow Customizable Workflow]''' state machine, declared in the trac.ini file, with the same syntax as for Ticket workflows.
    * '''[TestManagerForTracPluginWorkflow#Howtoprovidecustomoperations Customizable Workflow Operations]''', via a plugin api so that any component can provide its custom operations to be performed upon any workflow action, as defined in the trac.ini file.
-   * Workflow also supports a listener API for components interested in state transitions and actions performed
+   * Workflow also supports a listener API for components interested in state transitions and actions performed.
    * Workflow states also support custom properties, so to be able to convey additional context information on a workflow state and use it in listeners or directly from the database.
 
- * The developed workflow engine is able to work on any Trac Resource, it is not confined to this plugin. You can then define a workflow on any Trac resource, including Wiki pages, declaratively in the trac.ini file. You will then add a handful of custom code (for example in an ITemplateStreamFilter) to add the markup that the workflow engine generates for you to your desired Trac web page. See [wiki:TestManagerForTracPluginWorkflow#Extendworkflowsupporttoanyofyourartifacts this page] for further details.
-
-Here follows an overview of the plugin functionalities. For a brief [#Tutorialaspowerpointpresentation tutorial], refer to the [http://www.youtube.com/watch?v=BIi3QMT0rT4 Video tutorial on Youtube].
+ * The developed workflow engine is able to work on any Trac resource, it is not confined to this plugin. You can then define a workflow on any Trac resource, including Wiki pages, declaratively in the trac.ini file. You then add a handful of custom code (for example in an ITemplateStreamFilter) to add the markup that the workflow engine generates for you to your desired Trac web page. See [wiki:TestManagerForTracPluginWorkflow#Extendworkflowsupporttoanyofyourartifacts this page] for further details.
+
+For an [#Tutorialaspowerpointpresentation overview] of this plugin's capabilities, see this [http://www.youtube.com/watch?v=BIi3QMT0rT4 video].
 
 == Test Catalogs
@@ -107 +107 @@
  * '''Rename page''' button. This function is '''not allowed''' for Test Catalogs, Test Cases or Test Plans. This because the Test Manager plugin uses the page names to keep track of the test artefacts hierarchy information. Submitting a new page name will then throw you a meaningful error. '''To change the Catalog's title''', use the '''Edit this page''' button and change the first text line. It is interpreted as the catalog title. If you '''wish to move '''the object elsewhere, instead, use the 'move' Test Manager functions.
  * '''Delete this version''' button. It will delete the current Test Catalog's '''description Wiki page''', and revert to the last one. This action will have no effect on the changes you may have done to the sub-catalogs or test cases contained within. To undo changes to the Wiki pages of any of these latter objects, go to the corresponding page and work with the Wiki versions accordingly. As long as the Test Catalog internal organization in sub-catalogs and Test Case, Test Manager does not have a "Test Catalog snapshot" kind of functionality, which you may revert to.
- * '''Delete Test Catalog''' button. Pushing this button will ask you for confirmation and, if confirmed, will delete the current Test Catalog, all the contained sub-catalogs, Test Cases, Test Plans and the status history of them. '''''Caution''''': there in no undo functionality here.
+ * '''Delete Test Catalog''' button. Pushing this button will ask you for confirmation and, if confirmed, will delete the current Test Catalog, all the contained sub-catalogs, Test Cases, Test Plans and the status history of them. '''Caution''': there is no undo functionality.
 
 || [[Image(TestCatalog01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TreeviewoftheTestCatalog])]] || [[Image(TestCatalog04.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TabularviewoftheTestCatalog])]] ||
@@ -136 +136 @@
 They are implemented again as wiki pages, with a naming convention that allows the plugin code to recognize them and treat them appropriately, and with a set of auxiliary database tables. This provides out-of the box support for rich text formatting (using Wiki syntax), attachments and versioning.
 
-To add Test Cases into a Test Catalog, open the catalog, go to the bottom of the page and enter a name for the new Test Case to be created into the appropriate text box (blanks, special characters and case are supported). Then click the button '''Add a Test Case'''.  A new wiki page is generated, with a naming convention allowing the plugin code to position it correctly in the catalogs tree, and opened for editing. '''Be careful''' that the first line (the one surrounded by '==') will always be taken as the title of the Test Case, so do not remove this line. You can edit this line to change the test case title, anyway, at any time.
-
-You can then add the Test Case description just below the first line (i.e. the title), using WikiFormatting, adding attachments and everything else is supported for Wiki pages.
+To add Test Cases into a Test Catalog, open the catalog, go to the bottom of the page and enter a name for the new Test Case to be created into the appropriate text box (blanks, special characters and case are supported). Then click the button '''Add a Test Case'''. A new wiki page is generated, with a naming convention allowing the plugin code to position it correctly in the catalogs tree, and opened for editing. '''Be careful''' that the first line (the one surrounded by '==') will always be taken as the title of the Test Case, so do not remove this line. You can edit this line to change the test case title, anyway, at any time.
+
+You can then add the Test Case description just below the first line, ie the title, using WikiFormatting, adding attachments and everything else is supported for Wiki pages.
 
 When you are done, save the page '''Submit Changes''' to save your new Test Case.
 
-A Test Case is created in the context of a Test Catalog. Think of it as the '''Test Case''' "class", or "definition". It does not carry iformation about whether the Test Case was executed or when, and wheter it succeded or failed.
-
-To plan a test execution session, you will then generate a [#TestPlans Test Plan]. A Test Plan is used to record a specific execution of a set of Test Cases. Thus, a Test Cases also exists in the context of one or more Test Plans. Think of those as Test Case "instances", or "uses". In the context of the Test Manager plugin, these are called '''Test Cases in a Plan'''.
+A Test Case is created in the context of a Test Catalog. Think of it as the '''Test Case''' "class", or "definition". It does not carry information about whether the Test Case was executed or when, and whether it succeeded or failed.
+
+To plan a test execution session, generate a [#TestPlans Test Plan]. A Test Plan is used to record a specific execution of a set of Test Cases. Thus, a Test Cases also exists in the context of one or more Test Plans. Think of those as Test Case "instances", or "uses". In the context of the Test Manager plugin, these are called '''Test Cases in a Plan'''.
 
 A '''Test Case in a Plan, in addition to a basic Test Case''', also records the execution outcomes (or verdicts), ie whether a particular execution of the Test Case in the context of the containing Test Plan was successful or failing. You can also see the complete test status change history at the bottom of the Test Case in Plan page.
@@ -157 +157 @@
  * '''Show Related Tickets''' button. Clicking this button will perform a custom query listing all the Tickets related to this Test Case and, if applicable, the containing Test plan.
  * '''Move the Test Case into another catalog''' button. Only available on Test Case definitions. It allows you to cut (into a "virtual" clipboard) the test case, to be eventually pasted into some other (or the same) catalog, or sub-catalog. Push the button, then navigate to the destination catalog and puch the '''Move the copied Test Case here''' button to complete the move operation. Also look at the '''Organize Test Catalogs''' functionality for an alternative way of moving Test Cases. Refer to [#TestCatalogs Test Catalogs] for details.
- * '''Duplicate the Test Case''' button. Only available on Test Case definitions. Lets you make an exact copy of this Test Case definition. Note that the test execution statuses (i.e. successful, failed, etc.) associated to the original Test Cases in any Test Plan are not duplicated along with the Test Case definition.
+ * '''Duplicate the Test Case''' button. Only available on Test Case definitions. Lets you make an exact copy of this Test Case definition. Note that the test execution statuses, ie successful, failed, etc, associated to the original Test Cases in any Test Plan are not duplicated along with the Test Case definition.
  * '''Add to a Test Plan''' button. Only available on Test Case definitions. Allows you to add the Test Case to one or more suitable Test Plans, i.e. Test Plans that have been defined as not containing all the test cases (current and future) of the associated Test Catalog, but only a selected set of them.
  * '''Object Change History''' section. In addition to the standard Wiki versioning, test objects support their own change history, which lets you inspect who changes which property and when, also showing its old and new value. This is also particularly useful for [#Customfields Custom Fields] you may add to the test objects. See [#TestArtifactChangeHistory Test Artefact Change History] for more details.
@@ -164 +164 @@
  * '''Rename page''' button. This function is '''not allowed''' for Test Catalogs, Test Cases or Test Plans. This because the Test Manager plugin uses the page names to keep track of the test artefacts hierarchy information. Submitting a new page name will then throw you a meaningful error. '''To change the Test Case's title''', use the '''Edit this page''' button and change the first text line. It is interpreted as the test case title. If you '''wish to move '''the object elsewhere, instead, use the 'move' Test Manager functions.
  * '''Delete this version''' button. It will delete the current Test Case's '''description Wiki page''', and revert to the last one.
- * '''Delete page''' button. Pushing this button will ask you for confirmation and, if confirmed, will delete the current Test Case definition and all of the Test Case instances in any Test Plan, including their status change history. '''''Caution''''': there in no undo functionality here.
+ * '''Delete page''' button. Pushing this button will ask you for confirmation and, if confirmed, will delete the current Test Case definition and all of the Test Case instances in any Test Plan, including their status change history. '''Caution''': there is no undo functionality.
 
 || [[Image(TestCase01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#SampleTestCase])]] || [[Image(TestCase02.png_th.png, link=[wiki:TestManagerForTracPluginGallery#LateaddingaTestCasetooneormoreTestPlans])]] ||
@@ -173 +173 @@
 '''Since: 1.1.0'''
 
-A '''Test Plan''' represents a plan for a particular execution of all the Test Cases in a Test Catalog (or sub-catalog).
+A '''Test Plan''' represents a plan for a particular execution of all the Test Cases in a Test Catalog or sub-catalog.
 
 Think for example at the build verification test following a nightly build, or, for traditional projects, Functional Test and eventually Customer Verification Test.
@@ -216 +216 @@
  * '''Rename page''' button. This function is '''not allowed''' for Test Catalogs, Test Cases or Test Plans. This because the Test Manager plugin uses the page names to keep track of the test artefacts hierarchy information. Submitting a new page name will then throw you a meaningful error.
  * '''Delete this version''' button. It will delete the associated Test Catalog's description Wiki page, and revert to the last one.
- * '''Delete page''' button. Pushing this button will ask you for confirmation and, if confirmed, will delete the associated Test Catalog. Refer to [#TestCatalogs Test Catalogs] for details about what will be actually deleted. '''''Caution''''': there in no undo functionality here.
+ * '''Delete page''' button. Pushing this button will ask you for confirmation and, if confirmed, will delete the associated Test Catalog. Refer to [#TestCatalogs Test Catalogs] for details about what will be actually deleted. '''Caution''': there is no undo functionality.
 
 You have two ways of setting the execution outcome of a Test Case in a particular Test Plan (see figures below):
 
- 1. Directly from the test plan tree or tabular view, by clicking on the traffic-light icon and choosing the new color from the menu that opens. (Since 1.4.7)
+ 1. Directly from the test plan tree or tabular view, by clicking on the traffic-light icon and choosing the new color from the menu that opens. Since 1.4.7.
  1. By opening the test case first, by clicking on its name in the Test Plan tree or table, and then clicking on the corresponding traffic-light at the bottom of the page.
 
@@ -230 +230 @@
 == Moving or Copying Test Cases from one catalog to another
 
-It is also possible to move a single Test Case, or copy multiple Test Cases into a different catalog, with an experience similar to cut&paste.
+It is also possible to move one or more Test Cases into a different catalog, with an experience similar to cut&paste.
 
 As an alternative, it is also possible to ![OrganizingthecontentsofaTestCatalog graphically organize the contents of a Test Catalog] using drag&drop.
@@ -236 +236 @@
 === Moving a single Test Case
 
-To move a single Test Case from one catalog into another, you:
+To move a single Test Case from one catalog into another:
 
  1. Open the Test Case
@@ -247 +247 @@
 === Copying multiple Test Cases
 
-To copy one or more Test Cases, even from different catalogs, and paste them all together into a destination (sub-)catalog, you:
+To copy one or more Test Cases, even from different catalogs, and paste them all together into a destination (sub-)catalog:
 
  1. Open the Catalog. Expand the tree nodes as you like.
@@ -264 +264 @@
 Use '''drag and drop''' to move test cases into different catalogs or changing their order. As long as the '''Sort a test plan's test cases''' option in the Test Manager's '''Settings''' panel is set to '''User Specified''', the test cases will be displayed in the specified order when browsing the catalog and any associated test plans.
 
-''Currently, you can only move Test Cases but not Test Catalogs. In addition to that, copying is not supported yet.''
+'''Note:''' Currently, you can only move Test Cases but not Test Catalogs. In addition to that, copying is not supported yet.
 
 Click '''Save''' to submit your changes.
@@ -280 +280 @@
 The association is particularly useful when browsing the [#TestManagementandExecutionStatistics Test Management and Execution Statistics].
 
-You can specify a set of properties to control the contants of the new ticket's summary. In the {{{[testmanager]}}} section of the trac.ini file:
+You can specify a set of properties to control the contants of the new ticket's summary. In the {{{[testmanager]}}} section of the `trac.ini` file:
 
     ticket_summary_option: How to generate the ticket summary. Available options are:
@@ -308 +308 @@
 Two sample configurations follow:
 
-{{{
-#!ini
+{{{#!ini
 [testmanager]
 ticket_summary_option = fixed_text
@@ -315 +314 @@
 }}}
 
-{{{
-#!ini
+{{{#!ini
 [testmanager]
 ticket_summary_option = last_n_catalogs
@@ -329 +327 @@
  * planname: The name of the Test Plan
 
-For example, to get the test case number, you template will have something like:
+For example, to get the test case number, your template will have something like:
 
 {{{
@@ -339 +337 @@
 === Showing Tickets related to a Test Case
 
-While browsing a Test Case, either inside or outside of a Test Plan, you can list all of its related Tickets - i.e. the Tickets that were opened using the above '''Open a Ticket on this Test Case''' button.
+While browsing a Test Case, either inside or outside of a Test Plan, you can list all of its related Tickets, ie the Tickets that were opened using the above '''Open a Ticket on this Test Case''' button.
 
 To do this, just browse the Test Case and '''click on the Show Related Tickets button'''.
 
-If you are browsing a Test Case "definition", i.e. from a Test Catalog, you will be shown all of the Tickets opened against the Test Case '''in any Test Plan'''.
+If you are browsing a Test Case "definition", ie from a Test Catalog, you will be shown all of the Tickets opened against the Test Case '''in any Test Plan'''.
 
 If you are instead browsing a Test Case in a specific Test Plan, you will be shown all of the Tickets opened against the Test Case '''in that specific Test Plan'''.
@@ -439 +437 @@
 You can export to CSV format a Test Catalog or a Test Plan.
 
-In the Test Catalog and Test Plan pages you will find an "Export ..." button.
+In the Test Catalog and Test Plan pages you will find an "Export..." button.
 
 The export format is designed for you to elaborate your external statistics, but also 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).
@@ -481 +479 @@
 Custom fields can be added to the four test objects and to the [wiki:TestManagerForTracPluginWorkflow workflow] state object, by declaring them in the trac.ini file.
 
-The syntax is the same used for custom Ticket properties, only the name of the ini file sections are specific: you must use the test artefact type name followed by "-tm_custom".
+The syntax is the same used for custom Ticket properties, only the name of the `trac.ini` file sections are specific: you must use the test artefact type name followed by "-tm_custom".
 
 The test artefacts type names are the following:
@@ -490 +488 @@
  * testcaseinplan
 
-For example, the following sections in the trac.ini file define custom properties for each of the above artefacts.
-
-{{{
-#!ini
+For example, the following sections in the `trac.ini` file define custom properties for each of the above artefacts.
+
+{{{#!ini
 [testcatalog-tm_custom]
 remarks = text
@@ -527 +524 @@
 Once defined in the trac.ini file as above, custom fields will be available to the User for browse and for editing in the Web page, as shown next.
 
-'''Note: Editing custom properties requires the TEST_MODIFY permission.'''
+'''Note''': Editing custom properties requires the TEST_MODIFY permission.
 
 The following screenshot shows a custom "platform" field added to the Test Case artefact, and how it is presented to the User for editing.
@@ -545 +542 @@
 The default outcomes are configured in trac.ini at plugin installation (or upgrade) time as follows:
 
-{{{
-#!ini
+{{{#!ini
 [test-outcomes]
 green.successful = Successful
@@ -553 +549 @@
 default = to_be_tested
 }}}
+
 You can '''customize the outcomes''' at any moment by adding new outcomes, or modify the descriptions of the current ones. Do not delete previous outcomes if you have already assigned them to any of your test cases.
 
 For example, to add a new outcome named "It's a Mess!!!" to the failures, add a line like the following, in trac.ini:
 
-{{{
+{{{#!ini
 red.bigmess = It's a Mess!!!
 }}}
@@ -575 +572 @@
 Every object which has a workflow defined is created in a "new" state, so every transition should consider this as the first state in the state machine.
 
-This is a sample content of the trac.ini file to associate a workflow to the Test Case object. [[BR]]
-
-{{{
-#!ini
+This is a sample content of the trac.ini file to associate a workflow to the Test Case object:
+
+{{{#!ini
 [testcase-resource_workflow]
 review = new,changes_requested -> under_review
@@ -604 +600 @@
 Your quality process may require your test catalogs and test cases to follow particular templates. With the Test Manager, you can define templates for your test catalogs and your test cases. When you create a new test catalog or test case, their description will be filled with the templates you have defined.
 
-To create templates, open the '''Administration''' tab and go to the '''Test Manager -> Templates '''section.
+To create templates, open the '''Administration''' tab and go to the '''Test Manager -> Templates''' section.
 
 [[Image(Templates01.png_th.png, link=[wiki:TestManagerForTracPluginGallery#TheTemplatesmanagementsectionintheTestManagerAdministrationpanel])]]
@@ -671 +667 @@
  * Number of days between each data point: determines the scale, or granularity, of the charts, in terms of days per single piece of data.
 
-In alternative to using the administration panel, you can directly edit the trac.ini file:
-
-{{{
-#!ini
+In alternative to using the administration panel, you can directly edit the `trac.ini` file:
+
+{{{#!ini
 [testmanager]
 default_days_back = <number of days back from today>
@@ -682 +677 @@
 For example:
 
-{{{
-#!ini
+{{{#!ini
 [testmanager]
 default_days_back = 14
@@ -733 +727 @@
 == Tutorial
 
-'''TODO:''' These tutorials document release 1.0.3 and so need to be updated with the Test Plan and other recent features. Refer to the '''[http://www.youtube.com/watch?v=BIi3QMT0rT4 Video tutorial on Youtube]''' for more up-to-date information.
+'''TODO:''' These tutorials document release 1.0.3 and so need to be updated with the Test Plan and other recent features. Refer to the '''[http://www.youtube.com/watch?v=BIi3QMT0rT4 video tutorial on Youtube]''' for more up-to-date information.
 
  * attachment:"UserGuide_part_1.ppt"
@@ -773 +767 @@
 '''Trac 0.12 and 1.x are supported''', and also '''Python 2.6 and 2.7'''.
 
-'''Note:''' If you are using '''MySQL''' or '''PosgreSQL''', the database user must have read access to the trac.ini file.
+'''Note:''' If you are using '''MySQL''' or '''PosgreSQL''', the database user must have read access to the `trac.ini` file.
 
 The plugin can be installed as usual, from the Trac administration panel, and requires a database upgrade.
@@ -805 +799 @@
 
 Try this from the command line:
-
-{{{
+{{{#!sh
 python -c "import pkg_resources"
 }}}
-If you get no output, setuptools is installed. Otherwise, you'll need to install it before plugins will work in Trac.
+
+If you get no output, then setuptools is installed. Otherwise, you'll need to install it before plugins will work in Trac.
 
 '''Did you get the correct version of the Python egg?'''
 
-Python eggs have the Python version encoded in their filename. For example, `TestManager-1.0.0-py2.7.egg` is an egg for Python 2.7, and will not be loaded if you're running a different Python version (such as 2.5 or 2.6).
+Python eggs have the Python version encoded in their filename. For example, `TestManager-1.0.0-py2.7.egg` is an egg for Python 2.7, and will not be loaded if you're running a different Python version, such as 2.5 or 2.6.
 
 Also, verify that the egg file you downloaded is indeed a ZIP archive and not the HTML preview page instead.
@@ -822 +816 @@
 
  * you actually added the necessary lines to the [components] section:
-{{{
-#!ini
+{{{#!ini
 [components]
 tracgenericclass.* = enabled
@@ -830 +823 @@
 }}}
  * the package/module names are correct
- * the value is "enabled", not e.g. "enable"
+ * the value is "enabled", not "enable"
 
 '''Check the permissions on the egg file and on the trac.ini file'''
@@ -836 +829 @@
 The user user to run Trac (either tracd or Apache) must be able to read the egg files.
 
-Also, it's been reported that for PosgreSQL also its user must be able to read trac.ini.
+It has been reported that for PosgreSQL also its user must be able to read the `trac.ini` file.
 
 '''Check the log files'''
@@ -854 +847 @@
 Only one version of the plugin can be loaded for each running Trac server (ie each Python process). The Python namespaces and module list will be shared, and it cannot handle duplicates. Whether a plugin is enabled or disabled makes no difference.
 
-A globally installed plugin (typically setup.py install) will override any version in global or project plugins directories. A plugin from the global plugins directory will be located before any project plugins directory.
+A globally installed plugin, typically setup.py install, will override any version in global or project plugins directories. A plugin from the global plugins directory will be located before any project plugins directory.
 
 '''If your Trac server hosts more than one project''' (as with TRAC_ENV_PARENT_DIR setups), then having two versions of a plugin in two different projects will give uncertain results. Only one of them will load, and the one loaded will be shared by both projects. Trac will load the first found - basically from the project that receives the first request.
 
-Having more than one version listed inside Python site-packages is fine (ie. installed with setup.py install) - setuptools will make sure you get the version installed most recently. However, '''don't store more than one version inside a global or project plugins directory''' - neither version number nor installed date will matter at all. There is no way to determine which one will be located first when Trac searches the directory for plugins.
+Having more than one version listed inside Python site-packages is fine, ie installed with `setup.py` install, as setuptools will make sure you get the version installed most recently. However, '''don't store more than one version inside a global or project plugins directory''': neither version number nor installed date will matter. There is no way to determine which one will be located first when Trac searches the directory for plugins.
 
 '''Have you restarted Apache?'''
@@ -866 +859 @@
 '''If all of the above failed'''
 
-OK, so the logs don't mention these plugins, the egg is readable, the python version is correct and the egg has been installed globally (and is enabled in the trac.ini), you restarted Apache and it still doesn't work or give any error messages or any other indication as to why?
+OK, so the logs don't mention these plugins, the egg is readable, the python version is correct and the egg has been installed globally (and is enabled in the trac.ini file), you restarted Apache and it still doesn't work or give any error messages or any other indication as to why?
 
 Open a ticket here. The plugins maintainers watch ticket notifications continuously.
@@ -879 +872 @@
 
 '''Author:''' [wiki:seccanj] [[BR]] 
-'''Maintainer:''' [wiki:seccanj] [[BR]] 
+'''Maintainer:''' [[Maintainer]] [[BR]] 
 '''Contributors:'''