1. 19 Feb, 2016 32 commits
  2. 18 Feb, 2016 8 commits
    • Tristan Cavelier's avatar
    • Arnaud Fontaine's avatar
      simulation: Variation Equivalence Tester tested property name should not be hardcoded. · 53475de1
      Arnaud Fontaine authored
      Instead, define default values if not set (same as previously hardcoded
      ones) and get the value(s) define on the Tester instead as we may want
      to check only variation_category_list and not variation_property_dict
      for example...
      
      Followup of: "simulation: improve equivalence testers explanations messages".
      53475de1
    • Arnaud Fontaine's avatar
      simulation: Fix typo. · 2dff3124
      Arnaud Fontaine authored
      Followup of: "simulation: improve equivalence testers explanations messages".
      2dff3124
    • Arnaud Fontaine's avatar
      simulation: Fix typo in Variation Equivalence Tester (IndexError when solving Divergences). · 447d9924
      Arnaud Fontaine authored
      Followup of: "simulation: improve equivalence testers explanations messages".
      447d9924
    • Arnaud Fontaine's avatar
      simulation: tested_property_title field was missing. · 12777c46
      Arnaud Fontaine authored
      Followup of: "simulation: improve equivalence testers explanations messages".
      12777c46
    • Arnaud Fontaine's avatar
      simulation: MultiPropertyEquivalenceTester was missing from Variation... · 60808022
      Arnaud Fontaine authored
      simulation: MultiPropertyEquivalenceTester was missing from Variation Divergence Tester Portal Type.
      
      Followup of: "simulation: improve equivalence testers explanations messages".
      60808022
    • Arnaud Fontaine's avatar
      simulation: Define getTestedProperty() on mixin rather than subclasses. · 2706a178
      Arnaud Fontaine authored
      This makes more sense as all Tester inherits from EquivalenceTesterMixin,
      even project-specific EquivalenceTester classes.
      
      Also, define getTestedProperty{List,Title}() for compatibility sake as
      they are still widely used.
      
      Followup of: "simulation: improve equivalence testers explanations messages".
      2706a178
    • Sebastien Robin's avatar
      simulation: improve equivalence testers explanations messages · b4361eb8
      Sebastien Robin authored
      With latest simulation, the explanation given to user when solving a
      divergence was not good enough :
      - Property ids were displayed without possibility to display
        business word (like displaying 'stop_date' instead of
        'Delivery Date'
      - Some message was displayed in the solve divergence dialog whatever
        was the equivalence tester behind. Therefore, customizations of
        messages made a equivalence tester level were not displayed to user
      
      Therefore, following was done:
      - in solve divergence dialog, include the message generated by the
        equivalence tester
      - use tested_property_title to allow using business words to describe
        properties having divergence
      - most equivalence testers are written in a way to evaluate divergence
        on a single property. To have better UI configuration of such equivalence
        testers, change tested_property and tested_property_title properties
        type from "lines" to "string". This required to add some backward
        compatible code.
      - use Variation Divergence Tester to show a case of an equivalence
        tester using different properties. For this, add a property sheet
        dedicated to multi properties equivalence testers
      - update propertysheets to allow translating tested_property_title
      b4361eb8