add stresstesting scripts

[Alls-DeV]

compare.sh wrong slow generator numTests

• wrong, slow and generator are respectively the executables of the two solutions and of the testcases generator

• compare the outputs of two solutions of a problem, checking if they give the same outputs

• for generate test case use uid(a, b) that generate a randomic number from [a, b]

  #define uid(a, b) uniform_int_distribution(a, b)(rng)
  mt19937 rng(chrono::steady_clock::now().time_since_epoch().count());

---

validate.sh solution validator generator numTests

• solution, validator and generator are respectively the executables of the solution, validator of a solution and of the testcases generator
• validator should return OK or the string that explain the error
• validator first take in input the generator input and next the program output

[DannyAntonelli]

We have to add the latex to include the changes in the pdf. Do we want to keep the examples in the repository? Having them in the pdf doesn't make sense.

@dp1 is it okay for you to keep these files in the tests/ folder even though they are unrelated to the unit testing you're adding?

[dp1]

I like this PR, it seems quite involved to get stresstesting for all the booklet code, but it's good to have specific algorithms (e.g. geometry, maths) stresstested on a case by case basis.

[dp1]

@DannyAntonelli I'm not sure what you mean with changes to the PDF, intuitively stresstesting shouldn't influence the final booklet. Am I missing something?

I'd also like to keep unit tests and stress tests as logically separate things, so maybe we could move this out into a stress-tests folder outside of tests (i.e., move the current stresstest folder outside of tests)

[dp1]

One more thing, the examples are ok to have, but maybe we should have "real" stresstests as examples like we're starting to do in #30

[DannyAntonelli]

@alls-cpp's idea is to put it in the booklet so that during the competition you can test the solution and see where it fails. That's how he usually uses these scripts, isn't it?

[dp1]

Oh I see, I got the intent of this pr wrong. Yeah if this is to be used during the contest, we need to add some latex in content/ and move the scripts somewhere else, either in content/ itself or in source/. Maybe a subfolder in source?

[dp1]

Would \snippet not work here?

[dp1]

Suggested change

	\texttt{compare.sh wrong slow generator numTests}
	\texttt{./compare.sh wrong slow generator numTests}

[dp1]

Suggested change

	\texttt{validate.sh solution validator generator numTests}
	\texttt{./validate.sh solution validator generator numTests}

[dp1]

I'd move this section to the end of the booklet, since it's not something we're going to use in all contests or at the start of one. We could add a misc section containing this code and potentially more in the future