Should I include DUnit elements in my Delphi 7 project?

Question

I have an old project written for Delphi 7. I am going to integrate a bunch of new code into it, which includes a test suite using DUnit. DUnit is not part of Delphi 7 (it was integrated later), so the question arises: should I include DUnit elements in my project (check them for version control, etc.), Or do I need all participating developers to support their individual Install DUnit?

The project is closed by source code and written and deployed only within the enterprise that I am working on, i.e. project source code will not be delivered to any of the users.

Answer 1

As you formulated your question, there may be some confusion about what you ask. Therefore, let us first step back from this.

It looks like you are asking whether to include DUnit units in a production application . That would be a very bad idea, and I will avoid the details of why in this answer.

However, I realized that your question is whether you should treat this third-party source as your own source code for the project (from the point of view of source control). And I answered as such.

---

There are a number of principles that justify including a DUnit source in an SC repository.

• , dev-, , .
  • . , : (1) . (2) .
  • ( ), 100% .
• , DUnit.
  • , , .
• , DUnit, , ( ), . .
  • DUnit , . , .

: Delphi DUnit, Source Control. DUnit Delphi - , .