Thank you very much!!!

Don't do anything, I've already fixed it.

In Java the correct argument order is assertEquals(expected, actual). Because of this SAMPLE tests should be:

import org.junit.Test;
import static org.junit.Assert.assertEquals;
import org.junit.runners.JUnit4;


public class TwiceAsOldTest {
    @Test
    public void testSomething() {
      assertEquals(30, TwiceAsOld.TwiceAsOld(30,0));
      assertEquals(16, TwiceAsOld.TwiceAsOld(30,7));
      assertEquals(15, TwiceAsOld.TwiceAsOld(45,30));
      
    }
}

Fix this, and everything will be alright.

This is my first kata and I have a minimum experience of creating a katas.
Also, I'm not a java programmer.

What should I do to make things work fine?
I have to fix the tests and do the following:
assertEquals (localTwiceAsOld (son, dad), TwiceAsOld.TwiceAsOld (son, dad)); ?

petrosernivka, I had already fixed it, and now sample tests are wrong, again, please check that before approving a fork (even if it's yours ;)).
Fixed it again.

Wouldn't that mean the argument order on the basic tests is backwards as well?

mmmh, well... Might be that I didn't get your message the right way. Well, anyway, forget that.

I thought you were going to fix the kata issue with this fork. And now I realized you've published the fork after Chrono79 have fixed everything through the editor.

why didn't you do it yourself, then

The issues should be fixed by kata author or faulty translation author. And I pretty much don't care.

you're annoying with all of that. "O_o"

:(

and whatever? forking translations of someone else doesn't grant any points or %, so why do you bother that much?

And moreover: why didn't you do it yourself, then? Seriously, you're annoying with all of that. "O_o"

The kata was created just a couple days ago, and the author is still active. Only he can approve/reject translations now.

Can't you just edit it? O_o

Damn, I even did that... x)
well, let's just wait one week to reject this, then... x)

Dunno why but it doesn't allow me to reject it. Maybe I have to wait for a week to do it?

Sample tests had still flipped actual/expected.

Wrong argument order in assertEquals(TwiceAsOld.TwiceAsOld(dad, son), localTwiceAsOld(dad, son));.