t-wadaのブックマーク - はてなブックマーク

SMURF: Beyond the Test Pyramid
TotT 104 GTAC 61 James Whittaker 42 Misko Hevery 32 Code Health 31 Anthony Vallone 27 Patrick Copeland 23 Jobs 18 Andrew Trenk 13 C++ 11 Patrik Höglund 8 JavaScript 7 Allen Hutchison 6 George Pirocanac 6 Zhanyong Wan 6 Harry Robinson 5 Java 5 Julian Harty 5 Adam Bender 4 Alberto Savoia 4 Ben Yu 4 Erik Kuefler 4 Philip Zembrod 4 Shyam Seshadri 4 Chrome 3 Dillon Bly 3 John Thomas 3 Lesley Katzen 3 M
t-wada 2024/10/16
大きめの自動テスト群の設計時に考慮すべきトレードオフを頭文字SMURFで整理。Speed（スピード）、Maintainability（保守性）、Utilization（リソース使用率）、Reliability（信頼性）、Fidelity（忠実性）をレーダーチャートで可視化
リンク
How Much Testing is Enough?
I think it's worth underlining that coverage mainly tells you about code that has no tests: it doesn't tell you about the quality of testing for the code that's 'covered', especially if it's only line-coverage - branch/condition coverage is more informative there. ReplyDelete
t-wada 2021/06/18
1.プロセスと戦略を明文化 2.テストピラミッド構築（a.強固なユニットテスト基盤 b.結合テストをけちらない c.重要なカスタマージャーニーにE2Eテスト） 3.その他のテストに気を配る 4.カバレッジで現状把握 5.改善を回す
リンク
Test Sizes
Small tests should be isolated from each other, but this constraint gets in a way of medium and large tests (especially for web testing). Take a look at what users are doing with Selenium + TestNG. Also, dependencies and high parallelism are not mutually exclusive, it's unfortunate that this rumor is still around. Here is why: http://beust.com/weblog/2009/11/28/hard-core-multicore-with-testng/ Rep
t-wada 2016/08/15
クックパッドの取り組みのもとになった Google の試み

testing

google
リンク
1