Test Plan

For Online Real Estate System

Version 1.0

Submitted to Instructor Mikiyas

Department of Software Engineering

Group Project for Software Testing
Arbaminch University
Table of Contents
1. Test Plan Identifier................................................................................................................................3
2. Introduction...........................................................................................................................................3
3. Item To be Tested..................................................................................................................................3
5. Features to be tested..............................................................................................................................4
6. Approach................................................................................................................................................4
6.1 Unit Testing.......................................................................................................................................4
6.2 Integration testing..............................................................................................................................5
6.3 White box testing...............................................................................................................................5
6.4 Black box testing...............................................................................................................................5
6.5 Acceptance Testing (Alpha & Beta Testing).....................................................................................5
6.5.1 Alpha Testing.............................................................................................................................5
6.4.2 Beta Testing................................................................................................................................6
7. Test Case............................................................................................................................................6
7.1 Test Case 1: Create New Request......................................................................................................6
7.2 Test Case 2: Search Real Estate.........................................................................................................6
7.3 Test Case 3: Maintain User Information............................................................................................6
7.4 Test Case 4: Create New Real Estate.................................................................................................6
7.5 Test Case 5: Update Real Estate........................................................................................................6
7.6 Test Case 6: Maintain Location information......................................................................................7
7.7 Test Case 7:.......................................................................................................................................7
A. Create new Employee.....................................................................................................................7
B. Maintain Employee.........................................................................................................................7
8. Item Pass/Fail Criteria..........................................................................................................................7
9. Suspension Criteria and Resumption Requirements..........................................................................7
10. Test deliverables..................................................................................................................................7
11. Testing Tasks.......................................................................................................................................8
11.1 Test Planning...................................................................................................................................8
11.2 Allocation and Assignment of Personnel to the testing Sub-Project................................................8
11.3 Test Analysis and Design................................................................................................................8
11.4 Test Specification............................................................................................................................8
11.5 Test Data preparation.......................................................................................................................8
12. Environment Needs.............................................................................................................................8
12. Responsibilities....................................................................................................................................8
2.1 Quality assurance (QA) team.............................................................................................................8
2.2 Tester.................................................................................................................................................8
2.3 Project Director.................................................................................................................................8
2.4 Project Manager................................................................................................................................8
2.5 Test Manager.....................................................................................................................................8
2.6 Test Team..........................................................................................................................................8
2.7 Quality Manager................................................................................................................................8
13.Staffing and Training Needs....................................................................................................................9

1. Test Plan Identifier

TestPlan- REMS-V1.0

2. Introduction
Real Estate Management System (REMS) is an online real estate software application that
manages the overall operational activities and processes, starting from the management of the
property, to the management of real estate agencies, agents, clients and financial transactions. It
provides comprehensive reports for managing the Real Estate agency performance and
efficiency, and enables the management for a better decision-making.
The purpose of this document is to outline the testing plan for testing the critical use cases and
functionalities that are described in the Vision Document of the Online Real Estate System
(ORES).
3. Item To be Tested
The critical use case requirements (section 3.2 of Vision Document) are the items to be tested.
They are as follow:
 Create New Request.
 Search Real Estate.
 Maintain User Information.
 Create New Real Estate.
 Update Real Estate.
 Maintain Location information.
 Create new Employee.
 Maintain Employee.

5. Features to be tested
This section outlines all features that will be tested from the Vision Document.
Feature Identifier Description Requirements Number
T-001 Create New Request 3.2.1
T-002 Search Real Estate 3.2.2
T-003 Maintain User Information 3.2.3
T-004 Create New Real Estate 3.2.4
T-005 Update Real Estate 3.2.5
T-006 Maintain Location information 3.2.6
T-007 Create new Employee 3.2.7
T-008 Maintain Employee 3.2.8

6. Approach
The following software testing techniques were used in order to uncover errors in the Real Esatate
Management System:

6.1 Unit Testing

Unit testing is normally considered as an adjunct to the coding Step. It focuses verification effort on the
smallest unit of the software design. It has been conducted within the programming area. The individual
units have been tested in isolation and written to meet the specification of requirements, including any
requirement to interact with other units in the system. Unit testing is the test for the small units of
code, e.g. programs, modules or procedures in order to ensure that they perform their intended
functions. All possible Paths through control structure were exercised at least once. Unit testing
is also done to test data the data flow across a module interface.

