Cost Engine/Testing

This Wiki is read-only for reference purposes to avoid broken links.

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

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

• Bayu 2008-11-27

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
  • Market Comparison - Existing standard
• Specifications Document - Yes
  • Versioning of Document - Not Visible
  • Testing Document - Not Visible
  • Review and Feedback - Not Entirely
• Code Practice Compliance
  • In-code documentation - pending review
  • Commit to Branch - Yes
  • Backward compatible - Core code changes /core model changes
  • Impact to feature - Standard Costing
  • Reference to Document Specs - Not Specific

Issues Reference

• (link)

You are invited

• If you wish to join in please sign with (*~~~) below.