Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added history for commands #7

Merged
merged 2 commits into from
Feb 21, 2015
Merged

added history for commands #7

merged 2 commits into from
Feb 21, 2015

Conversation

born2snipe
Copy link
Contributor

Support for Up and Down going through the previously executed commands

@StrongJoshua
Copy link
Owner

Thanks for doing this :)

What is the CommandHistoryTest for? I've never JUnit before.

StrongJoshua added a commit that referenced this pull request Feb 21, 2015
added history for commands
@StrongJoshua StrongJoshua merged commit efa686e into StrongJoshua:master Feb 21, 2015
@born2snipe
Copy link
Contributor Author

It's an automated test that tests the logic of the CommandHistory class to ensure the behavior is working under known scenarios. So the idea is if you encounter a bug in the logic of that class you would add another test or change an existing test for your new scenario.

JUnit is a popular TDD tool for Java: http://junit.org/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants