Hello Everyone I'm Ruben and I'm gonna tell you "How does Google test Software". Let's ready? Jump in!
Oh come on! Don't go up! We use a lot of Google's products such as its own search engine
native apps on Android devices, the great powerful and useful Google Maps where you search firstly your home
'cause you think that you can watch yourself on the map (Really! people do that, I did it myself
don't fool me! All engineers think that Google test its own software as easily as possible: They mount a
technology on a PC or mobile device, check all features and possible mistakes, and...
Voilà! Hey Siri? Could you find me last photo on the camera roll? Ah no no I'm sorry
I'm sorry, you are not Google Assistant. Ok Google! Could you find me last photo on camera roll?
All right baby that's what I want!!
But if I told you that's not as simple as you think, how are you impressed?
Let me show you some curiosities about Google! Nowadays, Google has not a testing organization.
They have a concept of test called "Engineering Productivity" where exists within a "Focus area"
(That's how Google calls its software products). Eng Prod is made of:
a "Product Team", a "Service Team" and "Embedded Engineers".
A "Product Team" that builds and maintains code analyzers, IDEs, test case management systems
code review schedulers, bug databases...
The idea is to make the tools more productive. A "Service Team" that provides
expertise to Google product teams, including tools, documentation,
testing, release management... They try to resolve product-specific functional issues that Google
product teams might face. And "Embedded Engineers" that test a software on a device during a specific time.
Some of these engineers might be with the same product teams for years, other test
through teams wherever they are needed most. Google encourages all its engineers to change product teams often
to stay fresh, engaged and objective. They try to make
the experience of a engineer the best way possible. So, this means that testers
reports to Eng Prod managers,
Identifying themselves with a product team, like "Search", "Gmail", or "Chrome".
They are part of both teams and works really together.
It provides a forum for testers to share information.
Good testing ideas migrate easily within Eng Prod giving all tester,
accessing to the best technology
within the company. Yes, that's right! The job of the tester is to enable developers to test. This strategy puts
developers and testers on equal footing. The better they would be tests, the better the product would be.
Good job for developers! The thing is:
A developer can't test the product! Google's answer to resolve this is to split the role.
They solve the problem by having some types of testing roles at Google to solve very different
testing problems. The "Software Engineer". They create design documentation, design data structures and overall
architectures and spend time writing and reviewing code, including test driven design,
unit test and participate on the construction of small, medium and large
tests. The "Software Engineering in Test". They review designs and look closely at code quality and risk.
They refactor code to make it more testable. They are more concerned with increasing quality and
test coverage than add new features or
increasing performance. In other words, the "Software Engineer in Test" write code that allows
"Software Engineer" to test their features. The "Test Engineer" is the exact reverse of the "Software Engineer in Test". They put
testing first and development second. Many Google "Test Engineers" spend a good deal of their time
writing code in the form of automation
scripts and code that drives usage scenarios and even mimics a user. They also organize the testing work of
the "Software Engineer and "Software Engineer in Test", interpreting test results and drive test execution.
Ok, but the big question is: What about the user? User focused testing is the job of the Google
"Test Engineer". The next task is to understand how the features works together
to satisfy the needs of the user. For Google the quality of its
products is very important. So, next question we can ask ourselves:
How does one decide if what you built is high quality without testing it? The thing is: "Quality is not
equal to test". The solution is to do that testing and development go hand in hand. In development, it's
tested and codified together. The goal is to merge development and testing so that you can't do one without the other.
Build a little and then test it!
Build some more and test so more! "Quality is a development issue, not a testing issue".
Thanks for watching, and I hope you like this video. Give me a thumb-up and we'll see you on the next video! Bye!
For more infomation >> Xóa MK Và TK Google Samsung Galaxy J7 Pro | Hard Reset Samsung Galaxy J7 Pro | Góc Tin Học [GTH] - Duration: 8:38.
For more infomation >> Severe weather expected in viewing area - Duration: 3:57.
For more infomation >> Joe Diaz' Sunday Forecast - Duration: 1:33.
For more infomation >> Sunday high school tournament results - Duration: 1:48. 


For more infomation >> Top Nhạc Điện Tử Gây Nghiện Lấy Cảm Hứng | Top Electronic Music Inspired by Alan Walker | EDM DJ - Duration: 1:14:06.
For more infomation >> Quyền Công Thiếu Lâm Tập 02 - Phim Kiếm Hiệp Cổ Trang Lồng Tiếng Thuyết Minh | Phim Xưa [PX] - Duration: 6:27:26.
For more infomation >> Female cat Komugi can not eat even if she wants to eat it - Duration: 2:05.
For more infomation >> Những Cảnh Hài Hước Của Người Câu Cá | The Scene Of The Fishing Fun | Thú Vui Dân Dã [TVDD] - Duration: 13:58. 
Không có nhận xét nào:
Đăng nhận xét