Please conform to the following format when completing your A1.implementation.
I assume you will upload a single ZIP file which contains all of your classes. Make sure you upload the source code and not just the compiled *.class files. The safest thing to do is to export your entire Project into a single .ZIP file which you upload
Make sure that you place all of your code within a package whose name is your CCC user ID. Note that all of my solitaire variations start with "heineman.*" and your userID must be used so the TAs can differentiate multiple users. Also, be sure that you name your solitaire main class to be the name of the variation itself. Thus, for example, I note that Jeff Namias in this class is responsible for the Double Fives variation. He should place all of his code within the 'leftnamias' package and his main class must be 'jeffnamias.DoubleFives'.
All Java class that you submit must conform to the JavaDoc documentation standard.
The TAs will test your solitaire variation by submitting the Test cases from A1.correctness and they will also validate that it conforms to the rules of the game.
Note that your test cases must ensure that all of your classes pass the "80%" rule which I have mentioned in class. Now that you have (or should have!) a working plugin, you can take final advantage of a set of classes that I make available for you to complete the testing of your controllers.
Pay special attention to ks.tests.model.ModelFactory
in the StandAlone project and test.heineman.TestCases in the
A1 project. Also note that I have uploaded my full test cases and example
code for Narcotic in the A1 project.
The test cases exist to validate the various artifacts you contributed to the assignment. This includes:
The implementation is really held together by the controllers, so they take the most points.
Please take advantage of the many examples in the SolitairePluginTutorial project and StandAlone.