�ݺ�ߣshows by User: patricklam3382

�ݺ�ߣshows by User: patricklam3382 / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: patricklam3382 / Thu, 30 Oct 2014 19:04:10 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: patricklam3382 GTAC 2014: What lurks in test suites? /patricklam3382/gtac-2014-what-lurks-in-test-suites gtac2014whatlurksintestsuites-141030190410-conversion-gate02
We all want "better" test suites. But what makes for a good test suite? Certainly, test suites ought to aim for good coverage, at least at the statement coverage level. To be useful, test suites should run quickly enough to provide timely feedback. This talk will investigate a number of other dimensions on which to evaluate test suites. The talk claims that better test suites are more maintainable, more usable (for instance, because they run faster, or use fewer resources), and have fewer unjustified failures. In this talk, I'll present and synthesize facts about 10 open-source test suites (from 8,000 to 246,000 lines of code) and evaluate how they are doing.]]>
We all want "better" test suites. But what makes for a good test suite? Certainly, test suites ought to aim for good coverage, at least at the statement coverage level. To be useful, test suites should run quickly enough to provide timely feedback. This talk will investigate a number of other dimensions on which to evaluate test suites. The talk claims that better test suites are more maintainable, more usable (for instance, because they run faster, or use fewer resources), and have fewer unjustified failures. In this talk, I'll present and synthesize facts about 10 open-source test suites (from 8,000 to 246,000 lines of code) and evaluate how they are doing.]]> Thu, 30 Oct 2014 19:04:10 GMT /patricklam3382/gtac-2014-what-lurks-in-test-suites patricklam3382@slideshare.net(patricklam3382) GTAC 2014: What lurks in test suites? patricklam3382 We all want "better" test suites. But what makes for a good test suite? Certainly, test suites ought to aim for good coverage, at least at the statement coverage level. To be useful, test suites should run quickly enough to provide timely feedback. This talk will investigate a number of other dimensions on which to evaluate test suites. The talk claims that better test suites are more maintainable, more usable (for instance, because they run faster, or use fewer resources), and have fewer unjustified failures. In this talk, I'll present and synthesize facts about 10 open-source test suites (from 8,000 to 246,000 lines of code) and evaluate how they are doing. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/gtac2014whatlurksintestsuites-141030190410-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> We all want "better" test suites. But what makes for a good test suite? Certainly, test suites ought to aim for good coverage, at least at the statement coverage level. To be useful, test suites should run quickly enough to provide timely feedback. This talk will investigate a number of other dimensions on which to evaluate test suites. The talk claims that better test suites are more maintainable, more usable (for instance, because they run faster, or use fewer resources), and have fewer unjustified failures. In this talk, I'll present and synthesize facts about 10 open-source test suites (from 8,000 to 246,000 lines of code) and evaluate how they are doing.

GTAC 2014: What lurks in test suites? from Patrick Lam

]]> 361 4 https://cdn.slidesharecdn.com/ss_thumbnails/gtac2014whatlurksintestsuites-141030190410-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-patricklam3382-48x48.jpg?cb=1523384030