The proposed tests are a sample of what is submitted.

There is in the submitted version some random tests. So if it doesn't pass the first time it's not going to pass the 50th time.
I suggest you to write your code not to try to beat my tests but to answer the problem. If your solution fail, print out the arguments passed and write other unit tests to see what's wrong in your solution.

Forgive my ignorance, but when I use the given unit tests, mine is passing, but when I try to Submit it, it's failing some arbitrary tests.

Are these test outlined some place where I can actually test against them and try to figue out how my solution is failing, or is it more of a 'submit it until your code passes all tests' etc?

Coding is like driving, don't code and drink, that's dangerous.
I re-wrote the description, if it was really necessary.

Seems pretty clear to me ("check if a number n is divisible by all OTHERS numbers", then you get examples down below): any suggestion to improve it or idea about where the ambigous parts are :)?