As informa??es desta p¨¢gina n?o est?o completamente dispon¨ªveis no seu idioma de escolha. Esperamos disponibiliza-las integralmente em outros idiomas em breve. Para ter acesso ¨¤s informa??es no idioma de sua prefer¨ºncia, fa?a o download do PDF ²¹±ç³Ü¨ª.
Publicado : Nov 30, 2017
N?O ENTROU NA EDI??O ATUAL
Este blip n?o est¨¢ na edi??o atual do Radar. Se esteve em uma das ¨²ltimas edi??es, ¨¦ prov¨¢vel que ainda seja relevante. Se o blip for mais antigo, pode n?o ser mais relevante e nossa avalia??o pode ser diferente hoje. Infelizmente, n?o conseguimos revisar continuamente todos os blips de edi??es anteriores do Radar.
Saiba mais
Nov 2017
Experimente
Many development teams have adopted test-driven development practices for writing application code because of their benefits. Others have turned to containers to package and deploy their software, and it's accepted practice to use automated scripts to build the containers. What we¡¯ve seen few teams do so far is combine the two trends and drive the writing of the container scripts using tests. With frameworks such as and , you can express the intended functionality for either isolated or orchestrated containers, with short feedback loops. This means that it¡¯s possible to use the same principles we¡¯ve championed for code by TDD'ing containers. Our initial experience doing so has been very positive.
