1 / 11

Decision table editor

Chi Ben Jamilia Clary Jude Desti Sabrina Fontaine Preston Lucas. Decision table editor. Purpose. Training for the team to go through… Software inspection and testing Problem tracking and reporting Building up team spirits Data input, edit, save dtb and reopen, print dtp

shad-mendez
Download Presentation

Decision table editor

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chi Ben Jamilia Clary Jude Desti Sabrina Fontaine Preston Lucas Decision table editor

  2. Purpose • Training for the team to go through… • Software inspection and testing • Problem tracking and reporting • Building up team spirits • Data input, edit, save dtb and reopen, print dtp • All of these aspects are dependant upon another and will encourage team work • Explore the various aspects of testing • White Box • Black Box • Automation • Provide first-hand feedback on DTE tool

  3. Technical Approach • DTE partitioned into 4 overall segments of functionality

  4. Technical Approach • Alter input data and document any detected bugs. • Test by editing input data and document any detected bugs. • Determine and document any bugs related saving a file or accessing a file. • Determine and document any bugs related printing a dtp file.

  5. Technical Approach Will be using BugTracker to document all bugs

  6. Technical Challenges • Being able to determine and cover all relevant test cases for the DTE • Being able to automate those test cases for DTE, a GUI Application. • Being able to find a tool that would test the DTE or if its even feasible to find one

  7. Risks • Inability to find a tool that automates testing on a GUI application • Not enough time to create an application that can automate testing within a GUI application

  8. Completion Timeline 2/28/2010 Initial Group meeting, Intro to Bug Tracker 3/2/2010 Divide DTE into segments and assign to each member for further testing. 3/3/2010 Presentation on DTE and Project Objectives

  9. Completion Timeline Week of 3/15/2010 Conduct Acceptance Test then Begin Inspection testing on DTE tool Week of 3/22/2010 Begin Unit testing on 4 segments of DTE Week of 3/30/2010 Deadline for all high and medium priority bugs to be verified and assigned

  10. Completion Timeline Week of 4/5/2010 Begin work for testing automation Week of 4/19/2010 Final Project Completion

  11. Conclusion • DTE is a tool in the working and is very beneficial to Software Engineers • Goal of this project is to increase knowledge of various testing methods • White Box Testing • Black Box Testing • Automation • Parallel work in progress: fixing the documented bugs

More Related