0% found this document useful (1 vote)
1K views3 pages

Test Plan Project

This document provides a test plan for testing the FrontAccounting 2.4.8 software. It outlines the test identifier, objectives, approach, items to be tested, deliverables, environment, schedule, roles and responsibilities, needs, risks, contingencies, criteria for suspending/resuming, and approval process. Black box testing will be conducted at the system level and include smoke, functional, performance, usability, UI, compatibility, and recovery testing. Key areas like sales, purchase, and inventory will be tested along with critical features, while other features will not be tested.

Uploaded by

siddhesh bhor
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (1 vote)
1K views3 pages

Test Plan Project

This document provides a test plan for testing the FrontAccounting 2.4.8 software. It outlines the test identifier, objectives, approach, items to be tested, deliverables, environment, schedule, roles and responsibilities, needs, risks, contingencies, criteria for suspending/resuming, and approval process. Black box testing will be conducted at the system level and include smoke, functional, performance, usability, UI, compatibility, and recovery testing. Key areas like sales, purchase, and inventory will be tested along with critical features, while other features will not be tested.

Uploaded by

siddhesh bhor
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

SR. NO.

ATTRIBUTE DESCRIPTION

1. Test Plan Identifier FrontAccounting_2.4.8_MTP_1.0

2. References FrontAccounting_userGuide_2.0
3. Introduction FrontAcccounting (FA) is a professional web-based
accounting system for Enterprise Resource Planning (ERP).
It is developed in PHP/Ajax using MySQL database
management system.
The recommended HTTP web Servers are a) Apache & b)
Internet Information Services (IIS).
It is targeted towards small and medium sized enterprises.

Front Accounting includes:


1)Sales:
2)Purchase:
3)Items and Inventory:

4. Approach (Strategy) Test Method:


Black Box Testing

Test Level:
System Level

Test Type:
Smoke Testing
Functional Testing

Performance Testing
Usability Testing
UI Testing
Compatibility Testing
Recovery Testing

5. Test Items Login Module


Sales
Purchase
Items and Inventory
6. Features to be tested Sales Module:
Sales Quotation Entry

Sales Quotation Enquiry:


Delivery against sales orders
Invoice against Sales Delivery
Customer Payments
Sales Order Enquiry

Purchase Module:
Purchase Order Entry
Outstanding Purchase Order Maintenance
Supplier Invoices
Payment to Suppliers
Purchase Order Enquiry

Items and Inventory Module:


Inventory Location Transfer
Inventory Item Movement
Inventory Item Status

7. Features Not to be Sales Module:


Tested Customer Transaction Enquiry
Customer and Sales Reports
Template delivery
Template Invoice
Create and Recurrent Invoices
Sales Order Entry
Direct Delivery
Direct Invoice

Purchase Module:
Direct GRN
Direct Supplier Invoice
Supplier Transaction Inquiry
Supplier and Purchasing Reports

Items and Inventory Module:


Inventory Reports

8. Test Deliverables Test Plan, Test Scenario, Test Cases, Defect Reports
9. Test Environment A Windows environment with google chrome 32.0 and
above, Mozilla Firefox 56.0 and above should be provided
to each tester.
10. Scheduling Activity Start Date End Date No. of Days
Test Scenario 29 Jan 21 2 Feb 21 4
Test Case 3 Feb 21 5 Feb 21 3
Execution 4 Feb 21 7 Feb 21 4
and Defect
Reporting
11. Roles and
Responsibilities Activity Designation Name
Test Scenario Sr. Tester Sam
Test Case Creation Sr. Tester Sam
Test Case Execution Jr. Tester John
Defect Reporting Jr. Tester John
12. Staffing and Training - Training on Defect Tracking tool i.e., Mantis
Needs - Training on ERP Domain
13. Software and Risk issue 1) Government Rules and Regulation changes
2) If we deliver faulty product to client
3) Main Features such as Performance, Usability and
security is not up to the mark.
14. Risk and Contingency 1) Natural Disaster
2) Miscommunication
3) If a developer is taking too much time to fix defect
4) Resources are not available
5) If Environment is not ready
15. Suspend and Resume 1) If Showstopper or Blocker Defect Arises
Criteria 2) If Smoke Testing is Failed
16. Item Pass Fail Criteria 1) All Test cases are executed
2) All Defects are logged]
3) Time Constraint
17. Approvals Designation Name Date and Sign
Project Manager Mr. Sam

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy