1. 21 Sep, 2019 21 commits
  2. 20 Sep, 2019 6 commits
  3. 19 Sep, 2019 3 commits
  4. 18 Sep, 2019 4 commits
  5. 17 Sep, 2019 6 commits
    • Julien Muchembled's avatar
      qa: fix sort method in testResource · 8d5ced18
      Julien Muchembled authored
      The error was found with MariaDB 10.4, which returns results (of a
      request without ORDER BY) in a different order than previous versions.
      8d5ced18
    • Julien Muchembled's avatar
      ERP5SyncML: remove misuse of Transfer-Encoding: chunked · d10401d8
      Julien Muchembled authored
      We do not chunk at this level.
      
      Neither our code nor requests encodes the body this way
      and waitress (WSGI) considers the request is corrupted.
      
      It worked so far because Medusa ignores this header field.
      d10401d8
    • Kazuhiko Shiozaki's avatar
    • Ivan Tyagov's avatar
      Set int_index at Test Result creation time as it is really needed for showing... · e368cf4f
      Ivan Tyagov authored
      Set int_index at Test Result creation time as it is really needed for showing graph, test order execution in case of Scalability Tests and use int_index in scripts.
      e368cf4f
    • Ivan Tyagov's avatar
      Test Result Line do not have properly set int_index, instead title have been... · 54398666
      Ivan Tyagov authored
      Test Result Line do not have properly set int_index, instead title have been used in past. Until properly set (int_index) use current way for sorting. This is especially important for Scalability Tests's graphics.
      54398666
    • Nicolas Wavrant's avatar
      Price per quantity per slice · 05f913a0
      Nicolas Wavrant authored
      This MR introduces a second way of calculating the base price of a resource using "Base Price Quantity Step".
      
      Currently, for a resource, we could define on a Supply Line "Quantity Steps",  and set a price for each of these steps. Then, depending on the quantity of the resource, the price of the unique matching step would apply.
      
      For exemple : 
      
      | Quantity Step Range | Price for the step|
      |------------|---------|
      | 0 -> 10 | 10€ |
      | 11 -> 20 | 9€ |
      | 21 -> inf | 8€ |
      
      With the current method, for an Order of 15 products, the 2 range "11 -> 20" would apply, the unit price for the products would be 9€, and the total price would be 15*9 = 135€.
      
      The new method of calculating would apply the _Price for the step_ __to, and only to, all items of this step__. Which means, for an order of 15 products, the 10 first products would have a unit price of 10€, and the 5 next products would have a unit price of 9€, which makes in the end a total price of 145€, and a base price of 9.66€.
      
      /reviewed-on nexedi/erp5!896
      05f913a0