Detecting JUnit "tests" that never assert anything -
we used have technical director liked contribute code , enthusiastic adding unit tests. unfortunately preferred style of test produce output screen , visually check result.
given have large bank of tests, there tools or techniques use identify tests never assert?
since that's 1 time operation would:
- scan test methods (easy, junit report xml)
- use ide or other search references assert.*, export result list of method
- awk/perl/excel results find mismatches
edit: option references system.out or whatever preferred way output stuff was, tests won't have that.
Comments
Post a Comment