1. Decision Table Editor Verification & Validation

2. Outline Testing Process Testing Approach Test Results Project Plan Test Product Management Automation Technical Challenges Future Work

3. Testing Process Colloboration with the Development and Maintenance Team – In Charge of Fixing the Defects We Test the Product; D&M Fixes Found Defects A new version of the product is put up every week Every week Regression Testing is performed

4. Testing Approach Black Box Testing – Tool separated in four units Data Input Data Modification Printing Saving

5. Testing Approach Black Box Testing Data Input Scenarios Data Modification Scenarios Printing Scenarios Saving Scenarios

6. Testing Approach White Box Testing – Using JUnit to test all the functions – Nine Testing Packages – 72 tests

7. Test Results AcceptanceTest Results – DTE Actions: 3 P 1 F – DTE Conditions : 6 P 0 F – DTE Metadata: 4 P 2 F – DTE Variables: 4 P 0 F – DTE Save/Print/Change: 8 P 4 F Total Results: 25 P 7 F

8. Test Results Unit Test Results – Data Input Number of Bugs Found Number of Bugs Fixed 42

9. Test Results Unit Test Results – Data Modification Number of Bugs Found Number of Bugs Fixed 65

10. Test Results Unit Test Results – Printing Number of Bugs Found Number of Bugs Fixed 10

11. Test Results Unit Test Results – Saving Number of Bugs Found Number of Bugs Fixed 50

12. Test Results JUnit Test Results – Decision Table Class : 16 P 0 F – Condition Expression Class: 1 P 7 F – Condition Class: 7 P 0 F – Data Type Class: 5 P 0 F – DTE Variables: 6 P 0 F – Response Variables: 7 P 0 F – State Variables: 7 P 0 F – Stimuli Class: 7 P 0 F – Variable Class: 9 P 0 F Total Results: 65 P 7 F

13. Test Results Regression Test Results - Number of Bugs Found Number of Bugs Fixed 2613

14. Test Results Regression Test Results – Resounding Bugs - bugs that still existed after an attempt of fixing them Printing to DTP Save does not operate properly Changing of Model Name Error Checking

15. Project Plan Decision Table Project Plan Progress Indicators – If the number of bugs in the end is less than the initial bugs that we found End Bugs < Initial Bugs

16. Test Product Management The author, Ricardo Eights, using NetBeans for development When a change is made the new version is put up on the website: http://www.cis.famu.edu/~reights/ http://www.cis.famu.edu/~reights/ Old versions are still kept for back up purposes

17. Automation Difficulties Most potential tools are not free. Free source tools requires expert skills in Java to implement the automation – Contained execution issues.

18. Automation: Future Work Link up with a Java expert for the possibility of implementing the Automation. Our default option will be to create enough test cases that will satisfy the agreement of whether or not testing is sufficient.

19. Technical Challenges It seems that when certains bugs are fixed, more bugs appear At times a mixture of bugs appear after a fix has occured. Tools for gui application automation seems intangible

20. Future Work Inspections – Will Occur on the LOC for Printing and Saving Reason: Seems to be one of the bigger problems – Roles: Author – Ricardo Inspectors – Jude, Chi, and Preston Reader – Sabrina Moderator - Jamilia

21. Questions