approved

Thanks for approving it ^-^

Like this?

address my last remark above and I think it'll be approvable.

I fixed the different style problem

the test block Should return a boolean adds no value and should be removed. the asseertion messages and the description make it clear that a boolean is expected. to make it extra clear you can add return true; in the initial code if you want.

you addressed my first point but not the second ;-)

Fixed!

• why are randInt() and reference() defined twice ?
• the random tests weighed towards true should use the same style as those weighed towards false. in one case you use a it() block for all the assertions, in the other a describe() with a it() for each assertion: use the same style for both. both styles are fine, but the input should be shown in any case (either in the first parameter of it() , or in the 3rd optional parameter of strictEqual()

Fixed!

• good, you addressed my first point :)
• but the second still stands. remove these forward let declarations, use const instead at the site of the assignment.
• The random number generation is hard to follow (because you do not use a randInt(from, to) function) and they are wrong, because they generate number with decimals instead of integers. Use a randInt() function like that one:

function randInt(from, to) { // inclusive of from and to
  return Math.floor(from + Math.random() * (to - from + 1));
}

Then instead of:

tz_f = Math.random()* (12 - 1) + 1

You can write:

const tz_f = randInt(1, 11);

which is much more legible.

• the block

  it("testing for"+expected,function() {
  

  does not add anything, because the expected value will already be shown to the user by the test framework
• the reference solution is duplicated twice in the tests, you should erase one of them and move it to the describe('random tests' scope

I think I fixed it

• you are using the deprecated Codewars test framework instead of mocha + chai. you should use assert.strictEqual() from chai
• declaring all of those variables far away from the place where they are actually used is really bad practice. always narrow down the scope of your variables as much as possible. and in JavaScript specifically, always prefer const over let when possible, and let over var when possible

Javascript Translation!