API migration refers to the change of a used API to a different API in a program. A special case is called wrapper-based API migration. The API change is done without touching the program but the old API is reimplemented by means of the from now on used one. This so called wrapper has the interface of the reimplemented API but uses the implementation of the new one. This is an interesting approach because the wrapper can be used in each program, which uses the old API. To make this approach reproducible we study a ranking-based method for implementing a wrapper, where we always implement the method with the highest priority depending on failing test cases. Thus, we can reconstruct each implementation step. We first develop an infrastructure to run and log test suites of Java projects that use an API, which we want to change. We then build a wrapper for a given API using the ranking-based approach.