{"id":832,"date":"2014-05-07T22:34:15","date_gmt":"2014-05-07T19:34:15","guid":{"rendered":"http:\/\/blog.adrianbolboaca.ro\/?p=832"},"modified":"2020-01-15T22:02:25","modified_gmt":"2020-01-15T20:02:25","slug":"golden-master-code-cast","status":"publish","type":"post","link":"https:\/\/blog.adrianbolboaca.ro\/2014\/05\/golden-master-code-cast\/","title":{"rendered":"Legacy Coderetreat: Episode 2 – Golden Master Codecast"},"content":{"rendered":"

Golden Master Codecast<\/h1>\n

Blog post series<\/h3>\n

This blog post is part of a series about legacy coderetreat and legacy code techniques you can apply during your work. Please click to see more sessions<\/a> about legacy code.<\/p>\n

Code Cast<\/h3>\n

The Golden Master technique is very useful when a clear input and output is easy to obtain on the system level. There are some cases where the Golden Master technique can be applied with difficulty or where it cannot be applied at all. We will discuss these situations further as well.<\/p>\n

For all the given situations we need to think if the system tests generated with the Golden Master are enough, or we need to start adding other types of tests like unit tests, component tests, integration tests, security tests, etc<\/p>\n

After this session we will have a basic safety net composed of system tests. These system tests will check the SUT against the golden masters. A very important output of the system would be the golden masters persisted in any form. All the system tests would need always to be called during the next refactoring phases.<\/p>\n

This is a codecast in Java where I start generating system test with the Golden Master technique. Please read more details about this technique in the Part 3 \u2013 Golden Master blog post<\/a>. Have fun!<\/p>\n

 <\/p>\n