7 votes
Accepted

How to measure progress when automating a legacy project?

For a legacy system, particularly when there isn't any lower level automation to leverage, I find it helps to start with some analysis to determine first the major functional areas of the application ...
Kate Paulk's user avatar
  • 31.5k
6 votes

How to Reduce the Technical Debt of 1000 manual test cases?

There are a number of considerations. You should avoid thinking of 'x number of test cases' means 'x number of automated cases'. As attractive as automation is, it is very limited in what it can do ...
Michael Durrant's user avatar
4 votes

How to measure progress when automating a legacy project?

One approach is to spend some time creating a master list of all the application functionality. The simplest approach to that may be to base the list on UI functionality. A more complicated approach ...
Michael Durrant's user avatar
3 votes

How to measure progress when automating a legacy project?

TL;DR: Code coverage retrofit "automation" to a legacy project What does legacy mean? To me, legacy code is simply code without tests. The Legacy Code Dilemma: When we change code, we ...
Niels van Reijmersdal's user avatar
3 votes
Accepted

Are Characterization (Golden Master/Snapshot) tests supposed to be human readable?

Generally, characterisation tests are not an end state. They're a way to pin the current behaviour of untested legacy code, so that you can start making changes towards maintainability and testability ...
jonrsharpe's user avatar
2 votes

How to Reduce the Technical Debt of 1000 manual test cases?

Here's how I'd approach this: Analyze and rank the test cases by risk - First, I'd go through and analyze the manual test cases, looking to rank them in a way that helps decide on the automation ...
Kate Paulk's user avatar
  • 31.5k
1 vote
Accepted

What's the 'workflow' for writing tests for existing code with zero tests?

Technical Debt You have a described a situation where there is a lot of technical debt from having no tests. My approach would be: Change things for all code (new or updated) going forward to have ...
Michael Durrant's user avatar
1 vote

Are there some well known pitfalls to avoid when starting with unit testing on a "legacy" web application?

Kate already gave quite a good answer. From my experience I'd like to add avoid heavy test/mock frameworks There are some mighty frameworks out there that let you virtually break any restrictions ...
user1130's user avatar
1 vote

1.5 Million lines of code. 0 tests. Where should we start?

Make it clear: Unit testing is no longer an optional task. Period All code changes now get tests, new or updated as appropriate. The first ones will be REALLY hard as there are so many hurdles at ...
Michael Durrant's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible