You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org> on 2009/11/22 10:20:48 UTC
[jira] Resolved: (EMPIREDB-32) Create unit tests
[ https://issues.apache.org/jira/browse/EMPIREDB-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere resolved EMPIREDB-32.
-------------------------------------------
Resolution: Later
Assignee: Francis De Brabandere
This is more a state of mind than something that should be in the issue tracker. So I'm closing this issue... just try to write tests when you write new code
> Create unit tests
> -----------------
>
> Key: EMPIREDB-32
> URL: https://issues.apache.org/jira/browse/EMPIREDB-32
> Project: Empire-DB
> Issue Type: Task
> Components: Core
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
>
> This projects needs unit testing and continuous integration. Without this the chances for regressions are way to high!
> I suggest we do this after migrating to maven as maven is great for running the tests and generating reports
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.