SOFTWARE TESTING 1

SOFTWARE TESTING PLAN

Student’s Name
Institute Affiliation
Date
SOFTWARE TESTING 2

Table of Contents
Test Plan..............................................................................................................................2

Testing Goal.....................................................................................................................2

Test Environment.............................................................................................................2

Test Types........................................................................................................................2

Test: Data Generation and Automation Tools.....................................................................3

Test Data Generation Methods........................................................................................3

Automated Test Data Generation Tools..........................................................................3

Acceptance Test...............................................................................................................3

Deploy: Versioning, Maintenance, and Environment.........................................................4

Maintenance Plan.............................................................................................................4
SOFTWARE TESTING 3

Test Plan
Testing Goal

Testing billing system integration of Xero software is the most appropriate way and

crucial for identifying the success of this software. Furthermore, since the Xero software is

essential and serves as the basis for accounting functions in the firms, it is crucial for testing the

billing system of the software (Oliinyk & Oleksiuk, 2019).

Test Environment

In the test environment, there will be testing of data, front-end running environment,

browser, database server, network, and hardware, including Server Operating System (SOS),

Client Operating System (COS) and user manuals, configuration guidelines, installation

guidelines, and other documentation related to user manuals (Mauricette, 2019). 

Test Types

The test types of the Xero software will be included with life cycle phases is linked with

at:

Phase 1: Unit testing

Phase 2: Integration Testing

Phase 3: System Testing

Phase 4: Acceptance Testing

SOFTWARE TESTING 4

Test: Data Generation and Automation Tools

Test Data Generation Methods

Testing generally consumes and produces data in a large quantity. In Xero software, most

test data are often prepared in conjunction with the test case it is meant for. However, there are

many ways in which data can be generated. This includes with;

 Manual data generation

 Large-scale data transfer between the production and test environments

 Copying in large quantities of test data from old client systems

 Tools for the Automatic Generation of Test Data (Oliinyk & Oleksiuk, 2019).

Automated Test Data Generation Tools

In Xero software, while testing data, various sets of data sets are required for which

utilization of automated test data generation tools is done.

For Xero software, “Data Transfer Mechanism (DTM)” is used as a test data generator

automation tool, a customizable application that helps in data generation. Comprises of tables

that include procedures, views for testing databases like performance testing, load testing, quality

assurance, and usability testing are done (Mauricette, 2019). 

Acceptance Test

For the acceptability of the data, acceptance testing is done.

The examples of acceptance data for Xero software is included with;

 Business Acceptance Testing (BAT)- this testing helps determine if the Xero software has

all the requirements per the business purposes and goals.

SOFTWARE TESTING 5

 Operational Acceptance Testing (OAT)- Non-functional testing is used to determine

product readiness. It focuses on recovery, compliance, maintenance, and reliability. In

addition, OAT tests a product's stability before putting it into production.

 User Acceptance Testing (UAT)- to determine if the software is working as user-friendly

and correctly too. The most often utilized client requirements are selected in UAT testing

(Redpath & Gourdie, 2017).

Deploy: Versioning, Maintenance, and Environment

Maintenance Plan

The Xero software billing system will need a maintenance plan to keep it updated,

changed, and varied to fit the firm's demands. For example, Corrective Software Maintenance

(CSM) and Adaptive Software Maintenance (ASM) are systems that may be used to maintain

software (ASM). Maintenance is required to improve Xero software performance, fix bugs and

issues, and improve overall software quality (Oliinyk & Oleksiuk, 2019).

Testing Tools

Phases Describe the Use of Suggested

Software Testing Tools

Development and Unit Testing This testing tool helps analyze the

efficiency of quality before the

software is deployed. The primary

purpose of this testing tool is to

ensure quality standards

(Mauricette, 2019). 

Integration Testing The goal of integration testing is to

SOFTWARE TESTING 6

find and fix bugs in the interplay

between the various components

(Redpath & Gourdie, 2017).

System Testing It helps in doing end-to-end testing.

But, along with that, it helps fix

maximum bugs before acceptance

testing (Oliinyk & Oleksiuk, 2019).

User Acceptance Test (UAT) This tool is used to determine

whether or not a system can meet

the needs of an end-user.

SOFTWARE TESTING 7

References
Mauricette, J. (2019). User Satisfaction with Xero Accounting Software in Auckland, New

Zealand (Doctoral dissertation, Auckland University of Technology).

Oliinyk, B., & Oleksiuk, V. (2019). Automation in software testing, can we automate anything

we want?

Redpath, J., & Gourdie, J. (2017). Issues in Converting to the Xero Accounting System Platform.