Test Report:
Testing Document Group_02
Vacation System_ Test Report
Group02:
1. Mehmet Yucel
2. Gertraud Forsthuber
3. Andreas Czak
2. INTRODUCTION
The main purpose of the test plan for the Vacation System is to discuss the testing details of the use cases of this system. The software project test plan also describes the objective, scope, and approach of the software testing effort for this project. The test plan for the Vacation System also indicates the personnel responsible for each task and also specifies the risks associated with the test plan.
2.1 OBJECTIVES
The main objectives of the test plan our system are as follows:
To identify the features of the system that will be tested.
To identify and define all the activities necessary to prepare for and conduct the testing process on the Vacation System
To define the pass/fail criteria for each item that will be tested
To identify the deliverables of the testing phase.
To define any suspension criteria and resumption techniques
To discuss the testing techniques being used to test the System.
2.2 DEFINITIONS
The following are some of the terms and definitions that are related to the test plan of the Vacation System:
Pass/Fail criteria: Decision rules that are used to determine whether a software item passes or fails a test.
Test: A collection of one or more test cases
Test Item: A software item that is an objective of testing.
Test Plan: A document describing the scope, approach, resources and schedule of the intended testing activities.
Test Summary Report: A document summarizing the testing activities and results.
Testing: The process of analyzing a software item to detect the differences between the existing and required conditions.
2.3 TEST TASKS
This section of the test plan lists all the items of the Vacation System project that will be tested:
Login
Search and Select Vacation
Availability Control and Book Vacation
Questionnaire
3. APPROACH
This section of the test plan describes the overall approach for testing the Vacation System. The approach followed for testing our system, we ensured that the major features of the project are adequately tested. The testing carried out on the Vacation System while logging into the system as a customer or a normal user of the system.
4. TESTING
4.1 UNIT TESTING
The Unit Testing is a test that tests each single module of the software to check for errors. This is mainly done to discover errors in the code of our system. The main goal of the unit testing would be to isolate each part of the program and to check the correctness of the code. In the case of the Vacation System, all the web forms and the Java classes tested. There are many benefits for this unit testing:
The unit testing facilitates change in the code.
It allows testing to be done in a bottom-up fashion.
At the same time, unit testing has some disadvantages such as it might not identify each and every error in the system.
4.2 INTEGRATION TESTING
In Integration Testing, the individual software modules are combined and tested as a whole unit. The integration testing generally follows unit testing where each module is tested as a separate unit. The main purpose of the integration testing is to test the functional and performance requirements on the major items of the project.
All the modules of the project developed individually would be combined together and tested as a whole system in the integration testing.
4.3 REGRESSION TESTING
The Regression Testing is generally done whenever modifications are made to the source code of a project. The Regression Testing can also be defined as the process of testing changes made to the computer program and also makes sure that the older programming still works with the new changes.
So, before any new version of a software product is released, the old test cases for the project will be run against the software with the changes made, to make sure that the old functionalities of the project still work.
4.4 ACCEPTANCE TESTING
This testing is generally performed when the project is nearing its end. This test mainly qualifies the project and decides if it will be accepted by the users of the system. The users or the customers of the project are responsible for the test.
4.5 SYSTEM TESTING
The system testing is mainly done on the whole integrated system to make sure that the project that has been developed meets all the requirements. The test cases for the system testing will be the combination of unit and integration tests.
5. TEST CASES
The following are the test cases for the Vacation System:
TEST CASE 1 – USER LOGIN
Incorrect Input: Incorrect username, which is the email-id in the case of the System.
Pass Criteria: An appropriate message should be generated to indicate that an invalid username or password has been typed.
Correct Input: The correct input would be a valid e-mail id of the user and a correct password associated with the email-id which he uses to log in.
Pass Criteria: The user should be directed to the web page that the customer is intended to go to after he logs into the system.
For our vacation system, this task passed the all the necessary tests.
TEST CASE 2 – SEARCH AND SELECT VACATION
Incorrect or missing Input: No selection from a list or incorrect typing into the search field. Incorrect input, in this case, would be incorrect search criteria entered or incorrect format of data entered into the data-entry fields of the Vacation search page.
Pass Criteria: An appropriate message has to be generated to the user indicating the wrong entry that he has made in the fields.
Correct Input: A correct input would be entering the data into the data entry fields in a correct format or choosing an appropriate vacation from the list.
Pass Criteria: The pass criteria for this test case would be a listing of the available vacations and successful direction into the selection detailed vacation web page.
Unfortunately, we could not test this task due to lack of implementation of the system. (Our colleague did nothing for the whole project also his task -- Blagoy Panayotov --)
TEST CASE 3 – AVAILABILITY CONTROL AND BOOK VACATION
Incorrect Input: Booking more holidays than available holidays.
Pass Criteria: An error message should be generated to the user saying that “Error vacation could not be booked”
Correct Input: The correct input, in this case, would be that the customer would enter an available number of holidays.
Pass Criteria: The pass criteria for the system would be that it accepts the order and subtracts the chosen amount of the holidays from available holiday’s offers and generating a message that saying “Vacation Successfully booked”.
For our vacation system, this task fulfilled all the expected result.
TEST CASE 4 – QUESTIONNAIRE
Unfortunately, we could not test this task due to lack of implementation of the system. (Our colleague did nothing for the whole project also his task -- Mehdi Asgari Gilan --)
6. PASS OR FAIL CRITERIA
The test cases executed on the Vacation System and they met the specific requirements mentioned in the test cases of the document.
Due to successful internal testing, we are ready to publish our system.
