Hi, I'm using the google testing banner (the red & green bulbs) as the unofficial logo for my testing lectures in a [software engineering course](https://github.com/jce-il/se-class/wiki) Thanks!
Hi, I regularly refer to articles from this blog when discussing or advising colleagues about testing / engineering best practises. In addition, several articles have been a big source of inspiration for company-wide standards and guidelines with respect to software testing. Thanks for the great blog!
I use articles from this blog in a Masters Level Course on Software Testing, that I teach. I also encourage students to read this blog. Thanks for the excellent content, and for making this available.
Back in 2009 I started reading Misko Hevery's articles about designing for testability and Dependency Injection. I have witnessed the transformation of the PHP community from procedural code to true object-orientation, also thanks to these patterns which are now pushed by every decent framework.
Happy Birthday! I firstly read the new explanation of test engineer role is here! Although I don't comment much here, but I hope this test blog is always the best place we can learn and share new idea of testing.
Hey all I just wanted to say thanks! I have been a reader for several years. I regularly refer to articles from this blog when discussing or advising colleagues about testing / engineering best practises. Test technologies and codeless testing
I'm late to wish you a happy birthday. I have enjoyed this and many other Google tech blogs
I found you today because I wanted to get some understanding of code coverage analysis on large-scale projects. We have a pretty big codebase (>5M C# loc) and a big investment in integration testing (goes to the database). Our testing is costly and hard to measure coverage with standard tools, so we built our own. It was useful to read about how you do it. I'm glad I found that you measure median rather than mean coverage.
And next I found your front-page article is about flaky tests. We have a bunch of those too. We don't have any predictor for them, but our application is in the financial sector and we have some tests that fail on a certain day of the month or week.
Hi, I'm using the google testing banner (the red & green bulbs) as the unofficial logo for my testing lectures in a [software engineering course](https://github.com/jce-il/se-class/wiki)
ReplyDeleteThanks!
I am constantly checking this blog to find out insightful knowledge about testing.
ReplyDeleteThanks Googlers for sharing.
Hi, I regularly refer to articles from this blog when discussing or advising colleagues about testing / engineering best practises. In addition, several articles have been a big source of inspiration for company-wide standards and guidelines with respect to software testing.
ReplyDeleteThanks for the great blog!
I use articles from this blog in a Masters Level Course on Software Testing, that I teach. I also encourage students to read this blog.
ReplyDeleteThanks for the excellent content, and for making this available.
Back in 2009 I started reading Misko Hevery's articles about designing for testability and Dependency Injection. I have witnessed the transformation of the PHP community from procedural code to true object-orientation, also thanks to these patterns which are now pushed by every decent framework.
ReplyDeleteHappy Birthday! I firstly read the new explanation of test engineer role is here! Although I don't comment much here, but I hope this test blog is always the best place we can learn and share new idea of testing.
ReplyDeleteHey all I just wanted to say thanks! I have been a reader for several years. I regularly refer to articles from this blog when discussing or advising colleagues about testing / engineering best practises. Test technologies and codeless testing
ReplyDeleteIt's been very helpful!
ReplyDeleteThanks!
I'm late to wish you a happy birthday. I have enjoyed this and many other Google tech blogs
ReplyDeleteI found you today because I wanted to get some understanding of code coverage analysis on large-scale projects. We have a pretty big codebase (>5M C# loc) and a big investment in integration testing (goes to the database). Our testing is costly and hard to measure coverage with standard tools, so we built our own. It was useful to read about how you do it. I'm glad I found that you measure median rather than mean coverage.
And next I found your front-page article is about flaky tests. We have a bunch of those too. We don't have any predictor for them, but our application is in the financial sector and we have some tests that fail on a certain day of the month or week.
Thanks for the good reading. Keep it up.