The following errors were uncovered during the unit testing.

 Comparison of different data types.
 Incorrect logical operators or precedence.
 Incorrect comparison of variables.
 Improper or nonexistence loop termination.
  Improperly modified lop variables.

6.2 Integration testing

Integration testing is a systematic technique for constructing the program structure while at the
same time conducting tests to uncover errors associated with the interfacing. During this activity,
unit tested components were taken and a program structure were built per the design. Then
incremental integration was performed on the system. This means that programs were
constructed and tested in small increments instead of testing the entire program as a whole. This
was done because corrections of errors become difficult in case of whole program testing is done
and it is not easy to correct them at one go. Thus, through incremental integration testing, any
error uncovered could be easily noted and corrected and interfaces were tested completely.
6.3 White box testing
White box testing is also called as glass box testing. It is related with the structure of the
program. It helps in uncovering many errors that black box testing cannot. During White box
testing activity, every statement of the program is executed at least once. All independent paths
were also executed. Every logical decision was executed to check both true and false conditions.
All loops were executed at their boundaries and within their operational bounds. Validation
checks were also done during this process.
6.4 Black box testing
Black box testing also called as behavioral testing, focuses on the functional requirements of the
software. It is related to input and output only and not relate with the internal structure of the
program. This testing is also done to finds errors such as:
 Initialization and termination errors.
 Behavioral and performance errors.
 Incorrect or missing functions.
 Interface errors.
 Errors in data structure and external database access.
 Performance errors.

6.5 Acceptance Testing (Alpha & Beta Testing)

An acceptance test is a test carried out by the customer or end user rather then the developer in
order to enable the customer to validate all requirements. Alpha testing and beta testing are two
types of acceptance tests that were conducted.
6.5.1 Alpha Testing
Alpha test is conducted in a controlled environment. As a matter of fact, the end user conducts
alpha test at the developer’s site. But since I’m the developer and this system has been developed
at the company’s site itself, it is assumed that alpha test has been conducted at the company’s
site. During the course of the system development, the end user was operating the software in my
presence and I was recording the errors that were occurring and other problems that were coming
up. Rectification was made accordingly.
6.4.2 Beta Testing
Beta testing was also conducted at the company site by the end user, but in my absence. Here the
end user himself recorded all the problems that he had encountered during testing the system and
then reported to me at regular intervals. As a result of problem reported during beta testing,
modifications were made to overcome the problems.
7. Test Case
7.1 Test Case 1: Create New Request
 Incorrect input: An empty requirement field. (Name, Email, Property information).
 Pass criteria: An appropriate error message should be displayed and the customer should
not be allowed to make the request.
 Correct input: Fill in all required fields in correct format.
 Pass criteria: The user should be directed to the confirmation page.
7.2 Test Case 2: Search Real Estate
 Incorrect input: An empty requirement field. (Real Estate type, city, region, street).
 Pass criteria: An appropriate error message should be displayed and the customer should
not be allowed to be directed to the result page.
 Correct input: Fill in all required fields in correct format.
 Pass criteria: If the all required fields are correctly filled then the customer should be
directed to the result page.
7.3 Test Case 3: Maintain User Information
 Incorrect input: An empty required field. (Full Name, Email, Phone, Address).
 Pass criteria: An appropriate error message should be displayed and the employee should
not be allowed to confirm the task.
 Correct input: fill in all required fields in correct format.
 Pass criteria: the employee will be allowed to confirm the maintained information.
7.4 Test Case 4: Create New Real Estate
 Incorrect input: missing a required field of the property.
 Pass criteria: An appropriate error message should be displayed and the employee should
not be allowed to complete the process.
 Correct input: fill in all required fields in correct format.
 Pass criteria: the employee will be allowed to submit the real estate information and the
real estate information should be added to the database.
7.5 Test Case 5: Update Real Estate
 Incorrect input: missing a required field of the property.
 Pass criteria: An appropriate error message should be displayed and the employee should
