Changes between Version 3 and Version 4 of TestManagerForTracPluginPythonApi


Ignore:
Timestamp:
Jan 20, 2011, 5:17:36 PM (13 years ago)
Author:
Roberto Longobardi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestManagerForTracPluginPythonApi

    v3 v4  
    3333                             test catalog IDs.
    3434[[BR]]
    35     Attributes:
     35    '''Attributes:'''
    3636
    3737    For the following attributes, use the dictionary assignment syntax: {{{obj['attribute_name'] = new_value}}}
     
    5050    required to test a particular condition, and the expected result.
    5151[[BR]]
    52     Attributes:
     52    '''Attributes:'''
    5353
    5454    For the following attributes, use the dictionary assignment syntax: {{{obj['attribute_name'] = new_value}}}
     
    7272    "to be executed".
    7373    The association with test cases is achieved through the
    74     TestCaseInPlan objects.
     74    !TestCaseInPlan objects.
    7575   
    76     For optimization purposes, a TestCaseInPlan is created in the
     76    For optimization purposes, a !TestCaseInPlan is created in the
    7777    database only as soon as its status is changed (i.e. from "to be
    7878    executed" to something else).
    79     So you cannot always count on the fact that a TestCaseInPlan
     79    So you cannot always count on the fact that a !TestCaseInPlan
    8080    actually exists for every test case in a catalog, when a particular
    8181    test plan has been created for it.
    8282[[BR]]
    83     Attributes:
     83    '''Attributes:'''
    8484
    8585    For the following attributes, use the dictionary assignment syntax: {{{obj['attribute_name'] = new_value}}}
     
    110110    the future.
    111111[[BR]]
    112     Attributes:
     112    '''Attributes:'''
    113113
    114114    For the following attributes, use the dictionary assignment syntax: {{{obj['attribute_name'] = new_value}}}