1 / 33

11/13/09

CS 490 Software Testing Fall 2009 Implement Unit Test Framework for Application running on a Pocket PC 2003 device. F ramework for U nit-testing D evelopment G roup Team Leader: Lauren Stuart Team: Nate Frost, Jennifer Long, Mike Noah, Brad Van Dyk Website: http:// redlea.net/490/.

selma
Download Presentation

11/13/09

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. CS 490 Software TestingFall 2009Implement Unit Test Frameworkfor Application running on aPocket PC 2003 device Framework for Unit-testing Development Group Team Leader: Lauren Stuart Team: Nate Frost, Jennifer Long, Mike Noah, Brad Van Dyk Website: http://redlea.net/490/ 11/13/09 1

  2. Agenda • Demo • Test Selection • Save/Load Suites • Test Execution • Progress Bar • Results • Enhancement Plans • Unfinished Work 11/13/09 2

  3. NOTES FOR TEST SELECTION – DO NOT PUBLISH • Talk about how we can select one test in a tree, and the box is shaded • And if all tests in a tree are selected, then the box is checked 11/13/09 3

  4. Demo – Test Selection 11/13/09 4

  5. Demo – Test Selection 11/13/09 5

  6. Demo – Test Selection 11/13/09 6

  7. Demo – Test Selection 11/13/09 7

  8. NOTES FOR SAVE – DO NOT PUBLISH • Talk about how after tests are selected, clicking save tests will generate a file with test suite information • And about how the output of a saved test location may be changed – I think nate is working on this 11/13/09 8

  9. Demo – Save 11/13/09 9

  10. Demo – Save 11/13/09 10

  11. Demo – Save 11/13/09 11

  12. Demo – Save 11/13/09 12

  13. Demo – Save 11/13/09 13

  14. NOTES FOR LOAD – DO NOT PUBLISH • Talk about how after tests are selected, loading a test suite will ADD tests to the current selection 11/13/09 14

  15. Demo – Load 11/13/09 15

  16. Demo – Load 11/13/09 16

  17. Demo – Load 11/13/09 17

  18. Demo – Load 11/13/09 18

  19. Demo – Load 11/13/09 19

  20. NOTES FOR Test Execution – DO NOT PUBLISH • Talk about after tests are selected, user should click run and point out the progress of the tests being run • And the end results dialog 11/13/09 20

  21. Demo – Test Execution 11/13/09 21

  22. Demo – Test Execution 11/13/09 22

  23. Demo – Test Execution 11/13/09 23

  24. Demo – Test Execution 11/13/09 24

  25. Demo – Test Execution 11/13/09 25

  26. NOTES FOR RESULTS – DO NOT PUBLISH • After tests are run, close the program to find the output file • Open it to view the xml information • Notice the information about an individual test • The statistics for all tests • Timing for both 11/13/09 26

  27. Demo – Results 11/13/09 27

  28. Demo – Results 11/13/09 28

  29. Demo – Results 11/13/09 29

  30. Demo – Results 11/13/09 30

  31. Sample Presentation

  32. Plans for Enhancement • Confirmation message box for Save / Load • Show pass/fail results in a tree diagram • Human readable test statistics/results • Use a style sheet for current XML file • Expected finish: end deliverable 11/13/09 32

  33. Unfinished Work • Code Coverage • Cancel button during test execution • Hard to interrupt cleanly • Minor bugs 11/13/09 33

More Related