1 / 17

09/18/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/.

eldon
Download Presentation

09/18/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/ 09/18/09 1

  2. Agenda • Goal • Problem • Importance • Project Plan • Responsibilities • Questions 09/18/09 2

  3. Goal • Develop unit test framework for Cyberonics development environment • Pocket PC 2003 • Embedded Visual Studio SP3 • Maintain consistent communication • Provide project documentation 09/18/09 3

  4. Problem • Cyberonics does not have formal unit test procedures • Currently debug and step through • Slow, tedious • No unit tests frameworks for Pocket PC • Need customized framework 09/18/09 4

  5. Importance • Class III medical device • Requires strict test standards • Less room for human error • Help design, develop, execute tests • Automation • Easier to test • More time for development • Provides reports • Formal testing process 09/18/09 5

  6. Requirements • Enable Cyberonics to create and execute unit tests into existing code base • Provide constructs such as asserting equal, null, etc. • Allow Cyberonics to run unit tests in batches to enable test automation • Provide summary of test result with details of failures • Provide the code coverage report 09/18/09 6

  7. Investigation Report • Investigated many existing frameworks • Complexity – work involved in port/develop • Meets most Cyberonics requirements • CPPUnit • JUnit in class • Existing documentation/community • Open source • Full-featured • Other frameworks as references 09/18/09 7

  8. Project Plan • Divide into three teams • CPPUnit porting into eVC++4 • CPPUnit in VS2008 • Pocket PC Application Development 09/18/09 8

  9. CPPUnit eVC Team • Main Goal • Port CPPUnit into eMbedded Visual C++ 4 • Sub Goals • Map initial obstacles to the overall goal • Investigate RTTI library • Make small parts work and build up • 2 Members • Jenni and Brad 09/18/09 9

  10. CPPUnit VS2008 Team • Main Goal • Understand how CPPUnit works • Identify obstacles for eVCTeam • Sub Goals • Set up CPPUnit in VS2008 • Explore functionality • 1 Member • Lauren 09/18/09 10

  11. Pocket PC App Team • Main Goal • Application for automated testing • Sub Goals • Familiarize with environment • Design GUI • 2 Members • Mike and Nathan 09/18/09 11

  12. CPPUnit VS CCPUnit eVC Pocket PC App 09/18/09 12

  13. CPPUnit VS CCPUnit eVC Pocket PC App CPPUnit Features and Requirements Setup eVC 4 SP3 Basic CPPUnit Functionality Design Specification 09/18/09 13

  14. CPPUnit VS CCPUnit eVC Pocket PC App CPPUnit Features and Requirements Setup eVC 4 SP3 Basic CPPUnit Functionality Design Specification Advanced Functionality Prototyping 09/18/09 14

  15. CPPUnit VS CCPUnit eVC Pocket PC App CPPUnit Features and Requirements Setup eVC 4 SP3 Basic CPPUnit Functionality Design Specification Advanced Functionality Prototyping Integrate Advanced Features into GUI 09/18/09 15

  16. Milestones • October 2nd: Interim Report Presentation • October 16th: Status Report • October 30th: Interim Report Presentation • November 1st: Begin integration of all CPPUnit features with the GUI • November 13th: Status Report • November 23rd: Finish Integration and Documentation • December 4th: Preliminary Demo • TBA: Final Presentation 09/18/09 16

  17. Project Status CPPUnit VS CCPUnit eVC Pocket PC App CPPUnit Features and Requirements Setup eVC 4 SP3 Basic CPPUnit Functionality Design Specification Advanced Functionality Prototyping Integrate Advanced Features into GUI Beginning Nov. 1st 09/18/09 17

More Related