Issue #2 resolved

Get testdbwriter into fpc trunk

repo owner created an issue

dbtestwriter is using obsolete test suites (evidenced by the autoinc change around Nov 5 which gives false test errors on MSSQL).

Looking at the code again, it seems quite possible to throw the testdb unit (the core test output code) into the fpcunit directory as envisaged earlier, despite MvC's comments that there is an implicit dependency on db units there.

Subsequently, dbtestwriter could be folded into db test classes.

However, will need to find out.

Comments (1)

  1. Log in to comment