Abstract Labeling a module defective or non-defective is an expensive task. Hence, there are often limits on how much-labeled data is available for training. Semi-supervised classifiers, use far fewer labels for training models but there are numerous semi-supervised methods including self-labeling, co-training, maximal-margin, graph based methods, to name a few. Only a handful of these methods has been tested in SE for (e.g.) predicting defects– and even that, those tests have been on just a handful of projects.

This paper takes a wide range of 55 semi-supervised learners and applies these to over 714 projects. We find that semi-supervised “co-training methods” work significantly better than other approaches. However, co-training need to be used with caution since the specific choice of co-training methods need to be carefully selected based on a user’s specific goals. Also, we warn that a commonly-used co-training method (“multi-view”– where different learners get different sets of columns) does not improve predictions (while adding too much to the run time costs 11 hours vs 1.8 hours).

Those cautions stated, we find using these “co-trainers”, we can label just 2.5% of data, then make predictions that are competitive to those using 100% of the data. It is an open question worthy of future work to test if these reductions can be seen in other areas of software analytics.

All the codes used and datasets analysed during the current study are available in the https://GitHub.com/Suvodeep90/Semi_Supervised_Methods.