Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
If there are test cases which always expect some specific answer consistently in the same invocation, it makes test cases suspectible to counting. Users can use a global variable to count invocations of their solution, and return
true
,false
, orNone
or some other predictable result for every expected n-th invocation.This problem might not be especially relevant for some kata, the most affected kata are the ones which expect
bool
as an answer, but the general practice is that for random tests, the expected results (and their order) should be unpredictable This can be achieved for example by generating a list of inputs for all tests, and then shuffling the list.From spec:
Approved.
Tests for returning None, returning empty chessboard, returning [] have been implementend
Sample tests are still unfixed.
fixed
Issue: JUnit uses
assertEquals(expected, actual)
argument order.Since JDK 17
java.util.Random
implements theRandomGenerator
interface which provides default implementations ofnextInt(lo, hi)
for all random classes. NeverthelessThreadLocalRandom
has the nicer prng algorithm.Math.random()
, really? There areRandom::ints(lo, hi)
, andRandom::nextInt(hi)
, andThreadLocalRandom::nextInt(lo, hi)
today.This means that your code is too long. Note that this kata is a code golf kata, which means that it has a limit of code length:
Merged.
Could you please add a fixed test for the whole alphabet,
"a-zA-Z"
?AreTheySame.comp
is your solution, so probably a call tostring.Join
in your solution crashes.Removes
rand.Seed
since it's not necessary to seed the RNG since Go 1.20.rand.Seed
since it's not necessary to seed the RNG since Go 1.20.Loading more items...