StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhat would you do when you are about to add some new features to a large (and dirty) codebase which has virtually *NO* unit-testing code?
primarykey
Id
178997
data
AcceptedAnswerId
0
AnswerCount
14
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-10-07T15:21:32.100
FavoriteCount
3
LastActivityDate
2008-11-01T03:25:51.340
LastEditDate
2008-10-07T20:55:27.510
LastEditorUserId
10661
OwnerUserId
18638
ParentId
0
PostTypeId
1
Score
9
ViewCount
705
LastEditorDisplayName
S.Lott
text
Body
<a href="http://rads.stackoverflow.com/amzn/click/0201485672" rel="noreferrer">Martin Fowler</a> says that we should do refactoring before adding new features (given that the original program is not well-structured). So we all want to refactor this dirty codebase, that's for sure. We also know that without unit-testing code it's very easy to introduce subtle bugs. But it's a large codebase. Adding a complete suite of tests to it seems impracticable. What would you do in this case?
Tags
<unit-testing><testing><refactoring>
Title
What would you do when you are about to add some new features to a large (and dirty) codebase which has virtually *NO* unit-testing code?
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USS.Lott
UserOwnerUserId
1. USOwen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POWhat would you do when you are about to add some new features to a large (and dirty) codebase which has virtually *NO* unit-testing code?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POWhat would you do when you are about to add some new features to a large (and dirty) codebase which has virtually *NO* unit-testing code?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POWhat would you do when you are about to add some new features to a large (and dirty) codebase which has virtually *NO* unit-testing code?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.