Have you ever faced reading a unit test and had no idea what it tests, because the assertions where to complicated, even with domain knowledge? How about you would be able to actually see the discrepancy between the result and the expectation, without needing to decipher cryptic exceptions. Luckily this is easy for simple data types, but how about dealing with huge custom types? Is there a way of visualizing those differences? The answer will be presented in this talk: The idea is to leverage the power of utf-8 and transforming the complex datasets into human readable or even visually pleasing data sets, so you can immediately see, where the error is. By the example of a simple chess app, I will visualize some tests looking like this "█░█░█░█░n" + "░█░█░█░█n" + "█░█░█░█░n" + "░█░█░█░█n" + "█░█░♟░█░n" + "░█░█*█░█n" + "█░█░█░█░n" + "░█░█░█░█n", making the failure way more easier to spot and then also to correct. Join for learning more about unit tests easing, utf-8 characters, and how to leverage those learnings for your use cases.