Fixed
Details
Assignee
Laurel WilliamsLaurel WilliamsReporter
Laurel WilliamsLaurel WilliamsOriginal estimate
Time tracking
No time logged2d remainingComponents
Fix versions
Priority
Minor
Details
Details
Assignee
Laurel Williams
Laurel WilliamsReporter
Laurel Williams
Laurel WilliamsOriginal estimate
Time tracking
No time logged2d remaining
Components
Fix versions
Priority
Created August 21, 2009 at 8:12 PM
Updated October 22, 2009 at 8:28 PM
Resolved August 31, 2009 at 3:59 PM
Justin and Michelle say:
> I also like the idea that you have good names for your indexes. (module indexes in the tests).
> > However, I'm only worried about them being hardcoded. The danger is
> > that if even the order of the modules is changed, the tests could fail.
> > What I was thinking was more along the lines of writing a function that
> > will find the index of the module based on its name. This way you won't
> > have to manually keep track of the indexes.
This makes a lot of sense and I completely agree.
AND
I like the idea of putting the data into its own file - I think it
will lead to easier to read code in the builder. The javascript file
containing the data would still need to be located with the demo
rather then with the tests since we wouldn't want the demo to depend
on the tests directory.
Move the script tag into the html and commented out when not in use.