Closed (fixed)
Project:
Commerce Discount
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Jul 2013 at 13:06 UTC
Updated:
21 May 2015 at 04:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jkuma commentedComment #2
jkuma commentedComment #3
vasikehere is a first work on rewriting the discount tests.
any feedback it's welcomed.
- Added Discount component price name (component_title) to tests.
- Added Edit and Delete UI test for commerce_discount.test
to do:
- Add Edit and Delete UI tests for commerce_discount_date, commerce_discount_usage - are they necessary???
- Add the new Discount types to tests.
- others ???
Comment #4
pcambraLooking great so far
Yes but they probably should live in the submodules.
At least two areas more: install/uninstall/enable/disable discount tests (fields are created/deleted properly) and the actual effect of the discount, i.e. creating a 20% off with and without some inline conditions actually discounts that 20%, also the new discount types should be tested as you well mention.
My call to this issue would be not to wait until have it all but committing incrementally new tests, either keeping one issue or having separated ones.
Comment #5
vasike@pcambra : thanks a lot for the feedback and i agree with you.
i also think we can commit the test patches and put the task on "needs work" state, specifying the (remained) todos.
here is a new patch which adds to previous:
- Edit UI tests for commerce_discount_date, commerce_discount_usage, Delete UI not needed (the same as for commerce_discount)
- Test for Free products Discount type.
todos:
- Free shipping Discounts test: is this needed? this Discount could be built only if we have Commerce Shipping installed
- Discount with Inline Condition test : which Inline Condition should be tested here?
- install/uninstall/enable/disable discount tests (fields are created/deleted properly)
Comment #6
joelpittetThank you for cleaning up and adding moar tests!
Does this resolve these strict errors as well?
It needs a re-roll.
Comment #7
bojanz commentedComment #8
joelpittetI've re-rolled this to see how testbot reacts.
Comment #10
joelpittetServes me right... I committed other test related patches before this.
Comment #12
joelpittetI've committed these and working on fixing the broken tests which seem to work when I test them manually with.
Working on the remaining failures here:
#2481201: Update and fix the tests!