Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

16
  • 3
    You don't mention whether this raft of testing would be over and above the testing that should occur during development or in place of. Commented May 9, 2016 at 15:29
  • 3
    It would be benefitial but rather difficuilt to write unittest (tests-in isolotaion) if "we don't do TDD" because non tdd-code is usually hard to isolate. Writing Acceptance tests and/or integration test will also be difficuilt and/or fragile if you donot have an database abstraction layer (repository api) that allows you to define reproducable, non fragile pre-conditions. Commented May 9, 2016 at 15:42
  • 4
    @JoulinRouge: TDD helps with that. Since there is no code, you cannot tailor the test to your code. Commented May 9, 2016 at 16:11
  • 6
    This sounds like it would be a REALLY long code review. Commented May 9, 2016 at 18:17
  • 2
    I've worked at places where a peer review involved a fellow programmer looking over every line you've written, checking them against style guidelines and best practices, and writing the unit tests you didn't think to write. Commented May 10, 2016 at 5:14