Go gaga over Machine Learning

One last blog post before the year ends and we start a new beginning in the testing world, this article sums up where testing is headed to! Complexity, testing and its impact on innovation in 2018 Commercial industry has been fundamentally changed by digital technology. The most revolutionary organisations, like Uber and Netflix have shifted the goalposts, moving entire businesses online and introducing accessible, engaging and immersive consumer experiences. And, while tech innovation has historically happened at a discrete product or operational level, today it's taking place across an entire business - and beyond.

In continuation from my previous  series of posts  targeting testing in top few companies from the technology space. After  Software Testing @Facebook  and @Google  we shall now look at Microsoft: Testing@Microsoft Software Development Engineers in Test (SDETs) are usually just called Test and sometimes Software Testing. SDETs are responsible for maintaining high testing and qualityassurance standards for all Microsoft products. Software Development Engineers (SDEs) are often referred to as Software Development. SDEs write the code that drives Microsoft products and upgrades. Very few teams in Microsoft are still using SDETs to do significant amount of manual testing. Manual testing is mainly outsourced. Actually, as early as in 2004, for example, most of the manual testing of MSN Explorer was outsourced. Think about it this way: it just doesn't make sense for test manager to spend their headcount (SDETs) on something can be easily outsourced....

In continuation from my previous  series of posts targeting testing in top few companies from the technology space. After Software Testing @ Facebook  we shall now look at Google: Testing@Google Test exists within a Focus Area called Engineering Productivity . Eng Prod owns any number of horizontal and vertical engineering disciplines, Test is the biggest. A product team that produces internal and open source productivity tools that are consumed by all walks of engineers across the company. We build and maintain code analyzers, IDEs, test case management systems, automated testing tools, build systems, source control systems, code review schedulers, bug databases... The idea is to make the tools that make engineers more productive. Tools are a very large part of the strategic goal of prevention over detection. A services team that provides expertise to Google product teams on a wide array of topics including tools, documentation, testing, release management...

This topic has always been of interest by testers who like to understand how some of the best companies perform testing in their organization. Based on my research and what's on internet here are some very interesting snippets. I will try to keep this updated as and when I hear more but at the same time will have a series of posts  targeting the top few companies in the technology space. We shall start with Facebook here: Testing@Facebook Places huge emphasis on individual engineers making sure their changes are legit Strong shame culture around making irresponsible changes to the site, the apps, etc. (see  What are the roots of 'clowning' or 'clowny behavior' or 'clowntown' at Facebook?  and to a lesser but tone-setting extent  When people who work at Facebook say "clowntown" , what do they mean? )  I f you do something really bad (i.e. take the site down, kill the egress of the site in a significant way) you may get a photo of yourself...