Go gaga over Machine Learning

One of the good articles I read in a long time, that makes complete sense in today's agile environment:  Architecturally Aligned Testing Testing microservices should not be done in a separate test phase, by a dedicated test team, but instead collaboratively by cross-functional teams. There is a shift left in testing to ensure that teams stay autonomous and a shift right in testing towards exploration and experimentation.

The best time that I spend on my way to work reading blogs and sharing information, the byproduct a few must reads for almost anyone who wants an answer to where is technology going in the near future: IT goals for 2018: Five CIO must-dos For me, 2017 was a good year. We got a lot done. And the situation in the world -- everything moving at a faster... pace, constant change, new types of security threats, new technologies, new vendors, acquisitions, the on-going IT skills shortage and so on -- made it easier for me to make the case that we urgently needed to overhaul our organizational culture, processes and technologies. Top 10 blog posts of 2017 illuminate top CIO goals SearchCIO's most popular blog posts of 2017 point to a set of lofty -- and mandatory -- CIO goals: artificial intelligence,... digital transformation, multicloud management. IT leaders are learning all they can about these tech trends. The aim? To help their companies gain business advantage -- b...

It's been three months now that I have started my journey in a new working environment to implement a flavor of the Test Impact Analysis. Being a fan of ThoughtWorks and following Martin Fowler's blog  I was impressed about reading an article that spoke about the rise of TIA(Test Impact Analysis) The definition of TIA from martin fowler " Test Impact Analysis (TIA) is a modern way of speeding up the test automation phase of a build. It works by analyzing the call-graph of the source code to work out which tests should be run after a change to production code. Microsoft has done some extensive work on this approach, but it's also possible for development teams to implement something useful quite cheaply. " Problems to solve: Let's run all tests every time a change is pushed Tests that run late in the integration cycle - Implicitly Shifting right  Number of tests that run in the pipeline  The number of tests in the regression suite What shape is...