Python TeamCapstone Iteration II

Rich Hildebrand . Corey ZachrichJacob Funchion . Micah Detamore

Overview

• What the python team previously accomplished

• Newly added and in-progress features

• Features to-be-completed

Previously...

• Server and basic UI set up using Heroku and Django

• User code file buildero User-entered code written to unique file based on

sessionIDo File sent to PDB, then output written to a separate

unique file

• View current vars, values and line numbero Based on regex matches in the debugged output file

• View exceptions if thrown during debugging

• Unit tests introducedo Coding problems that request specific output based

on calls to the user-written program

This Iteration...

• Added test result area in templateo Expected and actual results

• Modified front endo Modified layout using CSSo Images replaced for cleaner appearanceo Added working unit test expected result window

• Worked on adding stack trace knowledgeo Similar to bt full in GDBo Implemented features of the "sys" module iteratively

retrieve all frame's local vars

Upcoming Features...

• XML parsingo Using the ElementTree libraryo Re-implementing features of C++ team's parser

• Tracebacko Frame info displayed in the code execution window

• Highlight line numberso Currently executing line number highlighted in the

coding window using JavaScript

• Run-all functionalityo Progress and details are unknown

• Add breakpointso Pause code execution at specific line number

Summary

• Functionality and user interface are still a work-in-progresso Moving at a steady pace, but many features still to

come

• Program demo

• Questions, comments, suggestions