Code Test implementation
BibCite really needs some sort of automatic code testing, e.g. using JUnit testing to avoid regressions and make certain that features are working after code changes.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
For GUI testing, the following libraries may be interesting:
http://
For database access normal JUnit tests should be sufficient, the same for encryption tests.
However, both uispec4j and jUnit are licensed under the CPl, which is incompatible with the GPL - I first thought, this may provide a problem, but actually, as long as BibCite binary compiled distributions do not contain any classes referencing jUnit or uispec4j, we should be fine.
Since compiled binaries do not need any testing mechanisms, since testing is done with source at coding stage, it should be fine, to just have separate test-classes and just not to distribute them.
That is at least my understanding of
http://
http://
And even here for how to distribute Netbeans with JUnit - which seems to conclude, that for us non-redistributing jUnit is entirely acceptable:
http://
The same should be true for uispec4j, since it is governed by the same license.
Regarding normal jUnit - I know found the problem with Netbeans 7 not showing the 'Tools' - 'Create jUnit Test' menu entry on right-clicking a java class - you need to create a folder 'test' in the root bibcite directory manually first - will be in in the next revision.
