csce3513 / Team18

Team 18 repository
5 stars 2 forks source link

user_stories #1

Open suwiringSIxbert opened 12 years ago

suwiringSIxbert commented 12 years ago

 Game starts with a preload/splash screen, either when settings (resume from last saved...) or modules (loading sounds, preparing sprites bitmaps or loading game engine may take some significant time...) are being loaded.  Main Menu (made of 4 button) -User selects “play” button to start “New game” or “Resume” -use can set up “options” -user can “exit” Play Options Help Exit I. If play is pressed, then another submenu pops up: New Game Resume If “New Game” is selected the new instances are created and the user plays for how long they want until victory or loss conditions are met. If the user wants to quit game before then (esc button), there is a prompt to “continue playing” or “Save and exit” or “Exit without saving”) If “resume” is selected, the game load from last settings and game states, allowing the user to keep playing like before. II. If “Options” is selected, then a set of settings is displayed: to set character, set number of opponent sprites, audio volume… this menu option is subject to change during game development: the user has option to choose “discard” to cancel chosen options or “done” to return to main menu. III. If “Help” is selected, the user is showed moves to play, rules of the game, and winning/losing criteria. The user choose “back” button to come back to main menu IV. If “Exit” is selected the user is prompted if they really want to exit. “OK (enter) - Cancel (esc)” option to exit or come back to main menu.

drugamba commented 12 years ago

Any ideas on the Test Cases due today?

Quoting suwiringSIxbert

reply@reply.github.com:

 Game starts with a preload/splash screen, ether when settings (resume from last saved...) or modules (loading sounds, preparing sprites bitmaps or loading game engine may take some significant time...) are being loaded.  Main Menu (made of 4 button) -User selects “play” button to start “New game” or “Resume” -use can set up “options” -user can “exit” Play Options Help Exit I. If play is pressed, then another submenu pops up: New Game Resume If “New Game” is selected the new instances are created and the user plays for how long they want until victory or loss conditions are met. If the user wants to quit game before then (esc button), there is a prompt to “continue playing” or “Save and exit” or “Exit without saving”) If “resume” is selected, the game load from last settings and game states, allowing the user to keep playing like before. II. If “Options” is selected, then a set of settings is displayed: to set character, set number of opponent sprites, audio volume… this menu option is subject to change during game development: the user has option to choose “discard” to cancel chosen options or “done” to return to main menu. III. If “Help” is selected, the user is showed moves to play, rules of the game, and winning/losing criteria. The user choose “back” button to come back to main menu IV. If “Exit” is selected the user is prompted if they really want to exit. “OK (enter) - Cancel (esc)” option to exit or come back to main menu.


Reply to this email directly or view it on GitHub: https://github.com/csce3513/Team18/issues/1

suwiringSIxbert commented 12 years ago

Take a reference to this guide:http://www.c-sharpcorner.com/uploadfile/dommym/a-test-driven-development-tutorial-in-C-Sharp-4-0/

and try to use the little code we have on: http://csce.uark.edu/~aslone/ maybe we will get something

drugamba commented 12 years ago

I created a wiki page of test cases we can work on it and expand our test cases.

drugamba commented 12 years ago

what unit testing did we decide to use?

drugamba commented 12 years ago

yeh we using Dengine for the Game engine . i think we decided to use NUnit for the unit testing . http://xngen.blogspot.com/2010/04/nunit-testing-framework-for-c.html

mxn011 commented 12 years ago

I have checked test-case wiki. Our first release was much easier I guess. Only movement and background. I think we don't have to cover all features on user story. I suggest that test case in wiki should be split into first release and future releases. Of course, we can do much farther if we are capable of.

Sorry for late response

suwiringSIxbert commented 12 years ago

So you mean we can go ahead and commit the code we had before?

mxn011 commented 12 years ago

I think so. Menu, save, and resume would be optional for first release.

aslone commented 12 years ago

Sorry about my lack of input this last week, I've been slacking a little. could someone send me a link to Dengine and explain why we decided to use it?

suwiringSIxbert commented 12 years ago

Here is the link: http://dengine.codeplex.com/ the reason we chose it is that it can be easily integrated with Visual Studio, It just debug open project but I think we can use any better if it is out there because we didn't make long development so far.

aslone commented 12 years ago

I haven't found anything better that's also easily accessible. Ice cream looked promising but it only has a few snippets of code that are open source.

mxn011 commented 12 years ago

Seems like we have to have meeting tomorrow with team viewer or at Acxiom. If we meet up at Acxiom, 1:30 is the best? Or, what time would be good for team viewer because we have to be in front of PC at home.