Difference between revisions of "Cost Engine/Testing"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(→Specifications and Document Review) |
(link to interopen Hudson and page) |
||
| Line 4: | Line 4: | ||
*Then we examine the best tools for a test suite. | *Then we examine the best tools for a test suite. | ||
**[http://fitnesse.org Fitnesse] is one such tool already explored by [[User:CarlosRuiz|Carlos Ruiz]] and [[User:Interopen|Ivan Calderon]]'s team at Interopen. | **[http://fitnesse.org Fitnesse] is one such tool already explored by [[User:CarlosRuiz|Carlos Ruiz]] and [[User:Interopen|Ivan Calderon]]'s team at Interopen. | ||
| + | ***Interopen has made [[PMC:QA]] page and setup with [http://www.adempiereqa.com/hudson/job/Fitnesse/ Hudson]. | ||
**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. | ||
Revision as of 18:21, 9 January 2011
Introduction
- Testing is vital and crucial as software death can happen.
- We need to examine the overall compliance to our best practice besides going through the features, requirements and 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
To come to an understanding of a scope, it is best to grasp where we are and where we want to go.
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 advanced 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 advanced 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 method beyond Standard Costing.
- In developing methods like Average Costing, e-Evolution has proposed that a complete writing of it is necessary.
- Thus the Sponsored Development: Libero Cost Engine is born.
Dictionary or Terms
- Costing Method - Standard, Average, FIFO, LIFO.
Index of Discussion Threads
(Listed in reverse chronology order - latest first)
Average Costing
- Mike Judd 2010-08-14
- Marek 2010-06-25
- Azzam Ahmad 2010-05-16
- Sanyasi 2008-02-13
- Armen Rizal 2007-06-15
- Joel S 2007-01-11
Standard Costing
Test Plan
Information gathering in progress. Please do not edit - Redhuan D. Oon
Specifications and Document Review
This part answer the question whether there exist sufficient documentation of specifications for proper review and whether the codings are in accordance to ADempiere Best Practices.
- Community Involvement - Yes
- Discussion Thread - Yes
- Critical Need - Yes /as Feature /accounts impact
- Overlap with other branches - Yes: Armen, Carlos (according to discussion threads)
- Market Comparison - Existing standard
- Specifications Document - Yes, still pending review
- Versioning of Document - Not Visible, still pending review
- Testing Document - Not Visible, still pending review
- Review and Feedback - Not Entirely, still pending review
- Code Practice Compliance
- In-code documentation - pending review
- Code naming convention - Yes, still pending review
- Follow patterns - pending review
- Commit to Branch - Yes, still pending review
- Backward compatible - Core code changes /core model changes
- Impact to feature - Standard Costing
- Reference to Document Specs - Not Specific
Use Cases
Black Box Testing
Conditional Testing
Issues Reference
- (link)
Test Suite
You are invited
- If you wish to join in please sign with (*~~~) below.
