Project Schedule Requirements Project Plan Team Members Team Participation Status Reports Home Page
Project Testing >>>

Introduction

To ensure a stable and user friendly application the GeorgiaPalm team has implemented a testing plan that will utilize all team members in the testing process. GeorgiaPalm will implement white box, black box, use testing, and also follow up with regression testing after any code enhancements.
      i. Tim Hare and John Shaffer will be utilized for white box testing of the data structures, algorithms           and desktop integration within the code.
      ii. Dianna Knight and Lester Henry will be adding support during the black box and use case testing.
Personnel
Dianna Knight Project Manager - Leader csu10679@
John Shaffer Tester and Customer Liaison csu12748@
Lester Henry Document Manager - Web Master csu15072@
Tim Hare Developer csu15072@
Testing Scenarios: Each test case has a testing scenarios that will be performed on each build. The test will be printed and 2 testers will be given half of the tests. Each scenario will as performed all steps need to checked off and clear documentation for each step need to be documented. Each seniero will need to passed or failed with the date performed and the testers initials. Any additional test made while in the application need to be documentation and results. Please comment on any form layouts that need to be fixed. This will be performed for each BlackBox test and on SOME White box test as approprate.

Test Cases

Data Correctness Test

Testing Scenarios Link
Test Number:1
WBS 5.3.3
Testing Type: Black box
Purpose: To ensure data is imported in to the PDA correctly.
Preconditions: Test file with database tables for synchronization and a Palm PDA.
Post-conditions: PDA completes sync and imports data with no errors.
Test Cases:
  1. A populated sample data file is loaded.
  2. An unpopulated sample data file is loaded.
  3. A corrupt sample data file is loaded.

Data Structure Test

 
Test Number: 2
WBS 6.3
Testing Type: White box
Purpose: To verify data was distributed to the correct data structures in the application.
Preconditions: PalmOS synchronized with desktop application data.
Post-conditions: Arrays are filled with data values equal to the exported desktop data.
Test Cases:
  1. Write a test program that will compare the contents of the imported data against the known test file data.

Data Distrubution Test

Testing Scenarios Link
Test Number: 3
WBS 6.4
Testing Type: Black box
Purpose: Verifying that all drop down selections are linked to the correct data.
Preconditions: The application populated with data.
Post-conditions: All drop down boxes provide valid selections.
Test Cases:
  1. Test the date entry text box
  2. Test the Job name
  3. Verify the contact name
  4. Verify the contact phone number
  5. Verify the Job location
  6. Verify the Job code dropdown
  7. Verify the Supervisor code dropdown
  8. Verify Job memos

Data Correctness Test

Testing Scenarios Link
Test Number: 4
WBS 6.6.1
 Testing Type: Black box
Purpose: To verify that dates can be queried for viewing in multiple modes.
Preconditions: Running application in monthly mode.
Post-conditions: Selection of date changes from monthly mode to daily/hourly mode.
Test Cases:
  1. Open application and select monthly view in the calendar.
  2. Open daily view from within the monthly view.
  3. Open a single date query and open only a daily view.

Open Job Itinerary Test

Testing Scenarios Link
Test Number: 5
WBS 6.6.1.2
Testing Type: Black box
Purpose: Testing the ability to open an Itinerary and view details
Preconditions: Running application populated with data.
Post-conditions: An open assignment with travel and assignment details available.
Test Cases:
  1. Open an imported assignment.
  2. Verify that the correct flight information was imported.
    a. Airline Name
    b. Flight number
    c. Departure date and time
    d. Arrival date and time
  3. Verify the correct rental car information was imported.
    a. Company name
    b. Car rental pickup location
    c. Car rental drop-off location
    d. Car type
    e. Pickup date and time
    f. Drop-off date and time
  4. Verify that the correct hotel information was imported.
    a. Hotel name
    b. Hotel address
    c. Hotel phone number
    d. Arrival date and time
    e. Departure date and time

Creat Job Itinerary Test

Testing Scenarios Link
Test Number: 6
WBS 6.4.1
Testing Type: Black box
Purpose: Test the ability of the application to create, save, and close a job Itinerary.
Preconditions: Application populated with data.
Post-conditions: A new assignment is created and saved; it is then closed and re-opened.
Test Cases:
  1. Create a new assignment
    a. Enter Date of new assignment
    b. Create the Job name
    c. Create contact name
    d. Create contact phone number
    e. Enter the Job location
    f. Create/Select the Job code
    g. Select the Supervisor code
    h. Enter a Job memo
  2. Save the new assignment.
  3. Re-open the assignment and then close the assignment.

Edit Job Itinerary Test

Testing Scenarios Link
Test Number: 7
WBS 6.6.1.2
Testing Type: Black box
Purpose: To verify that data can be entered or edited in the travel section of an job assignmentitinerary.
Preconditions: Application populated with data and an open assignment.
Post-conditions: All allowed text boxes are editable and data that is changed is saved replacing previous data.
Test Cases:
  1. Open an old assignment.
  2. Enter/edit new flight information.
    a. Airline Name
    b. Flight number
    c. Departure date and time
    d. Arrival date and time
  3. Enter/edit new rental car information.
    a. Company name
    b. Car rental pickup location
    c. Car rental drop-off location
    d. Car type
    e. Pickup date and time
    f. Drop-off date and time
  4. Enter/edit new hotel information.
    a. Hotel name
    b. Hotel address
    c. Hotel phone number
    d. Arrival date and time
    e. Departure date and time
  5. Verify the changes are recorded to the stored data structures.

Time Entry Test

Testing Scenarios Link
Test Number: 8
WBS 6.6
 Testing Type: Black box
Purpose: Verifying that hours and minutes can be entered on a daily basis.
Preconditions: Populated application with an open assignment in daily mode.
Post-conditions: Application records the correct values for hours and minutes.
Test Cases:
  1. Enter values for test hours worked
  2. Verify that daily values are correctly stored.
  3. Verify that hours are calculated for the week.

Export Validation Test

Testing Scenarios Link
Test Number: 9
WBS 5.3.3
Testing Type: White box
Purpose: To verify that data entered in the application is exported to the .xml correctly.
Preconditions: Application with edited or created data to be exported.
Post-conditions: An .xml file with data in the correct format.
Test Cases:
  1. Data will be exported to a data file.
  2. The data file will be compared with the stored data for accuracy.

Memo Field Test

Testing Scenarios Link
Test Number: 10
WBS 6.4
Testing Type: White box
Purpose: To verify that data entered in the memo field is valid.
Preconditions: Application populated with data and a job selected.
Post-conditions: Application with memo data correctly saved.
Test Cases:
  1. Validate data is added to the memo field.
  2. Test string length by overflow.
  3. Enter null value for textbox.
Build 1 Week 12
Completed Requirements: 3.0 - 4.0 - 5.0 - 6.0(6.1 - 6.5)
Tests to be Run: 1 - 2 - 3 - 6 - 7 - 9
Build 2 Week 15
Completed Requirements: 6.0(6.4-6.7)
Tests to be Run: 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10
Error Report
Error Number
Found By
When Found
Description
Status