Tuesday, January 09, 2007

Steve Rowe on "Letting test drive the process"

Just came across a blog post by Microsoft' Steve Rowe called "Letting test drive the process". Steve quotes an article by Richard Collins -- "Test, test and test again" -- and adds his own observations on the practices of involving testers early in the development process, and of building testable interfaces into the product instead of heavy UIs.

According to Steve Rowe, Microsoft's development and testing process follows these recommended practices. I quote Steve:

"Also, at Microsoft, testing begins from day one. Every product I've ever been involved with at Microsoft has had daily builds from very early on. Every product has also had what we call BVTs (build verfication tests) that are run every day right after the build completes. If any of their tests fail, the product is held until they can be fixed."

Hmmm...I would expect Microsoft to have less problems with their products in this case. But I think a couple of problems that plague Microsoft in particular are backwards compatibility and the sheer amount of hardware/OS/service pack combinations that they need to test.

Speaking of Microsoft and testing, I found The Braidy Tester's blog very informative.


AlexanderIII said...

hi, Grig!
First, please accept my appologize for the chinese translation of your article "Performance Testing vs. Load Testing vs. Stress Testing".
Now, I'm requesting the late permission(including other articles on your blog) from you.
I promise the translation will not be used as any commercial purposes until receiving your permission.

It has been posted on my blog.

my email address is CNAlexanderIII@gmail.com

Best wishes from AlexanderIII in China.

Grig Gheorghiu said...

Alexander -- I grant you permission to translate my blog posts into Chinese, but I want to make it clear that you do not have my permission to use them for any commercial purposes. My posts are released under the Creative Commons license "Attribution-NonCommercial-ShareAlike 2.5". Details here:



Anonymous said...

I guess that's SOP that before any product or whatever will be launch or be introduce to the public, it should undergo any performance or load test.

Modifying EC2 security groups via AWS Lambda functions

One task that comes up again and again is adding, removing or updating source CIDR blocks in various security groups in an EC2 infrastructur...