Log in / create account
Openbravo.com
Issues
Forge
University
View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

ERP 2.50:QA test plan 2.50/Modularity

Contents

Introduction

This document describes the QA test plan for 1st, 2nd, and 3rd iterations of Modularity project. This plan includes test of module development, module installation and new process of Initial Client Setup and Initial Organization Setup.

Test cases

Module Development

Introduction

This test cases covers the development of five modules with some dependencies among them.

Preconditions

For executing this test cases an standard 2.50 version of Openbravo ERP is required. A basic development environment will be used: A SQL Client (to execute queries) and a HTML/XML editor (a plain text editor is good enough).

1. Create "Rooms" module

View larger

The scenario is to create a basic Room Reservation system as an Openbravo ERP module.

TC01-01 - Register module

Summary: Using the Module Manager, register a new module "ROOMS".

Steps:

Issues to verify: Module is saved as "In Development". Since ROOMS (DB) and rooms (Java) are available, there is no warning message about using them.

TC01-02 - Create Tables

Summary: Creation of module database tables

Steps:

TC01-03 - Create References

Summary: Creation of module references

Steps:

TC01-04 - Add tables to Dictionary

Summary: Add the 3 tables to Application Dictionary

Steps:

TC01-05 - Add window and tabs

Summary: Create the window and the tabs

Steps:

TC01-06 - Compile

Summary: Compile to verify everything is created

Steps: 

    [java] 507  [main] ERROR org.openbravo.data.Sqlc - SQL error in query: 
    [java]         SELECT ROOMS_Roomattend.AD_Client_ID, 
    [java] (CASE WHEN ROOMS_Roomattend.AD_Client_ID IS NULL THEN ' ' ELSE  (COALESCE(TO_CHAR(table1.Name),' ') ) END) AS AD_Client_IDR, 
    [java] ROOMS_Roomattend.AD_Org_ID, 
    [java] (CASE WHEN ROOMS_Roomattend.AD_Org_ID IS NULL THEN ' ' ELSE  (COALESCE(TO_CHAR(table2.Name),' ') ) END) AS AD_Org_IDR, 
    [java] ROOMS_Roomattend.Typeattender, 
    [java] (CASE WHEN ROOMS_Roomattend.Typeattender IS NULL THEN ' ' ELSE  ( COALESCE(TO_CHAR(list1.name), ' ') ) END) AS TypeattenderR, 
    [java] ROOMS_Roomattend.Department, 
    [java] (CASE WHEN ROOMS_Roomattend.Department IS NULL THEN ' ' ELSE  ( COALESCE(TO_CHAR(list2.name), ' ') ) END) AS DepartmentR, 
    [java] ROOMS_Roomattend.C_Bpartner_ID, 
    [java] (CASE WHEN ROOMS_Roomattend.C_Bpartner_ID IS NULL THEN ' ' ELSE  (COALESCE(TO_CHAR(table3.Name),' ') ) END) AS C_Bpartner_IDR, 
    [java] ROOMS_Roomattend.Meetingrole, 
    [java] ROOMS_Roomattend.ROOMS_Roomschedule_ID, 
    [java] (CASE WHEN ROOMS_Roomattend.ROOMS_Roomschedule_ID IS NULL THEN ' ' ELSE  () END) AS ROOMS_Roomschedule_IDR,

the problem is that you do not marked one column as Identifier for ROOMS_Roomattend table.

2. Create "Required material" module

Introduction

This module is an extension to Rooms module. It will add the ability to reserve material for a meeting (like a projector, a conference-able phone, etc.). This module main extensions are:

Preconditions

This module depends of Rooms so on the system must exist a module Rooms just like described above.

TC02-01 - Register module

Summary: Using the Module Manager, register a new module "Required Material".

Steps:

Issues to verify: Module is saved as "In Development". Since RMAT_ (DB) and RMAT_(Java) are available, there is no warning message about using them.

TC02-02 - Create Tables

Summary: Creation of database tables

Steps:

TC02-03 - Create Stored procedure

Summary: Creation of stored procedure

Steps:

TC02-04 - Create Reference List

Summary: Create a reference list for table RMAT_MATERIAL

Steps:

TC02-05 - Create Reference Table

Summary: Create a reference Table RMAT_MATERIALREQUIRED

Steps

TC02-06 - Add Procedure to Application Dictionary

Summary: Add Procedure to Application Dictionary

Steps

TC02-07 - Add a message

Summary: Add new message to Application Dictionary

Steps

3. Create "Extended Material-1" module

Introduction

This module is an extension to Room Materials module. It will add some new functionality:

Preconditions

This module depends of Rooms and Required Materials modules so on the system the modules must exist.

