ray-print / rambling-harmonicas-blackjack Goto Github PK

add Travis gate job to do full tests on commits, and also if supported run program and ensure no crash occurs
Check that the .tar, .zip, and installation file works; check that dev environment is correctly set up when git cloned.

-Upgrade command line parser and Gradle
-Refactor to try-with-resources, use lambdas where appropriate, etc.
Blocked 'cause my computer is old and doesn't even support Java 1.7. haha.

-Add option to force calculation and display EV. Show calculcation time.
-Consolidate second-best advice option with first where appropriate ("Dh" for hard total 11, for example). Make this the default behavior; if not displaying EV, only show this abbreviation, and don't show it in cases where it's not relevant (like if the first action is "Hit", since hitting is always possible)
-Add text description of "H","S", "Y", etc. (a legend)
-Prettify Rules description (have Rules.prettyString() to print a sanitized version of toString)
-Add basic tests for command line output (no exceptions thrown, output produced)

cacheStatus
dealerProbabilitiesCache
cacheInitialized
hits

Requires editing calculation functions. Blocked pending tests refactoring.

This is a pretty standard feature that this calculator doesn't have yet.

This is not trivial because certain features in Rules are used for computation and should not be visible outside of the package. FastShoe likewise is a package-private type thing.

Start versioning program
-should be on jar and any dists
Set up resources directory with standard Gradle structure

Calculations seem to be going 4x or more slower than they used to go. (~40 seconds to solve a rule set as opposed to 10 or so) Set up profiler to debug this. This could also just be an issue with a cache setting or the Rules accuracy setting -- those should be investigated first.