Yes we all are reading and enjoying every bit of it. Waiting anxiously for upcoming posts. Though as you mentioned tools will be covered in future posts but still what is "Industry leading recording technology" that "converts manual tests to automated tests"?
Appreciate your constantly sharing us so many valuable information.
This post mentioned that "The ongoing effort to automate to within the “last inch of the human mind” is currently the design spec for the next generation of test engineering tools Google is building." Is it possible to tell more about the test engineering tools in Google in future posts?
Great series of posts! I do a lot of manual testing and would love to hear more about the industry leading recording technology that converts manual tests to automated tests. I've used Selenium for this in the past but would love to explore alternatives. Thanks!
I really enjoy these posts to discover what other organizations are doing to improve testing. I was particularly interested in the statement involving "Industry leading recording technology..." What does Google use for this or what frameworks seem to be ahead of the rest? We have attempted multiple packages from commercial to OSS, but all of them seem to fall short on driving the browser and are usually fragile.
Doesn't Small-Medium-Large say more about the scope of a test than it does about the type or purpose of the test (e.g. a performance test can be "small" or "large")?
Yes all of this will be covered in future posts. Sorry I am slower to get this information out than I would like. This day job thing is really getting in the way of my writing. Our recording technology is called RPF, the Record Playback Framework. It's a Chrome extension that records to Java Script and does some pretty innovative tricks to solve some of the persistent recording issues on the web. If it helps, we do plan on open sourcing all this and working with other browser companies to make it more universal.
Thanks for the info James. I have an offer for an SET. I already work with as an SDET at a rival company ;). This line in your 3rd post concerns me:"SWEs are testers, SETs are testers and TEs are testers." Do SETs ever get to be devs? More importantly do they get the same level of respect or are they looked down upon as inferior? Say 5-6 yrs down the lane i might want to delve into developing, would that be possible? I am genuinely interested in test but would definitely want the flexibility and environment minus the ego games.
I do manual, performance and automation testing working on Nokia projects. From my point of view, automation testing is worthed only when it's costs (development and maintenance) are not too big. Also the most important aspect for automation testing should be that the aplication is not always changing (UI and code) so you don't need maintenance all the time for automation tests. I guess a mix between automation and manual testing will always work in any company. If anyone is interested in different software topics, visit http://softwaretopics.net - there are some interesting stuff here!
Really informative!! What is the career path of an SET at google? Most SETs/SDETs switch to SDEs because they are not quite sure if they can make a rewarding career technically as an SDET. It would be really helpful if as part of your next post you can cover these aspects as well..
I'm looking forward to possibly test-driving the RPF tool. It's so refreshing to hear your posts/seminars/etc emphasize the importance of the human element in testing. Whether it be automated testing or manual testing, the human eye and human ability of common sense should never be removed from quality software assurance. I look forward to your next posts. Thanks again!
Yes we all are reading and enjoying every bit of it. Waiting anxiously for upcoming posts.
ReplyDeleteThough as you mentioned tools will be covered in future posts but still what is "Industry leading recording technology" that "converts manual tests to automated tests"?
This series is fantastic, thank you.
ReplyDeleteYou mention "Industry leading recording technology" ... can you tell us what that is?
Thank you!
Appreciate your constantly sharing us so many valuable information.
ReplyDeleteThis post mentioned that "The ongoing effort to automate to within the “last inch of the human mind” is currently the design spec for the next generation of test engineering tools Google is building." Is it possible to tell more about the test engineering tools in Google in future posts?
Great series of posts! I do a lot of manual testing and would love to hear more about the industry leading recording technology that converts manual tests to automated tests. I've used Selenium for this in the past but would love to explore alternatives. Thanks!
ReplyDeleteI really enjoy these posts to discover what other organizations are doing to improve testing. I was particularly interested in the statement involving "Industry leading recording technology..." What does Google use for this or what frameworks seem to be ahead of the rest? We have attempted multiple packages from commercial to OSS, but all of them seem to fall short on driving the browser and are usually fragile.
ReplyDeleteDoesn't Small-Medium-Large say more about the scope of a test than it does about the type or purpose of the test (e.g. a performance test can be "small" or "large")?
ReplyDeleteAh man, another great post. Looking forward to future posts, especially on SET's & TE's (?).
ReplyDeleteYes all of this will be covered in future posts. Sorry I am slower to get this information out than I would like. This day job thing is really getting in the way of my writing. Our recording technology is called RPF, the Record Playback Framework. It's a Chrome extension that records to Java Script and does some pretty innovative tricks to solve some of the persistent recording issues on the web. If it helps, we do plan on open sourcing all this and working with other browser companies to make it more universal.
ReplyDeleteThanks for the info James. I have an offer for an SET. I already work with as an SDET at a rival company ;). This line in your 3rd post concerns me:"SWEs are testers, SETs are testers and TEs are testers." Do SETs ever get to be devs? More importantly do they get the same level of respect or are they looked down upon as inferior? Say 5-6 yrs down the lane i might want to delve into developing, would that be possible? I am genuinely interested in test but would definitely want the flexibility and environment minus the ego games.
ReplyDeleteI do manual, performance and automation testing working on Nokia projects.
ReplyDeleteFrom my point of view, automation testing is worthed only when it's costs (development and maintenance) are not too big. Also the most important aspect for automation testing should be that the aplication is not always changing (UI and code) so you don't need maintenance all the time for automation tests.
I guess a mix between automation and manual testing will always work in any company.
If anyone is interested in different software topics, visit http://softwaretopics.net - there are some interesting stuff here!
Hey James,
ReplyDeleteReally informative!! What is the career path of an SET at google? Most SETs/SDETs switch to SDEs because they are not quite sure if they can make a rewarding career technically as an SDET. It would be really helpful if as part of your next post you can cover these aspects as well..
Thank you.
I'm looking forward to possibly test-driving the RPF tool. It's so refreshing to hear your posts/seminars/etc emphasize the importance of the human element in testing. Whether it be automated testing or manual testing, the human eye and human ability of common sense should never be removed from quality software assurance. I look forward to your next posts. Thanks again!
ReplyDeleteHow do you test scalability, load etc. at this enormous scale ? Do you simulate everything ?
ReplyDeleteGreat post, also loved to hear that you guys plan on delivering this tool as open sourced.
ReplyDeleteaccomplish repeate
ReplyDelete