domain object test

lvlupnow

sts_group2-version2_1.docx

Home >Computer Science homework help >domain object test

Bed and Breakfast Management System

Software Test Specification (STS)

November 2014

By Group 2:

David Jones

Larry Francois

Table of Contents

1. Introduction

1.1. Objectives

1.2. Background

1.3. Scope

1.4. References

1.5. Test Environment

1.5.1. Hardware

1.5.2. Software

1.5.3. Data

2. Architectural Design

2.1. User interface

2.2. Services

2.3. Domain Objects

3. Traceability Matrix

4. Test Specifications

4.1. User Interface – Black box testing

4.2. Service – White box testing

4.3. Domain Objects – White box testing

1. Introduction

1.1. Objectives

The objective of this document is to provide an outline for testing the Bed and Breakfast Management System. The guidelines in this document will allow a software test team the ability to perform white-box and black-box tests to validate the capabilities of the system

1.2. Background

The Bed and Breakfast Management system is used to automate the management of small bed and breakfast establishments. It manages reservations based on room availability by allowing customers to reserve stays by dates it also monitors expenses and profits. This document is a guideline to be used to assist in testing efforts in developing a system that is capable of meeting the customers need.

1.3. Scope

The testing documentation is scoped to the test cases specific for the three modules of the architectural context diagram:

1. User Interface – Section 2.1

1. Services – Section 2.2

1. Domain Objects – Section 2.3

1.4. References

1. IEEE std. 829-1998 – IEEE Standard for Software Test Documentation

1. Software Requirements Specification (SRS)

1. Software Design Document (SDD)

1.5. Test Environment

The testing environment for the Bed and Breakfast Management System consist of minimal requirements. No special equipment or any specific software. During white-box testing systems will be Restricted to testers only. Each component will be tested separately and thoroughly in simple environment accommodating to all testers.

1.5.1. Hardware

A modern server computer with at least 4 GB or more of usable RAM. A physical storage capacity of at least 2TB to store records. These requirements will be efficient enough to house the BBMS software. We will also need a modern client computer networked to the server. This machine will include all peripherals, i.e. Mouse, and keyboard, printer and monitor. The requirements for the client machine will be minimal 500GB physical storage, 2GB or more of RAM.

1.5.2. Software

The software will consist of the Bed and Breakfast Management System which can run on a Windows or Linux platform. The (BBMS) software will be installed on the server and client computer that is going to be used for testing. Verify installation before use

1.5.3. Data

Testers of the BBMS should be prepared with the following data in order to complete the use cases in section 4 of the STS:

1. Date ranges for the calendar

1. Non-overlapping ranges for successful reservations

1. Overlapping ranges for unsuccessful reservations and checks.

2. Customer data

1. Test names (first, last)

1. Test addresses (street, state and zip code)

1. Dummy credit card information (valid and invalid formats)

1. Dummy phone numbers (valid and invalid)

3. Reservation data

1. Sample prices per day (valid and invalid)

1. Guarantee dates for a guest

4. Establishment Data

1. Set of room numbers to create for vacancies

The set of data listed above will accommodate the entirety of test cases across the user interface, service, and domain object cases listed in this document.

2. Architectural Design Diagrams

These diagrams describe the 3 core modules of the BBMS software. The units are User Interface, Services, and Domain Objects.

2.1 User Interface

This module is about the users interacting with the BBMS software. The users are able to use the software by way of the user interface. The user interface provides and output to the services. The only external interface objects are the monitor, keyboard and mouse.

Calendar Lookup

Room Reservation

Guest Information

Guest Payment

Main Menu

Check Out

Print Report

User Interface

Architectural Context Diagram of the User Interface

2.2 Services

This module is about processes that run within the BBMS. The service modules provide the input and out to the user interface and manage the flow of data to and from the domain objects. The main functions of these services are making a reservation, checking a guest out, and generating the profit report.

AddGuest

MakePayment

ReserveRoom

CheckOut

CalendarLookup

ProfitLossReport

Services

Architectural Context Diagram of the Services

2.3 Domain Objects

This module is about the entities that hold data that is used by the services to provide the functions of the BBMS. These entities are referred to as domain objects.

Room

Reservation

Guest

Payments

Domain Objects

Architectural Context Diagram of the Domain Objects

3. Traceability Matrix

Test Category	Test Description	SDD Requirement	SRS Case	SDD Entity	STS Test Case	Pass/Fail
User Interface	Calendar	X	X	X screens	X
Services	Make Reservation	X		X Entities	X
Domain Objects	Add reservation to Reservations	X	X	X Entities	X

4. Test Specifications