TC03-01 - Register module

Summary: Using the Module Manager, register a new module "Extended Material".

Steps:

Issues to verify: Module is saved as "In Development". Since EXMAT1_ (DB) and EXMAT1_ (Java) are available, there is no warning message about using them.

TC03-02 - Alter Tables

Summary: Modify database tables

Steps:

4. Create "Extended Material-2" module

Introduction

This module is an extension to Rooms and Room Materials module. It will add some new functionality:

Preconditions

This module depends of Rooms, Required Materials and Extended Material modules so on the system the modules must exist.

5. Create "Room Overview" module

Introduction

This module is an extension to Rooms. It will show the information contained on the Rooms module in a more user friendly way:

Preconditions

This module depends of Rooms so on the system the modules must exist.

TC05-01 - Create View

Summary: Creation of stored view

Steps: 

CREATE OR REPLACE VIEW RVIEW_ROOMS
(ROOMS_ROOM_ID, ROOMNAME, TOPIC, RESERVATIONDATE, STARTTIME, ENDTIME, USERNAME)
AS
SELECT r.ROOMS_ROOM_ID, r.NAME AS ROOMNAME, rs.topic, rs.RESERVATIONDATE,  rs.STARTTIME, rs.ENDTIME, us.name as username
FROM ROOMS_ROOM r, ROOMS_ROOMSCHEDULE rs, ROOMS_ROOMATTEND ra, AD_USER us
WHERE r.ROOMS_ROOM_ID = rs.ROOMS_ROOM_ID
AND rs.ROOMS_ROOMSCHEDULE_ID = ra.ROOMS_ROOMSCHEDULE_ID
AND rs.AD_USER_ID = us.AD_USER_ID
ORDER BY rs.RESERVATIONDATE
TC05-02 - Register module

Summary: Using the Module Manager, register a new module "Extended Material".

Steps:

Issues to verify: Module is saved as "In Development". Since RVIEW_ (DB) and RVIEW_ (Java) are available, there is no warning message about using them.

TC05-03 - Register the view in AD

Summary: Register the view in the Application dictionary

Steps:

TC06 Create "Report Payment New" module

Introduction

This module adds a new report in the application. The report is based on a existing one, Payment report, but with more features.

Preconditions

Put the files in the corresponding java path (folders path)

TC06-01 - Register module

Summary: Using the Module Manager, register a new module "New Payment report".

Steps:

Issues to verify: Module is saved as "In Development". Since PAYREPNEW (DB) and PAYREPNEW (Java) are available, there is no warning message about using them.

TC06-02 - Create functions

Summary: Create the required functions for the reports

Steps:

TC06-03 - Create Report

Summary: Add an entry in the application dictionary for the report

Steps:

TC06-04 - Add a menu entry

Summary: Add an entry in the menu for the report

Steps:

Module Installation

Introduction

Once developed and uploaded, modules should be available for download.

Preconditions

1. Install a module from Central Repository

Summary: Use Module Manager to access Central Repository and install a new module.

Preconditions:

Steps:

Issues to verify:

2. Install a module from file system

Summary: Use Module Manager to browse for a Openbravo module file and install it.

Preconditions:

Steps:

Issues to verify:

3. Install a module with dependencies

Summary: Use Module Manager to access Central Repository and install a new module with dependencies.

Preconditions:

Steps:

Issues to verify:


4. Install a module in another language

5. Install a pack

6. Install an industry template

Module Update

Introduction

If there's available a new version of a module, it can be updated.

Preconditions

1. Update a module from Central Repository

Summary: Use Module Manager to access Central Repository and update a module that was previously installed.

Preconditions:

Steps:

Issues to verify:

Uninstall module

Introduction

Once installed, modules can be uninstalled.

Preconditions

Steps:

Issues to verify:

Installation History

Introduction

Every action performed in Module Manager is logged in Installation History.

1. Scan for updates

Summary: Use Module Manager to check if there are updated in the Central Repository, and verify that the action was logged.

Steps:

Issues to verify: 

Note: The time will depend on the momment you performed the action, and the number of updates will depend on the new versions availabe from Central Repository.

2. Install a module

Summary: Use Module Manager to install a module, and verify that the action was logged.

Steps:

Issues to verify:

Note: The time will depend on the momment you performed the action, and the number of updates will depend on the new versions availabe from Central Repository.

New Initial Client/Org Setup process

Test the two new processes.

Retrieved from "http://wiki.openbravo.com/wiki/ERP_2.50:QA_test_plan_2.50/Modularity"

This page has been accessed 10,614 times. This page was last modified on 3 April 2012, at 11:00. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.