Why Johnny STILL Can't Unit Test His Legacy Code - And What You Can Do About It

•

1 gostou•343 visualizações

Here, we look at the organizational and managerial issues surrounding refactoring legacy code. Topics that will be discussed include: 1) The definition of legacy code. It’s not just old card reader driver code that hasn’t been updated in a while. 2) The definition of unit testing. Running it has to be quick as an eye blink and repeatable. That’s going to obviate dependencies on our class under test. Especially ones that require databases, user interfaces and so on. 3) What’s the real goal of this, anyway? Looking into the TCO issues and the support of an Agile and Lean Startup mentality to aid the business attain its goals. 4) The need to write appropriate integration tests before we journeying into refactoring. How we, as managers, have to support that undertaking first. 5) Is unit testing merely “a tax” on otherwise available developer cycles to get features done? 6) Why, as managers, we sometimes think that integration tests are enough. 7) Why the metric of code coverage isn’t enough, although we might think that’s the goal. This will be a discussion that gets into the notion of why code coverage is merely a management report that serves as a starting point. 8) When are we done with writing unit tests? If 100% coverage isn’t the goal, what is? 9) The role of more advanced tools, such as Java PIT mutant testing and Microsoft Pex, in finding test suites that truly test quality. How to break the news to your developers, as well! 10) Examples of code that make a developer’s job a nightmare when they are trying to insert true unit tests. 11) How we, as managers, must change from a culture that might tell our people what to do and become one that leads and enables them.

Software

Why Johnny STILL Can't Unit Test His Legacy Code - And What You Can Do About It

Mais conteúdo relacionado

Mais de Howard Deiner

Digital circuits, including the ones that we use for modern day computers, rely on digital electronics. That just means that they work because of a particular voltage being present to mean a one and the lack of a voltage to mean a zero. Itâ€™s how we build circuits together to transform an input into an output, with all of the circuits and programs to run on those circuits (in a von Neumann computer) that makes computers useful. But when designing these circuits, one basic design question to answer is â€œshould I use a clock or not (synchronous vs asynchronous)?â€ While synchronous circuits are easier to design, asynchronous circuits have many advantages, such as high performance. Let me mapping this concept onto organization dysfunction. As a coach, I can tell within 5 minutes of meeting a client how well the organization will do when attempting to become more Agile through reductions in Lean Wastes by adopting some Software Craftsmanship and DevOps practices and principles. How can I tell? Easy. I look at their calendaring tools. When I see a personâ€™s email box full of calendar requests and a calendar that resembles a paved driveway, I know immediately that we will have a lot of problems. On the other hand, when the corporate culture embraces true one-on-one collaboration, with few meetings, I know that weâ€™re going to get on together just fine. As an organization if we want to make progress on work to be done, we have a choice to make. We can either be asynchronous by collaborating together and getting stuff done, or we can take the route that has be drummed into everyoneâ€™s head over the last 159 years: we can hold meetings. Unhappily, the more we rely on meetings as the primary way of making progress, the less we get done because of waiting and coordination wastes. This talk will discuss the underlying analogy more in depth, apply it to organizations we are familiar with, and discuss the proper role for meetings in an organization. It will then turn its attention to how DevOps in general and virtualization/containerization in particular allows us to be more asynchronous as an organization, and therefore much quicker and less wasteful.

Synchronous vs Asynchronous Digital Circuits as an Analogy to Organizational ...

Why Johnny STILL Can't Unit Test His Legacy Code - And What You Can Do About It

Recomendados

Recomendados

Mais conteúdo relacionado

Mais de Howard Deiner

Mais de Howard Deiner (19)

Último

Último (20)