The 3 core modules presented in section 2 of this document are tested in this section. These tests establish the validity of the functionality of the BBMS software. They are built around the specifications and requirements that were defined in the SRS and SDD documents. There is one black-box test and two white box tests. The black-box test employs personnel with a non-engineering background. The white-box testing is done by the software developers who designed the system.u

4.1 User Interface

This test is for the User Interface unit. It is designed to test the human to computer interface of the BBMS. Testing the user interface is a black box test. In this test nothing is known about how the program works. It only has user actions and expected outcome.

4.1.1. Making a reservation

4.1.1.1 Test: Reservation calendar display

Test case specification: The purpose this test case is to provide a black-box test of the CalenderLookup portion of the user interface as required in SRS section 3.1.1.

Test Items: This will test the CalenderLookup service’s ability to display the dates of a room’s reservation in a calendar.

See SDD Screen: 5.1.2 Reservation Calendar

Step	Input Specifications	Output Specifications
1	Click Reservations button from the main menu.	The Reservation Calendar screen appears.
2	Click Previous Month button.	The previous month is shown on the screen.
3	Click Next Month button.	The current month returns to the screen.
4	Click Next Month button.	The next month is shown on the screen.
5	Click Previous Month button.	The current month returns to the screen.
6	Click Room 1 button.	All calendar days are still white. $80.00 appears in the Daily Room Rate box.
7	Click Room 2 button.	All calendar days are still white. $90.00 appears in the Daily Room Rate box.
8	Click Room 3 button.	All calendar days are still white. $100.00 appears in the Daily Room Rate box.
9	Click Start Reservation button.	The Room Reservation screen appears.

Environmental Needs:

1. Computer with 40GB of disk space

2. Monitor

3. Keyboard

4. Mouse

Special procedural requirements: None

Intercase Dependencies: None

4.1.1.2 Test: Reserve Room

Test case specification: The purpose of this test case is to provide a black-box test of the MakeReservation portion of the user interface as required in SRS section 3.1.1.

Test Items: This will test the ability to create a reservation for specified dates and room number.

See SDD 5.1.3 Room Reservation Entry

Step	Input Specifications	Output Specifications
1	Click Room 3button.	$90.00 appears in the Daily Rate box
2	Click the calendar pop-up button the Reservation Start Date box.	A popup calendar appears on the screen.
2	Click 14 on the pop-up calendar.	12/14/2014 appears in the box below Reservation Start Date.
4	Click the calendar pop-up button the Reservation End Date box.	A popup calendar appears on the screen
5	Click 16 on the pop-up calendar.	12/15/2014 appears in the box below Reservation End Date.
6	Click the Guaranteed box.	An X appears in the Guaranteed box.
7	Click the calendar pop-up button the Guaranteed Date box.	A popup calendar appears on the screen
8	Click 10 on the pop-up calendar.	12/10/2014 appears in the Guaranteed Date box. The focus is on the Create Reservation button.
9	Click Create Reservation button.	The Guest Information screen appears.

Environmental Needs:

1. Computer with 40GB of disk space

2. Monitor

3. Keyboard

4. Mouse

Special procedural requirements:

Intercase Dependencies: None

4.1.1.3 Test: Add Guest

Test case specification: The purpose of this test case is to provide a black-box test of the AddGuest portion of the user interface as required in SRS section 3.1.1.

Test Items: This will test the entering the guest’s name, address, phone, and credit card information.

See SDD Screen: 5.1.4 Guest Data Entry

Step	Operator Action	Output Specifications
1	Enter James in the First Name box and press the enter key.	The cursor goes to the Last Name box.
2	Enter Markman in the Last Name box and press the enter key.	The cursor goes to the address box.
3	Enter 101 Fairview Street and press the enter key.	The cursor goes to the next line of the Address box.
4	Enter Pawtucket and press the enter key.	The cursor goes to the next line of the Address box.
5	Enter RI 02860 and click the Phone box.	The full address remains in the Address box and the cursor goes to the first digit of the phone number.
6	Enter 4011234567 and press the enter key	(401)123-4567 stays in the phone number box and the cursor goes to the Credit Card number box
7	Enter 1234 5678 9012 3465 and press enter.	1233-4567-8901-2345 appears in the Credit Card Number box and the cursor goes to the Expiration Date box.
8	Enter 073016 and press enter.	07/30/16 appears in the Expiration Date box and the Save Guest button is focused.
9	Click the Save Guest button.	The Guest Payment screen is displayed.

Environmental Needs:

1. Computer with 40GB of disk space

2. Monitor

3. Keyboard

4. Mouse

Special procedural requirements: None

Intercase Dependencies: Test 4.1.1.2 Room Reservation must have been completed prior to this test.

4.1.1.4 Test: Guest payment

Test case specification: The purpose of this test case is to provide a black-box test of the MakePayment portion of the user interface as required in SRS section 3.1.1.

