Smart Client Bug Reporting Challenge

Smart Client Bug Reporting Challenge

"Calling all smart client developers! Want to win a cool Visual Studio .NET branded backpack or T-shirt? Want to help the Windows Forms team ship an amazing product? If so, come enter the Bug Reporting Challenge Contest. It’s super simple—you find a bug in Windows Forms or ClickOnce, then you file the bug you found using the Microsoft Product Feedback Center. If it's a bug that the Windows Forms or ClickOnce teams fix for Whidbey, or it's a bug we'd like to fix but have to postpone for some reason, then you get 1 credit. Each month we will hand out 1 backpack and 3 T-shirts for the top 4 bug finders. Come back and enter as often as you have a bug.

Why are we doing this, you ask? When we looked at the bug stats filed by the community through the Feedback Center, we found that over 30% of code defect bugs submitted were being fixed in the product. This is a really high number when you remember that the builds the community have are not the most up-to-date ones that the team has (e.g. another 30% are not repro by our team—meaning that we already fixed it by the time that the bug came in). We wanted a way to say "thank you" to all the people who have been finding the great bugs in the product that we are fixing, so we came up with this contest."

I'm really excited to see how the contest goes.  The Winforms team is one of the top two teams in terms of # of bugs reported on the Product Feedback Center and they have found the bugs reported so far to be very helpful.  It seems you've been reporting bugs anyway, but now you can win something for doing it! Good Times

Comments (9)
  1. Matt says:

    Just a T-shirt? And not even a T-shirt per bug!

    Good luck getting people to spend any time with this. You don’t really expect "free" QA do you? How about a free MSDN subscription or something a little more worthwhile!

  2. josh ledgard says:

    Having come from the QA world at Microsoft I can tell you that VS would come out well tested with our without bugs from customers.

    We’ve had the feedback center up for a while and this is a small step towards what could be bigger contests/rewards to come. Right now people are posting bugs and workarounds without getting anything but the satisfaction of a response from the actual developer/PM working on the orrigional code. Try getting that from many other large companies.

    Trust me, we are looking into ways of rewarding people accross the board when we ship Whidbey, the Winforms team just took some initiatives to do something now.

  3. Norman Diamond says:

    11/24/2004 1:05 PM josh ledgard

    > Having come from the QA world at Microsoft I

    > can tell you that VS would come out well

    > tested with our without bugs from customers.

    Having been a Microsoft customer, I can tell you that with VS, just like other Microsoft products, versions other than US-English often look like they haven’t been tested. And even US-English versions don’t always look like they’ve been tested if the character set isn’t ASCII, for example converting to a wide character string even when the source string is ASCII.

  4. Norman Diamond says:

    By the way it’s only on rare occasions that we even get to do QA for free. Usually we have to pay Microsoft in order to do QA for Microsoft, either by paying for a support incident or by purchasing an MSDN subscription. Sometimes even MSDN subscribers are told to pay again to submit a support incident concerning a VS bug. (I declined to do so.)

  5. Marc Bernard says:

    > Having come from the QA world at Microsoft I

    > can tell you that VS would come out well

    > tested with our without bugs from customers.


    > Having been a Microsoft customer, I can tell

    > you that … VS … often look like they

    > haven’t been tested.

    I second that emotion. Try opening a solution with lots of projects in it – go for coffee.

    Try using inherited WinForms – forget about being able to use the forms designer.

    Try using more than one monitor – watch the phantom windows appearing and disappearing at will on the second monitor.

    Try making a reference to a DLL larger than 64k – can’t copy it? Why not?

  6. josh ledgard says:

    Wow, some bitter customers on Thanksgiving. Sorry there are things that have dissapointed you guys about our releases. I doubt there is another product with the Scope of VS that doesn’t have its kinks.

  7. Norman Diamond says:

    Well, sure I was somewhat bitter about Thanksgiving (Nov. 23rd) being a working day in my present employer, but that had nothing to do with your company. Same for the Emperor’s birthday (Dec. 23rd) by the way, and both of these are legal holidays.

    Anyway, true bitterness towards your employer derives from the amount of damage done by your products (particularly Windows 95) combined with reneging on asserted warranties (Windows 95, Windows 2000, Windows XP, Windows Server 2003, Visual Studio 2003, and MSDN subscriptions, among others). Yeah sure MSDN doesn’t have special warranties attached, but your company sent a pamphlet asserting the same customary 90-day pretence of a warranty and then promptly reneged on it.

    Bitterness is not really about your betas. Bitterness might derive from doing beta QA for you and seeing the same bug released, but true bitterness comes from paying for the bug itself and then being told to pay again in order to report the bug. Even with Windows 95, which destroyed so much disk data that no amount of bitterness can match it, the bitterness didn’t really start until discovering how many lies your company had told in its fake warranties.

Comments are closed.

Skip to main content