not be allowed to update the Real estate.
 Correct input: fill in all required fields in correct format.
 Pass criteria: the real estate information should be updated in the database.
7.6 Test Case 6: Maintain Location information
 Incorrect input: missing the location field.
 Pass criteria: An appropriate error message should be displayed and the manager should
not be allowed to add or update the real estate location.
 Correct input: filling the location field.
 Pass criteria: the manager should be directed to the confirmation page.
7.7 Test Case 7:
A. Create new Employee
 Incorrect input: An empty requirement field. (User Name, Password).
 Pass criteria: an appropriate error message should be displayed and the manager should
not complete the new account.
 Correct input: fill in all required fields in correct format.
 Pass criteria: the manager should be directed to the confirmation page.
B. Maintain Employee
 Incorrect input: An empty requirement field. (User Name, Password).
 Pass criteria: an appropriate error message should be displayed and the manager should
not complete the process.
 Correct input: fill in all required fields in correct format.
 Pass criteria: the employee information should be deleted/ updated in the database.

8. Item Pass/Fail Criteria

The testing of the REMS will be considered pass when the test cases meet the specific
requirements in the Vision Document. A fail test is flagged if a test case does not meet the
actions mentioned in the document.

9. Suspension Criteria and Resumption Requirements

If a test case failed, the code of its part will be resolved. Testing for the failed test case will
resume after the bug has been fixed.

10. Test deliverables

The following artifacts will be produced after the tests are conducted on the REMS:
 Test Plan.
 Test Cases.
 Test Log.
 Incident Reports
 Test Report
 Release Notes.
11. Testing Tasks
11.1 Test Planning
To be done by the Test Manager in consultation with the Development Team, Trust and
Authority
11.2 Allocation and Assignment of Personnel to the testing Sub-Project
Test Manager to request personnel from Program Manager and Product Development Manager
11.3 Test Analysis and Design
This will be done by the Test Department in consultation with the Product Development
Manager and the Program Manager
11.4 Test Specification
Separate Document
11.5 Test Data preparation
A mixture of test and live data will be used, with the live data coming in towards the end of the
test cycle. Live data will be anonymized if necessary.

12. Environment Needs

All tests will be done by an Intel machine running Windows XP operating system and using Java
Development Kit 1.7.0, Eclipse with NUnit testing environment.

12. Responsibilities
2.1 Quality assurance (QA) team
Responsible for preparing test cases, test data and expected results in each Test Stage
2.2 Tester
Responsible for who will execute the testing.
2.3 Project Director
The Project Director (PD) ultimately is responsible for the final decision on all Test and
Evaluation issues.
2.4 Project Manager
The Project Manager (PM) is responsible for confirming Test and Evaluation results.
2.5 Test Manager
The Test Manager (TM) is responsible for overseeing the Test and Evaluation process, including
creating test plans, execution, review, and coordinating acceptance.
2.6 Test Team
The Test Team is responsible for testing or assisting with testing of the Prime Contractor's
system.
2.7 Quality Manager
The Quality Manager (QM) monitors the prime contractor’s testing efforts and participates in
any reviews.
13.Staffing and Training Needs
Specify test staffing needs by skill level. Identify training options for providing necessary skills.
Training may relate to the system under test, the business, the test techniques, the tools being
used.
In this real estate management system, we use trained and skilled man powers to manage,
develop and control the aver all structures of this systems like managers, testers etc. And also, it
includes different testing techniques like unit testing system testing and eclipse ide as an
equipment’s.
14.Schedule

15.Risks and Contingencies

This section relates to what could go wrong and what will be done to minimize the adverse
impact if the risk does indeed occur.

Assumptions are not explicit within the IEEE 829 standard however it is necessary to detail any
in this section. Identify the high-risk assumptions of the Test Plan. Specify the impact and
contingency plans for each.
Possible risks are:
• Changing Authority requirements
• Changing end date
• Quality problems
• New technology
• Lack of skilled personnel
• Lack of good quality test environments.
It is necessary to focus on any risks to the testing outlined within this Test Plan and not to the
project itself. Also note that the risks will be managed via the internal (Supplier) and external
(NHS CFH) project risk registers.

Remember that for each risk identified it is necessary to provide a contingency.