Test Items: This will test entering the payment of a guest who is making a payment over the telephone.

See SDD Screen: 5.1.5 Payment Entry

Step	Input Specifications	Output Specifications
1	None.	The Payment entry screen appears with James Markman displayed at the top of the screen. $80.00 is displayed in the Daily Room Rate box. $90.00 is displayed in the Daily Room Rate box. $180.00 is displayed in the Total Amount box. The cursor will be in the Payment Amount box.
2	Enter 90.00.	$90.00 is displayed in the Payment box. The focus is on the Make Payment button.
3	Click Make Payment button.	A pop-up window displays $90.00 charged to customer credit card 1233-4567-8901-2345.
4	Click the OK button.	The pop-up disappears and the Main Menu screen is displayed.

Environmental Needs:

1. Computer with 40GB of disk space

2. Monitor

3. Keyboard

4. Mouse

Special procedural requirements: None

Intercase Dependencies: Test 4.1.1.3 Guest Information must have been completed prior to this test.

4.1.1.5 Test: Display Reservation

Test case specification: The purpose of this test case is to provide a black-box test of the CalenderLookup portion of the user interface as required in SRS section 3.1.1.

Test Items: This is a test to see if the new reservation is displayed on the calendar.

SDD Screen: 5.1.2 Reservation Calendar

Step	Input Specifications	Output Specifications
1	Click Reservations button from the main menu.	The Reservation Calendar screen appears.
2	Click the Reservations button.	The Reservation screen is displayed with the 14 and 15 date boxes colored in blue.
3	Click Exit.	The Main Menu screen is displayed.

Environmental Needs:

1. Computer with 40GB of disk space

2. Monitor

3. Keyboard

4. Mouse

Special procedural requirements: None

Intercase Dependencies: Tests 4.1.1.2 through 4.1.1.4 must have been completed prior to this test. A reservation will have been made so that the reservation will appear on the calendar.

4.1.1.6 Test: Guest check out

Test case specification: The purpose of this test case is to provide a black-box test of the CheckOut portion of the user interface as required in SRS section 3.1.1.

Test Items: This is a test of checking out a guest where any remaining money due to the bed and breakfast business is automatically charged to the guest’s credit card. This same process removes the reservation form the room and is tested in this test as well.

See SDD Screen: 5.1.6 Check Out

Step	Input Specifications	Output Specifications
1	Click the Check Out button.	The Check Out screen is displayed. A list of guests by room number is displayed the Guest Selection box. James Markman is listed for room 2.
2	Click James Markman from the list.	James Markman is highlighted in bold letters. $180.00 is displayed in the Total Amount box. $90.00 is displayed in the Balance Due box.
3	Click Finalize button.	A pop-up window displays $90.00 charged to customer credit card 1233-4567-8901-2345.
4	Click the OK button.	The main menu screen is displayed.
5	Click the Reservations.	The calendar screen is displayed with the 14 and 15 date boxes the same color as the rest of the date boxes.
6	Click the Exit button.	The main menu screen is displayed.

Environmental Needs:

1. Computer with 40GB of disk space

2. Monitor

3. Keyboard

4. Mouse

Special procedural requirements: None

Intercase Dependencies: Tests 4.1.1.2 through 4.1.1.4 must have been completed prior to this test. A reservation will have been made with the data and services needed to check a guest out.

4.1.1.7 Test: Profit report

Test case specification: The purpose of this test case is to provide a black-box test of the ProfitReport portion of the user interface as required in SRS section 3.1.1.

Test Items: This is a test of process that generates the profit report.

See SDD Screen: 5.1.7 Profit Report

Step	Input Specifications	Output Specifications
1	Click the Reports button.	The Profit Report screen is displayed.
2	Enter 1 in the Starting Month box.	The cursor goes to the Starting Year box.
3	Enter 2014 in the Starting Year box.	The cursor goes to the Ending Month box.
4	Enter 12 in the Ending Month box.	The cursor goes to the Ending Year box.
5	Enter 2014 in the Ending Year box.	$280.00 is displayed in the Sum of All Payments box.
6	Click the Exit button.	The main menu screen is displayed.

Environmental Needs:

1. Computer with 40GB of disk space

2. Monitor

3. Keyboard

4. Mouse

Special procedural requirements: None

Intercase Dependencies: Tests 4.1.1.2 through 4.1.1.4 twice for 2 reservations must have been completed prior to this test. To get the sum of all payments made, another reservation and check out is to be made to provide more than one payment record in the Payments database. Repeat the Reservation test steps 1, 9 through 30 with these differences: Select room 3 in step 10, Enter 200.00 in step 28. Repeat the Check Out test with steps 1 through 4.

4.2 Service Test

4.3 Domain Objects Test