Rewrite demo assignment

This is a proposed implementation of the assignment layout discussed in #67 .

Resolves #67 
I see. I had in mind that we would verify that setup affects the execution
of each test and is called once per test.  So for example if "ten=10"
appears in setup, we should verify that "ten" is available in "setup".


On Thu, Aug 21, 2014 at 12:26 PM, albert12132 <notifications@github.com>
wrote:

> In client/demo_assignments/hw1/tests/q1.py:
>
> > +    4
> > +    # explanation: Squaring a negative number
> > +    # choice: -4
> > +    # choice: 2
> > +    # choice: None
> > +    """,
> > +  },
> > +  {
> > +    'type': 'doctest',
> > +    'test': """
> > +    >>> square(0)
> > +    0
> > +    # explanation: Squaring zero
> > +    """,
> > +    'teardown': """
> > +    print('Optional Teardown code for the testcase goes here')
>
> I meant to ask what you had in mind for testing the demo and whether or
> not the teardown runs, in addition to the unittests that we have for ok.py.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Cal-CS-61A-Staff/ok/pull/76/files#r16561409>.
>