Megatest

Artifacts Associated With Ticket ca896bc63d6c6de69ee35f0ee60155e14821b1a8

1. Ticket change [39f0bb750d] (rid 18081) by bb on 2019-07-29 18:12:46:

   1. foundin initialized to: "any"
   2. icomment:

      I tend to use "skip" state to mean "this test is not applicable", and any downstream dependencies to propagate skip (manually in the test itself).
      
      The ask:
      A new state COMPLETED/NOT_APPLICABLE
      1) a logpro rule (expect:not-applicable ... )
      2) when a test is examined to run, if any of its dependencies are COMPLETED/NOT_APPLICABLE, treat that dependency as a PASS
      
      This allows a regression where
      1) inputs are not trusted.  If the input is broken, and the design intent is that if the input is invalid, this test is not a fail, just merely not applicable, this can be implemented by a logpro rule.
      2) a flow is immature.  If an input is not ready, and the design intent is that the run passes even if some tests' input is invalid, this can be implemented by a logpro rule.
      

   3. login: "bb"
   4. mimetype: "text/x-fossil-plain"
   5. private_contact initialized to: "463e166cbd557fda643f629dd4886619ce461689"
   6. severity initialized to: "Important"
   7. status initialized to: "Open"
   8. title initialized to: "request new state/status"
   9. type initialized to: "Feature_Request"