{"id":12099,"date":"2014-04-24T13:54:54","date_gmt":"2014-04-24T10:54:54","guid":{"rendered":"https:\/\/mozaicworks.com\/?p=6956"},"modified":"2023-09-15T15:04:56","modified_gmt":"2023-09-15T12:04:56","slug":"a-developer-in-test","status":"publish","type":"post","link":"https:\/\/mozaicworks.com\/blog\/a-developer-in-test","title":{"rendered":"A Developer in Test"},"content":{"rendered":"

\"AimeeRiversITAKEUnconf2014\"<\/a><\/p>\n

Modern applications are interconnected, depending on public services from one or more external applications. At the same time, applications change often. Their public services are very likely to change also. When this happens, our application has to continue working correctly<\/strong>.<\/p>\n

How can we know it does? The answer is by having automated tests for all external services used. How does such a test look? How is it written? What technologies\/skills do we need? Who is going to implement it? These are tough questions, but Aimee Rivers<\/a> has shown us that the answers are easier than they seem in her talk from I T.A.K.E. Unconference 2013<\/a>.<\/p>\n

Who’s going to build the test?<\/strong><\/h2>\n

The usual problem when trying to answer this question is that developers don’t like to write tests and testers might not have the necessary technical skills. Still, someone has to be the lucky person to do it and according to Aimee, the DIT (Developer in Test) will be the one.<\/p>\n

Now you may wonder what is a DIT? Is it another role in the development team? It turns out that it is not a new role. Before watching Aimee’s video, I have used the name “agile programmer” instead because the DIT is a programmer who likes to:<\/p>\n