Difference between revisions of "Cost Engine/Testing"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(suggesting a test plan roadmap for Cost Engine) |
(change of topics) |
||
Line 5: | Line 5: | ||
**Fitnesse expands the concept of testing to be more bazaar like and allow anyone out there to test easily, diversely and constantly. | **Fitnesse expands the concept of testing to be more bazaar like and allow anyone out there to test easily, diversely and constantly. | ||
− | = | + | =Scope Deliberation= |
+ | ==General Proposition of an ERP== | ||
+ | *The essence of a modern ERP today lies in its Financials Integration | ||
+ | *The core of that is the Costing Engine that fulfills Cost Accounting requirements | ||
+ | *A Costing Engine is a highly challenging module to develop and even SAP cannot perfectly resolve all scenarios. | ||
+ | *ADempiere seeks to resolve the most common terms of such use, such as Average Costing with Average Invoicing, FiFO and LiFO. | ||
+ | ==State of Affairs== | ||
+ | *Compiere, which ADempiere inherits from does not have a complete costing feature beyond [[Standard Costing]]. | ||
+ | *In developing [[Average Costing]], e-Evolution has proposed that a complete writing of it is necessary. | ||
=Test Plan= | =Test Plan= |
Revision as of 23:43, 8 January 2011
Contents
Introduction
- Testing is vital and crucial as software death can happen.
- Firstly we write out a feature specifications within a test plan.
- Then we examine the best tools for a test suite. Fitnesse is one such tool already explored by Carlos Ruiz and Ivan Calderon's team at Interopen.
- Fitnesse expands the concept of testing to be more bazaar like and allow anyone out there to test easily, diversely and constantly.
Scope Deliberation
General Proposition of an ERP
- The essence of a modern ERP today lies in its Financials Integration
- The core of that is the Costing Engine that fulfills Cost Accounting requirements
- A Costing Engine is a highly challenging module to develop and even SAP cannot perfectly resolve all scenarios.
- ADempiere seeks to resolve the most common terms of such use, such as Average Costing with Average Invoicing, FiFO and LiFO.
State of Affairs
- Compiere, which ADempiere inherits from does not have a complete costing feature beyond Standard Costing.
- In developing Average Costing, e-Evolution has proposed that a complete writing of it is necessary.