Difference between revisions of "Cost Engine/Case IX"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(→Transation Input) |
(→Testing Steps) |
||
Line 20: | Line 20: | ||
*The final goal of this test is to detect if the Receipt created can be reversed without error and its costing details accurate. | *The final goal of this test is to detect if the Receipt created can be reversed without error and its costing details accurate. | ||
+ | =Output Results= | ||
[[Image:AttributeSetInstanceTest.gif|thumb|centre|650px|Reversal of Purchase and Receipt of a mandatory Attribute Set Product]] | [[Image:AttributeSetInstanceTest.gif|thumb|centre|650px|Reversal of Purchase and Receipt of a mandatory Attribute Set Product]] | ||
Revision as of 04:23, 27 February 2011
Note: This Use Case is based on Libero's Cost Engine/Testing for Mandatory Attribute Set Instance.
Contents
Testing Goals
- Setting a product to mandatory Attribute Set
- Assigning it to a Purchase OrderLine
- Test complete the PO and Material Receipt
- Test Invoice Receipt
- Test non-invoiced receipt reversal
Transation Input
Two new input details are introduced into the Costing Steps For table:
- Attribute Set?
- This will call on a method to make the Apple product having a PatioSet attribute set, and PatioSet is made mandatory.
- Get Attribute Instance?
- This will call on a method to generate a new Attribute Set Instance for Apple product (or any other product as defined in the test below).
Testing Steps
- Similar to the previous steps, the only difference here is that during Purchase Order, the test shall detect the presence of a mandatory Attribute Set attached to the Product and assign its Instance ID to the OrderLine.
- During Material Receipt of the Purchase Order, its ReceiptLine also stores the Instance ID.
- The final goal of this test is to detect if the Receipt created can be reversed without error and its costing details accurate.