Adding unit tests to legacy code [closed]

by

The best way, I have found, is to incrementally add the unit tests, not to just jump in and say we will now unit test the application.

So, if you are going to touch the code, for bug fixes or refactoring, then first write the unit tests. For bugs unit tests will help prove where the problem is, as you can duplicate it.

If refactoring, you will want to write unit tests, but you may find that the test is impossible to write, so you may need to find a high level, that calls the function that will be refactored, and unit test that part. Then, as you refactor the offensive function, write your tests so you can ensure that it is operating as it should.

There is no easy way to do this.

This question may help with more suggestions.
How do you introduce unit testing into a large, legacy (C/C++) codebase?

More Related Contents:

  1. What is Mocking?
  2. What Makes a Good Unit Test? [closed]
  3. What’s the difference between unit tests and integration tests? [duplicate]
  4. Should one test internal implementation, or only test public behaviour?
  5. What is unit testing and how do you do it? [duplicate]
  6. What is unit testing? [closed]
  7. Mock functions in Go
  8. Should Private/Protected methods be under unit test? [closed]
  9. Visual Studio 2015 or 2017 does not discover unit tests
  10. Unit Tests not discovered in Visual Studio 2017
  11. Fill os.Stdin for function that reads from it
  12. Unit testing Anti-patterns catalogue
  13. How to test my servlet using JUnit
  14. Configuring IntelliJ IDEA for unit testing with JUnit
  15. Do MSTest deployment items only work when present in the project test settings file?
  16. Updating input html field from within an Angular 2 test
  17. Junit5 mock a static method
  18. How to avoid multiple asserts in a JUnit test?
  19. Unit testing with singletons
  20. How do you mock a Sealed class?
  21. Is it bad practice to have more than one assertion in a unit test? [closed]
  22. Example invalid utf8 string?
  23. Mock framework vs MS Fakes frameworks
  24. Should it be “Arrange-Assert-Act-Assert”?
  25. Dependency Injection: Turtles all the way down?
  26. Unit testing code with a file system dependency
  27. What is a “Stub”?
  28. F# development and unit testing? [closed]
  29. Testing route configuration in ASP.NET WebApi
  30. how do I mock sqlconnection or should I refactor the code?

Leave a Comment