Megatest

Artifacts Associated With Ticket 9b82775b936561bcd14c12f6e4121c39469291df

1. Ticket change [e8f230f274] (rid 3674) by mrwellan on 2013-04-09 12:22:03:

   1. comment initialized to:

      <verbatim>
      1.	Config file includes are done relative to the location of the first config file
      
      If foo/bar.config contains:
      [include configs/nada.config] 
      
      and configs/nada.config contains:
      [include blah/fuz.config]
      
      Then fuz.config would need to be at foo/blah/fuz.config
      
      2.	Config file includes are done relative to the location of the currently being processed config
      
      In the example above fuz.config would be found at foo/configs/blah/fuz.config
      
      3.	Config file includes are required to be absolute e.g.
      
      #{getenv MT_RUN_AREA_HOME}/foo/configs/blah/fuz.config
      
      Which policy do you want going forward? I'll ensure we adhere to whatever we choose from here on out. My current test suite assumes policy #3 but I'm fine with supporting either #1 or #2.
      </verbatim>
      

   2. severity initialized to: "Important"
   3. status initialized to: "Open"
   4. title initialized to: "config file relative path handling policy"
   5. type initialized to: "Feature_Request"

2. Ticket change [7040bb0c75] (rid 3725) by mrwellan on 2013-04-12 09:16:58:

   1. Appended to comment:

      
      
      <hr /><i>mrwellan added on 2013-04-12 15:16:58 UTC:</i><br />
      Current policy and Megatest behavior is to store the link path to the test.
      

   2. priority changed to: "Immediate"
   3. resolution changed to: "Open"
   4. status changed to: "Closed"