QA test plan 2.40/Heartbeat

Introduction

For statistics purposes, some data will be collected from OpenbravoERP installations, trough Heartbeat.

Aim of the project

The Openbravo heartbeat will periodically gather and send data about the Openbravo installation back to a service on Openbravo's infrastructure. This data will then be used to generate detailed reports clearly identifying where and how the Openbravo product is being utilised.

Environment

For this test execution, it will be necessary:

• At least one installation of OpenbravoERP
• In order to test different environments it is also recommended
  • Four installations of OpenbravoERP:
    • One Linux/Oracle
    • One Linux/PostgreSQL
    • One Windows/Oracle
    • One Windows/PostgreSQL

Previous data

In order to test this module, it is recommended to use BigBazaar data.

Note: Existent data can be used as well.

Heartbeat fields available

• System identifier - An identifier unique to each Openbravo installation that is generated when the heartbeat is first enabled.
• External IP Address - String generated when the heartbeat is sent (runtime)
• Activity rate - Number of logins to Openbravo in the last month. The Range will be the following: 0-1: (1-Inactive), 1-100: (2-Low), 101-500:(3-Medium), 500-1000: (4-High), 1001 or more (5-Very High).
• Complexity rate - Represents the complexity of the System. Takes into account number of Organizations where the Range is: 0-2: (1) Low, 3-6: (2) Medium, 7 or more: (3) High
• Number of registered users - Number of registered users to Openbravo
• Operative System - String from System properties (runtime)
• Operative System version - String from System properties (runtime)
• Database - String from SQL statements (runtime)
• Database version - String from SQL statements (runtime)
• Application server - String from servlet context (runtime)
• Application server version - String from servlet context (runtime)
• Web server - String from servlet context (runtime)
• Web server version - String from servlet context (runtime)
• Java version - String from System properties (runtime)
• Apache-Ant version - String (compilation time)
• Openbravo version - String (compilation time)
• Openbravo install mode - String (compilation time)

Registering fields available

• Registration Id - un-editable text field
• Company name - text field
• Company address - text box
• Contact name - text field
• Contact title - text field
• Contact email - text field
• Contact phone - number field
• Company industry - text field
• Company size in revenues (€) - number field
• Company size in number of employees - number field
• Subscribe to development News (Yes, No) -> automatic subscription to development mailing list - check box
• Subscribe to commercial News (Yes, No) -> automatic subscription to Y distribution list - check box
• Allow commercial contact (Yes, No) -> register them as a lead in Openbravo CRM system - check box

Test cases

Generic testcases

1. Look for typos on forms and windows

• Steps:
  • Navigate through all forms and read labels and messages to check spelling

Expected Result: There are no typos

2. Check for consistency

• Steps:
  • Navigate through all forms
  • Verify buttons are used in a consistent way (both within heartbeat and Openbravo ERP)
  • Verify message text and colors are used in a consistent way
  • Verify general behavior is consistent

Expected Result: There are no inconsistencies

Results

All the bugs will be reported with the prefix QA-BEAT.

• All the bugs

• Open bugs