1 / 13

Acid Reign Tellabs

This document outlines the requirements, successes, and shortcomings of the Unit Test Script (UTS) generation system utilizing C-Files. Users can effectively generate, save, edit, print, and manage UTS from existing C-Files. Key features include script generation, editing, and the ability to cut, copy, and paste unit tests. Notable shortcomings include the inability to print scripts and handle goto statements or preprocessor commands. Member responsibilities and roles in the project are also detailed to enhance collaboration and accountability.

kerem
Télécharger la présentation

Acid Reign Tellabs

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. Acid Reign Tellabs Prototype

  2. Agenda • Requirements • Successes and Accomplishments • Shortcomings • Developer’s Duties • And to make your life easier…

  3. Requirements • The user can generate a Unit Test Script from a C-File. • The user saves a Unit Test Script to disk. • The user can open an existing Unit Test Script. • The user can edit an existing Unit Test Script.

  4. Requirements • The user can print the Unit Test Script. • If the C-File is modified after the last Unit Test Script generation, the program will merge the existing Unit Test Script file with a new Unit Test Script for the modified C-File. • The user can cut, copy, and paste Unit Tests.

  5. Successes and Accomplishments • The user can generate a Unit Test Script from a C-File. • The user saves the Unit Test Script to disk. • The user can open an existing Unit Test Script. • The user can edit an existing Unit Test Script.

  6. Successes and Accomplishments • The user can cut, copy, and paste Unit Tests.

  7. Successes and Accomplishments • The user can cut, copy, and paste Unit Tests.

  8. Shortcomings • The user cannot print the Unit Test Script. (Not Expected) • If the C-File is modified after the last Unit Test Script generation, the program cannot merge the existing Unit Test Script file with a new Unit Test Script for the modified C-File. (Not Expected)

  9. Short Comings • The program cannot handle goto statements. • The program cannot handle preprocessor commands.

  10. Member’s Responsibilities • Atul Ankola • GUI • Edit UTS/Save UTS • UTS/GUI Interface • UTS Data Structure • Samuel Blinn • GUI • GUI Interface

  11. Member’s Responsibilities • Jason Blankman • C-File Parser • Test Generator • UTS/UTG Interface • UTS Data Structure • Chris Reardon • GUI • GUI Interface

  12. Member’s Responsibilities • Michael Shrall • UTS Data Structure • UTS Parser • UTS Interface

  13. Prototype HERE WE GO!!!!

More Related