Wednesday, October 08, 2008

Principles of Testing - Separate Testers and Developers

Testers and Developers should be different people.Why???(this is from Utest community)

This may be one of the more controversial and difficult principles
of testing, but it’s also one of the most important.  Quite simply, the
same group of people should not do both your development and testing.

Now let’s be clear: this is not to say that developers shouldn’t do
testing.  They should, and they should be highly involved with any
testing process.  What this principle says is that developers should
not be the only people doing the testing and that there should also be
separate testers as well.  To know the, few reasons why? Click here...


, , , , , ,

Powered by ScribeFire.

Has Google Changed the Meaning of “Beta?”

      This piece of information about the beta products google has and what is the percentage of them are beta? This is also from a blog in
      A recent study has shown that 49% of Google’s products are in beta.  That’s incredible, especially considering that these products include Gmail, Google Docs, and more.  So what does beta really mean to Google?  NetworkWorld asked them and found out:
      “We have very high internal metrics our consumer products have to meet before coming out of beta. Our teams continue to work to improve these products and provide users with an even better experience.  We believe beta has a different meaning when applied to applications on the Web, where people expect continual improvements in a product.  On the Web, you don’t have to wait for the next version to be on the shelf or an update to become available.  Improvements are rolled out as they’re developed.  Rather than the packaged, stagnant software of decades past, we’re moving to a world of regular updates and constant feature refinement where applications live in the cloud.”
        The problem with this philosophy is that customers may not stick around long enough for a product to take off.  If it doesn’t do what they expect upon launch, then they will abandon the platform until it meets their expectations.  In many cases, they may not come back at all. To know more about this topic, Click here...


, , , , , , , , ,

Powered by ScribeFire.

When to Stop Testing: The Customer’s View

          This is a great information shared by a customer on Utest community. I have taken few words from him to share with you and also added the link at the end for your reference.
          On our forum, there’s a discussion about when to stop testing software - when enough testing is enough.  There are a lot of good answers in the discussion, but one that I wanted to highlight is the voice of the customer.

         The customer expects certain things from their software.  A consumer may not care if the software crashes once in a while, but a business may expect greater reliability.  It doesn’t matter if a game displays a single pixel in the wrong color, but it does matter if every time the player opens a treasure box the entire screen turns purple. To know about the customer needs, you have to click on this link...


, , , , , , ,

Powered by ScribeFire.