QA Processes/Installers Testing
Contents |
Introduction
This document explains the procedure for testing an Openbravo ERP installer. An installer is built when a release is ready to be published. Most common installers are on Alpha Releases, Beta Releases, Production Releases and Maintenance Packs.
Compatibility Testing
Installers are tested to work in two Operating Systems:
- Windows
- Linux
Also, the two supported databases are:
- Oracle
- PostgreSQL
When installing, it's possible to include or not include Sample data.
Finally, installation can be made on Standard or Development modes.
The 16 combination are not tested, so an heuristic picking is made. The eight tested environments are:
- Operating System: Windows
- Database engine: Oracle
- Include sample data
- Development installation
- Operating System: Windows
- Database engine: Oracle
- Do not include sample data
- Standard installation
- Operating System: Linux
- Database engine: Oracle
- Include sample data
- Standard installation
- Operating System: Linux
- Database engine: Oracle
- Do not include sample data
- Standard installation
- Operating System: Windows
- Database engine: PostgreSQL
- Do not include sample data
- Development installation
- Operating System: Windows
- Database engine: PostgreSQL
- Include sample data
- Standard installation
- Operating System: Linux
- Database engine: PostgreSQL
- Include sample data
- Standard installation
- Operating System: Linux
- Database engine: PostgreSQL
- Do not include sample data
- Standard installation
This test includes basic installation steps as described in ERP/2.50/Openbravo ERP Installation.
Steps after successfully installing:
- Login with Openbravo user.
- If installation includes sample data, create a Sales Order as described in the Acceptance Test but using Openbravo user, with BigBazaar Admin role, and choosing "Standard" Business Partner and "Standard" Product.
- If there is no sample data, just using Openbravo user, move to Application Dictionary || Table and Columns, and create a new Table.
DBSourcemanager testing
In order to verify that DBSourcemanager is working properly, the XML files stored on AppsOpenbravo/src-db/database folder should match with database model.
Steps:
- On a console window, move to AppsOpenbravo/src-db folder
- Copy the database folder to a new folder
- On Windows
C:\OpenbravoERP\AppsOpenbravo\src-db> copy database originalDatabase
- On Linux
/opt/OpenbravoERP/AppsOpenbravo/src-db> cp database originalDatabase
- Move back to AppsOpenbravo folder
- Execute a database export:
ant database.lib export.database
- Using a Diff application, compare database and originalDatabase folders
- Both folders should have no differences.
Defects revision
For defects marked as Regression and those still not verified, a verification process will be launched. For more details, see QA_Processes/Defect_life_cycle.
Test case execution
QA has three defined sets of test cases:
- Smoke Test
- Acceptance Test
- Functional Test
Main differences are:
- Complexity (Smoke the simplest, Functional the most complex)
- Coverage
- Effort
- Automation (Smoke fully automated, Functional mostly manual)
Depending of the release type, QA will pick the convenient set:
- Alpha release: Smoke Test
- Beta release: Functional Test
- Production release / Maintenance Packs: Acceptance Test