Changes between Version 38 and Version 39 of TestManagerForTracPlugin

Timestamp:

Oct 11, 2010, 2:37:07 PM (14 years ago)

Author:

Roberto Longobardi

Comment:

--

TestManagerForTracPlugin

@@ -181 +181 @@
 
 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.
-See the README.txt file for how to recreate this example.
-The following screenshot shows a custom "platform" field added to the Test Case object, and how it is presented to the User for editing.
+
+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 artifact type name followed by "-tm_custom".
+
+The test artifacts type names are the following:
+ * testcatalog
+ * testcase
+ * testplan
+ * testcaseinplan
+
+For example, the following sections in the trac.ini file define one custom property for each of the above artifacts.
+
+{{{
+    [testcatalog-tm_custom]
+    prop1 = text
+    prop1.value = Default value
+
+    [testcaseinplan-tm_custom]
+    prop_strange = text
+    prop_strange.value = windows
+
+    [testcase-tm_custom]
+    nice_prop = text
+    nice_prop.value = My friend
+
+    [testplan-tm_custom]
+    good_prop = text
+    good_prop.value = linux
+}}}
+
+'''Note: Only text property types are currently supported.'''
+
+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.'''
+
+The following screenshot shows a custom "platform" field added to the Test Case artifact, and how it is presented to the User for editing.
+
+The value is initially displayed read-only, as a label. Clicking on the pencil icon turns the label into an edit box, allowing the User to edit the value and also displays a "Save" button. Clicking the button immediately saves the new value into the database.
 
 [[BR]]