The open-source launch of Chrome OS was announced today, and the source is available to download and build
http://www.chromium.org/chromium-os. The entire project, including testing, is being open-sourced and made available for scrutiny and to help others to both contribute and learn from our experiences.
The test engineering team haven't been idle - we're a small, international team and as a result we're having to be innovative in terms of our testing so we maximize our contribution to the project. We had two goals: to take care of short-term release quality and to plan an automation infrastructure that will serve the operating system for many years in the future.
Currently we're combining manual and automated testing to achieve these goals. The manual testing provides fast feedback while we're extending the use of test automation to optimize future testing. In terms of test automation, we're using a collection of open-source tools such as:
There are some interesting plans and ideas afoot on how to significantly increase the testability and accessibility of Chrome OS - watch for future blog posts on these topics in the coming months!
We have used various approaches to design our tests, including 'tours' (mentioned in various posts on this blog). We are also applying the concept of 'attack surface' used in security testing more generally to determine what to test, from both technical and functional perspectives.
For the launch we devised the 'early-adopters tour'; where we validated the open source build and installation instructions on a collection of netbooks purchased from local stores (we expect many of you will want to build and run Chrome OS on similar machines).
If you're one of the early adopters - have fun building, installing and running Chrome OS and post your comments and ideas here. We hope you enjoy using Chrome OS as much as we're enjoying testing it!
I was wondering if it would be possible to be used in different architectures and older devices?
ResponderEliminareg arm based.
Probably a very very very long shot, but just daydreaming
thanks
Chrome OS is here to test... A much anticipated piece of cool stuff by testers as it was supposed to be open source in testing as well...
ResponderEliminarGreat work!!! Congratulations!!!
ResponderEliminarCheers
Diego
What exactly U guys tested for Chrome OS ..?? Can u please share u r TC list.
ResponderEliminar@Nicholas - The source code is available now and you're welcome to try it on older devices, or to port it to other hardware architectures e.g. to ARM-based systems. An earlier official blog post mentions ARM explicitly http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html
ResponderEliminar@tabbasi & @ Piyush - tests are being provided as part of the project e.g. http://git.chromium.org/viewvc/chrome/trunk/src/testing/
We will post more material in the coming months, both the actual tests, and on how we test, our experiences and results, etc.
@Diego - thank you :)
Have you used xUnit framework to drive your Selenium tests or you've developed your own engine?
ResponderEliminarthanks
Where is Selenium testing scripts? If any. I can only find autotest.
ResponderEliminarThanks
I cannot find where selenium testing scripts are. Could you point it out?
ResponderEliminarThanks
Eric
Can we run automation in Chromebook?
ResponderEliminarwhich automation tool is used to automate chrome app & how to run same tests on Chromebook?
ResponderEliminarDoes it possible to run automation test for packaged app in chromebook device itself. which APIs ( like selenium, protractor, appium) we can leverage to do the same. could anyone please guide here.
ResponderEliminarCan you share how to testing chrome using TDD
ResponderEliminar