Re: C++ fluency
On May 12, 6:21 pm, "Phlip" <phlip2...@gmail.com> wrote:
James Kanze wrote:
Each unit test checks only a single set of input. Most
functions have billions of possible input, if not more. How
exhaustive do you test? (The answer, of course, depends.
But given the non-linearity of computer logic, you often
need quite a few.)
Given a website with 50 different skins (CSS folders), I
tested all the skins like this:
max = SLOW_TESTS ? 50 : 5
skins.sort_by(&:rand)[0..max].each do |skins|
test_this_one(skin)
end
You integrate in FAST_TEST mode, and only test 5 random skins.
The test server runs in SLOW_TEST mode.
That sounds like a good idea. Not sure how to integrate it into
my makefiles, however---maybe two separate targets (localbuild
and export?). (Obviously, choosing all of the tests randomly
isn't always the best solution, but you can probably find a
reasonable subset somehow.)
Oh, and any skin-specific tests that you just changed in the
last 10 minutes run when you integrate, too.
That will be a bit trickier to add to the makefile:-).
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34