Machine Learning Testing
It is strangle how bubbles go up. Early adopters obtain extraordinary results, and soon people are talking about the “chasm” being crossed, and new adopters already are being called latecomers.
One of the recent bubbles in the software industry is machine learning. It shows clearly the stage of the software industry that the job market is full of positions for developers with experience in implementing machine learning in the most farfetched scenarios. Yet, you see almost no positions for testers requiring equivalent experience. How come?
Who will be asking questions regarding the repeatability of the results? It comes as an enormous surprise to some CIOs when they uncover that several of the methods currently used in what is named “machine learning” are statistical methods, which won’t produce the same result twice, even if provided the same input. It comes as an even larger surprise that testing the implementation with the same data used for its “training” is absolutely useless, and that they need an equivalently large input dataset for testing purposes. And it surprises several developers that machine learning libraries, even if implementing a method with reliable confidence, still demand a lot of transformation of the raw input into the features used in the training process, and then a lot of filtering of the output before it is really usable.
Machine learning testing ought to be seen soon as a much desired skill. Before we start to believe that the machines will test themselves.
