Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Lol, I think most of that randomness is somewhere in the test directories.


sort by: page size:

My thoughts exactly. Randomness has a place in tests, but not in unit tests.

Hmmm but if you change the distribution, this won't be deterministic anymore unless the randomness only applies to new users entering the test setup.

Where you say random I think you mean systematic.

Well, it's totally random alright.

Not sure if I'd describe them as random, but yeah.

Yes, randomness!

Yet every run still has many thousands of RNG invocations for that particular metric. To be off by a few percent, safe to say that RNG would fail any randomness test.

I mean, unless you know all the variables in the feature scope it is pretty much random...

It's just randomness.

Hmm this made me chuckle, is that not equivalent to a test for randomness, which is very very hard indeed?

Except it's "stuff I queried", which is pretty random. Or at least not predictable before being tried, which is nearly as good.

Besides, geeks like to shrink things. I wouldn't have been surprised if it used "rand(YC application videos)", to save a character.


Well, it's deterministic, because the program is deterministic, but it certainly does look random.

Randomness

That is very much not random, but generally enough for 99% of all use cases.

More random, I'd say.

Pretty sure those are random too.

random was what came to my mind after your first sentence. It could really use a deterministic test harness for the different layers.

That definitely is quite... random!

Sometimes it is just random.
next

Legal | privacy