From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.


The Quality Assurance Group (QAG) is comprised of experienced technical and functional resources within the bazaar. They work together to . The QAG takes a largely tactical role in making sure the processes of testing, CI and bug control runs smoothly. Their foremost responsibility is to provide other PMC groups with an automated testing base.

The QAG will include all the persons and companies within the bazzar interested in keep Adempiere as the most stable and tested Opensource ERP.


QAG support the goals assigned to the PMC Head according to the PMC_Structure

  • Creation and documentation of test code, test data, test scenarios, and test automation
  • Build a CI testing environment for Adempiere to support other PMC groups
  • Define and conduct tests and quality assurance
  • Define the label (status) of a release (i.e. alpha, beta, release candidate, production ready)
  • Checking and administering trackers (specially bugs and feature requests)


Responsibility delegation will be based in agreement of QAG leader and the QAG member assuming such responsibility.

Accountability of QAG leader cannot be delegated - QAG leader is accountable for all the actions and decisions taken by QAG.

  • Manage the QAG Roadmap
  • Coordinate the QAG Release schedule
  • Schedule and conduct a regular QAG session on IRC as a channel for people to escalate and also to discuss their patch or feature request
  • Define architecture for new QAG developments
  • Establish the development processes and infrastructure needed for QAG to be effective
  • Produce “how to get involved” guidelines to help new potential contributors in QAG get started
  • Facilitating code or other donations by individuals or companies to QAG
  • Working with Committers to ensure in-bound contributions are made in accordance with the ADempiere IP Policy.
  • Establish rules and guidelines for QAG
  • encourage and breed more skilled developers into QAG
  • Manage release policies for:
    • New features under development, testing code,etc..
    • high risk bug fixes
  • oversee merging proven stuff from trunk into release branch, review test code and include it in CI server
  • reverting when something goes wrong in testing code


The QAF is composed by the following key roles:

  • QA Leader, is appointed by PMC Head
  • Issue Manager,checking and administering trackers (specially bugs and feature requests)

Group Members

The QAG group is composed by the following members :

Key Roles

Becoming a Member of QAG

QAG doors are open - you can participate in anything you think can be helpful.

To become a QAG member please drop a message in forums expressing your wish, skills and availability. The corresponding QAG leader and/or PMC Head could ask for a chat to know you better.

Member Guidelines

  • In the unlikely event that a member of the QAG becomes disruptive to the process or ceases to contribute for an extended period, the member may be removed by vote of remaining QAG members, or banned by PMC Head and QAG leader(following an expected due process).
  • QAG members may resign at any time by delivering notice of their resignation to the PMC Head and QAG leader.
  • The work of the QAG is shared by the QAG members. All QAG members are expected to contribute actively.
  • Active participation in the user newsgroups and the appropriate developer mailing lists is a responsibility of all QAG members, and is critical to the success of the Project. QAG members are expected to monitor some key communication channels as Adempeire forums, wiki, IRC and PMC mailing list.

Appointing for a Key Role

Key roles are filled by PMC Head, by invitation or by examination of people appointing to position.

If you want to appoint to one of the vacant key roles just drop a message to PMC Head expressing your wish, skills and availability. PMC Head could ask for a chat and a "test period" to fill the role.


Mail List

A mail list was set up for communication between PMC members:

Link to the Archive of the List


Each message sent to the list must be marked [QA].


To coordinate meetings a google calendar was set up and QAG members can create events on such calendar.

ADempiere Calendar


Some google documents will be created and shared within QAG members (and published for community review).

Here we can maintain an index of the QAG related documents:

Index of Meeting Minutes

Objetives and Tasks

  1. Consolidate all QA documentation in a wiki page menu
  2. Review/complete QA documentation
  3. Call for help and join in forums
  4. Review new contirbutions and consolidate a team
  5. Schedule first meeting
  6. Review status of fitnesse
  7. Review status and structure of junit test
  8. Review and research Selenium, Sahi and Windmill
  9. Review and research load testing tools as Jmeter, Radview, OpenSTA,Grinder
  10. Try to get community sponsor for a performance CI test environment with millions of records, and multiple tenants
  11. Setup CI server Hudson with junit test and document
  12. Setup Fitnesse or Selenium or Sahi or Windmill with Hudson and document
  13. Setup load testing server
  14. Create rules for developers to create junit test in any new contribution
  15. Involve community into creating functional test cases with fitnesse and Selenium, base on a simple tutorial

Design and requirements

Research and documentation

CI server

Code testing

Functional testing

optimization docs of QA

Load testing