Objective: To get set up for the final team project
Follow the directions in this section only if you didn't do this for the testing project...
Steve set up Eclipse so that each user can install her own plugins.
Our subversion repository is
svn+ssh://username@serac.cs.wlu.edu/svn/csrepos/cs209_fall2015/
where username
is your username for the CS computers.
I created the project in the repository with three directories, trunk
, tags
, and branches
. You will develop in the trunk
directory, but you may want to set up tagged versions of your code in the tags
directory or try out different ideas in the branches
directory.
svn+ssh://username@serac.cs.wlu.edu/svn/csrepos/cs209_fall2015/
trunk
After the project is (finally) checked out, you are likely seeing compilation errors in the test cases.
ErrorParsedEvaluatedTests
Now, JUnit is on your classpath.
That will handle most of your errors. There will still be errors in
ParsedExpressionTreeTests
because I did some
test-driven-development example tests for you -- to show some tests that should
pass if you've coded properly. TDD is helpful for making you see what you would
like your code to do, i.e., it helps you think about the API--what should be
returned for the given input.