This is really interesting insight. Just curious, why do you do your Test Channel phase after the Devs use it for every day work?
Engineers using our applications is something I'm trying to encourage at my company currently. I was hoping to have it as a later phase though- after QA has been part of writing acceptance tests, ironing out the functionality and getting the application in good working order. I guess my thought would be, having the devs use it after would help flesh out any remaining bugs after QA has torn it apart, instead of having to deal with some of the low hanging issues that QA can clear up right away.
Canary Channel- I feel this is great point.But one question that comes to my how do you decide code is not fit to release ? So I assume that google has acceptance criteria for moving product into testing. Also the way google does beta had always fascinated me, yes gmail if I am right had long inning in beta.Then I believe GTalk is still in beta. Question I have here is which is more profitable , releasing product to the beta stage or having a team of tester fixing all those bugs and having little room of risk for production fix. Also if I am right, google might be only company to earn revenues via beta releases.They did display lot of ads in gmail beta.
Hi James, can you share your thoughts about the difference between how Google tests and how Microsoft tests? pros/cons, or just your general impressions?
Just wondering, with small iterations of development and testing, what test documentation is used at google for manual testing? as time is a factor as with most agile projects, creating a long test script as found in v-model projects is obviously not feasible . . .
Answers are coming I promise. Not sure about Google v MS issue though. That one might be better left for a conference where a two way discussion with some Microsoft engineers in attendance for point/counterpoint.
Have a curiosity , As you told gmail went as a beta for around 4years and went live only once you reached 99.9% uptime, so with this you are showing that quality is an ongoing process and less testers are needed. However one thing i would like to point is, Gmail can go as beta for four years however what do you suggest when there is a strict deadlines on a project (not talking about the product based companies), they have to ship it, not beta though!! What are your suggestions in those circumstances? Customers can't wait for 4years when there is a strict requirement from the end user.
This is really interesting insight. Just curious, why do you do your Test Channel phase after the Devs use it for every day work?
OdpovedaťOdstrániťEngineers using our applications is something I'm trying to encourage at my company currently. I was hoping to have it as a later phase though- after QA has been part of writing acceptance tests, ironing out the functionality and getting the application in good working order. I guess my thought would be, having the devs use it after would help flesh out any remaining bugs after QA has torn it apart, instead of having to deal with some of the low hanging issues that QA can clear up right away.
James,
OdpovedaťOdstrániťFantastic observation - quality is a work in progress!
It would be interesting to understand how Google test cross-browser compatibility of Chrome. Do you guys use any tools ?
Thanks
Sri
Canary Channel- I feel this is great point.But one question that comes to my how do you decide code is not fit to release ?
OdpovedaťOdstrániťSo I assume that google has acceptance criteria for moving product into testing.
Also the way google does beta had always fascinated me, yes gmail if I am right had long inning in beta.Then I believe GTalk is still in beta.
Question I have here is which is more profitable , releasing product to the beta stage or having a team of tester fixing all those bugs and having little room of risk for production fix.
Also if I am right, google might be only company to earn revenues via beta releases.They did display lot of ads in gmail beta.
- Kiran Badi
Hi James,
OdpovedaťOdstrániťcan you share your thoughts about the difference between how Google tests and how Microsoft tests? pros/cons, or just your general impressions?
thanks!
Ted
Just wondering, with small iterations of development and testing, what test documentation is used at google for manual testing? as time is a factor as with most agile projects, creating a long test script as found in v-model projects is obviously not feasible . . .
OdpovedaťOdstrániťTremendous insight and technical wisdom! Thanks!
OdpovedaťOdstrániťAny updates on Testify aka Google Test Analytics? Can't wait to get my HUD going!
Answers are coming I promise. Not sure about Google v MS issue though. That one might be better left for a conference where a two way discussion with some Microsoft engineers in attendance for point/counterpoint.
OdpovedaťOdstrániťhello sir
OdpovedaťOdstrániťi have used loadrunner 9 version the probelm is i can record the image file but run time i cannot see thatimage what can do
hi James,
OdpovedaťOdstrániťHave a curiosity , As you told gmail went as a beta for around 4years and went live only once you reached 99.9% uptime, so with this you are showing that quality is an ongoing process and less testers are needed. However one thing i would like to point is, Gmail can go as beta for four years however what do you suggest when there is a strict deadlines on a project (not talking about the product based companies), they have to ship it, not beta though!! What are your suggestions in those circumstances? Customers can't wait for 4years when there is a strict requirement from the end user.