TEST PLAN
FRONT ACCOUNTING
-------------------------------------------------------------------------------------------------------------------------------------------------
1. TEST PLAN IDENTIFIER :-
FRONT ACCOUNTING Test Plan 1.0
2. REFERENCE :-
Front Accounting User Guide [Link]
3. INTRODUCTION :-
Front Accounting (FA) is a professional web-based Accounting system for Enterprise
Resource Planning (ERP). It is developed in PHP / Ajax using MySQL management system.
It is targeted towards small and medium sized enterprises. It is integrated with modules
that support most common business processes. Front Accounting is a multi-user system. It
supports multiple languages and currencies. Front Accounting is developed by an
international team. Senior developer Joe Hunt from Sweden and Janusz Dobrowolski
from Poland.
4. TEST ITEM:-
a) Login:- In the login page the users have to login using your valid user id and
password. Multiple users can login into system.
b) Sales:- In the sales module, the seller/salesman can setup a quotation entry and after
that it can be convert into sales order entry if there is an order for product from
customer's side. Then the salesman can make a delivery entry for the products which is
been dispatched to customer along with an invoice entry. After the customer does
payments the salesman can make a customer payment entry in the system for the same
c) Purchases:- In the purchase module, the Buyer makes a purchase order entry in the
system for the products he/she ordered to a supplier. Then buyer can make goods
receive entry for products that has been delivered from supplier along with a supplier
invoice entry. Then the buyer can make a supplier entry after paying the desired amount
for the products they received.
d) Items and Inventory:- In the Item and Inventory module, here the stockist/inventory
manager maintain the goods/products which are allocated at different warehouses in
different locations. Here they maintain the record of goods transferred from one location
to another location with a specific date . Here they also maintain the status of each
products at different location warehouses and the transaction details of each products
with a specific date range/duration.
1 | Page Satyam pawar
TEST PLAN
FRONT ACCOUNTING
-------------------------------------------------------------------------------------------------------------------------------------------------
d) Items and Inventory:- In the Item and Inventory module, here the stockist/inventory
manager maintain the goods/products which are allocated at different warehouses in
different locations.
Here they maintain the record of goods transferred from one location to another
location with a specific date . Here they also maintain the status of each products at
different location warehouses and the transaction details of each products with a
specific date range/duration.
5. FEATURES TO BE TESTED:-
a) Login:-
i. User login
b) SALES:-
i. Sales Quotation Entry
1. place quotation entry
2. cancel quotation entry
ii. Sales Order Entry
1. place order entry
2. cancel order entry
iii. Delivery for sales order
1. update the order details
2. Clear quantity
3. process dispatch
iv. Invoice for delivery note
1. process invoice
2. update invoice
2 | Page Satyam pawar
TEST PLAN
FRONT ACCOUNTING
-------------------------------------------------------------------------------------------------------------------------------------------------
V. Customer payment
1. add payment entry
C) PURCHASE:-
i. Purchase Order Entry
1. place order entry
2. cancel order entry
ii. Receive purchase order items (GRN)
1. update purchase order
2. process receive items
iii. Supplier Invoice Entry
enter invoice
iv. Payment to Supplier
1. enter supplier payment
d) ITEM AND INVENTORY:-
i. Inventory Location Transfer
1. process transfer
ii. Inventory Item Movements
1. Show item movement
iii. Inventory Item Status
1. search
3 | Page Satyam pawar
TEST PLAN
FRONT ACCOUNTING
-------------------------------------------------------------------------------------------------------------------------------------------------
6. FEATURES NOT TO BE TESTED
a) Manufacturing
b) Fixed Assets
c) Dimensions
d) Banking and General Ledger
e) Setup
7. TEST APPROACH:-
a) method of testing :-
i. Black-Box testing method
ii. Smoke Testing
b) Levels of testing:-
i. System Integration testing (SIT) ii. Regression Testing
c) Type of testing:-
i. Functional testing -> with all the In scope – Flows
ii. Compatibility testing in. Security testing
iv. Performance testing
v. Cross Browser Testing in (Chrome & Firefox)
8. TEST DELIVERABLES:-
a) Test Plan
b) Test Scenarios
c)Test Cases
d)Defect Summary Report / Daily Status Report
e) Issue Logs
4 | Page Satyam pawar
TEST PLAN
FRONT ACCOUNTING
-------------------------------------------------------------------------------------------------------------------------------------------------
9. TEST ENVIRONMENT:-
HARDWERE :-
RAM 8GB
PROCESSOR APPLE - M1
OPRETING SYSTEM MACoS
SERVER APACHE TOMCAT
BROWSERS GOOGLE CROME,MOZILA FIREFOX ,
SAFARI
SOFTWARE
PDF READER ADOBE PDF READER
JIRA DEFECT TRACKING TOOL
10. SCHEDULE
[Link]. TASK/ACTIVITES NO. OF DAYS DATE RANGE
1 Test plan writing 2
2 Test scenarios writing 2
3 Test case writing 4
4 Test case Execution & Defect 2
reporting
11. ROLES AND RESPONSIBLITIES
[Link] NAME OF PERSON DESIGNATION TASK/ACTIVITIES
1 SATYAM PAWAR Test plan writing
2 SATYAM PAWAR Test scenarios writing
3 Test case writing /
Execution & defect
Reporting
4 SATYAM PAWAR Test case writing /
Execution & defect
Reporting
5 SATYAM PAWAR Test case writing /
Execution & defect
Reporting
5 | Page Satyam pawar
TEST PLAN
FRONT ACCOUNTING
-------------------------------------------------------------------------------------------------------------------------------------------------
12. STAFFING AND TRAINNING :-
Training Conducted by Training conducted for Training topic
Satyam pawar Functional
walkthrough & training
of
Front Accounting
(ERP) application -
Functional flows of
below Modules:
a) Sales
b) Purchase
c) Inventory
& its sub-modules
2) Training of Jira tool to
login defects (issues)
found during test
execution by testing
team
3) Software testing
process walkthrough for
team to follow
common test standards
at
Quastech
13. SOFTWARE RISK ISSUES (Product risk):-
* Non-Availability of Test automation tools to test
* Non availability of functionally skilled testers to test the functional product
* Non availability of training on the product to the testers
14. RISK AND CONTINGENCIES (Project risk):-
* Non-availability of complete "Test Basis"
* Delay in receiving the build from Development team
* Lack of required testing resources to complete the test on time
6 | Page Satyam pawar
TEST PLAN
FRONT ACCOUNTING
-------------------------------------------------------------------------------------------------------------------------------------------------
15. SUSPEND AND RESUME CRITERIA
Suspend criteria Resume criteria
1)Show stopper defect found 1) Show stopper defect is resolved
(blocker defect ) and retested
2) Power outages 2)Power issue resolved
3) System has crashed 3) System (Hardware/Sofware) is
fixed and can be resumed
16. ITEM PASS/FAIL CRITERIA
TEST EXIT criteria:- (item pass/fail criteria)
1) All the Test Cases should be executed (with 100%
Test Coverage)
2) All the Test cases should be with Pass status post test
execution.
3) Code for all Failed testcases should be fixed /
Retested and closed.
4) Required quality of product (software) should be achieved.
5) All the Test Deliverables should be Updated with latest
content
17. APPROVEL :-
SR Name of Designation Date Remark Signature
NO. the /role (approved/unapproved)
Person
7 | Page Satyam pawar
