[HN Gopher] Test Sizes (2010)
___________________________________________________________________
Test Sizes (2010)
Author : thunderbong
Score : 18 points
Date : 2024-04-24 07:12 UTC (1 days ago)
(HTM) web link (testing.googleblog.com)
(TXT) w3m dump (testing.googleblog.com)
| acrophiliac wrote:
| Dear Mr. Stewart, I'm glad that this strategy works for your
| organization, but personally, this sounds like a terrible idea.
| It's as if I was a carpenter organizing my tools and instead of
| wrenches, hammers, and saws I call them small, medium, and large
| tools. Why would you deliberately omit any reference to their
| function or role?
| tantalor wrote:
| To some extent, people do organize their tools like that.
|
| Big stuff has constraints on space, access, materials loading,
| special power, safety etc
|
| I don't mean you put all the big stuff in the same spot. But if
| you consider them all as "the big stuff" then you can plan your
| shop around them and gain efficiency.
|
| Same for the small stuff, they have different needs like
| drawers, hangers, etc.
| malkia wrote:
| check any major cloud provider - dozen of different vm sizes
| pfdietz wrote:
| Where do tests with unlimited running time fit in that? For
| example, fuzzing or property based testing, where you can
| potentially continue running the tests forever, hoping new bugs
| show up.
| malkia wrote:
| This is reflected in bazel - https://bazel.build/reference/test-
| encyclopedia#role-test-ru... - one can mark the tests in terms of
| their expected time to finish, and their memory usage, but also
| whether it can run together with other tests, etc.
___________________________________________________________________
(page generated 2024-04-25 23:02 UTC)