unit testing - Test Method order: lower level tests first? -


case in point:

1) 1 particular test method tests low-level feature. let's tests instance factory. 2) lot of functions depend on 1 low-level thing.

now, low-level thing broken, , test method fails.

do want see buried under hundreds of other failed tests of functionality relies on it? or want see 1 primary failure?

just instance of think you'd want have some ordering of test method execution, namely: lower levels before higher ones.

note not imply dependency order of test methods execution. no test method needs result or state other test.

personally i'd rather have error messages warn me of scope of problem - if run unit-tests frequently, you'll know changed break them.


Comments

Popular posts from this blog

android - Spacing between the stars of a rating bar? -

aspxgridview - Devexpress grid - header filter does not work if column is initially hidden -

c# - How to execute a particular part of code asynchronously in a class -