[sword-devel] Testing SWORD 1.7.0RC#
greg.hellings at gmail.com
Tue Aug 6 08:45:48 MST 2013
On Tue, Aug 6, 2013 at 10:41 AM, David Haslam <dfhmch at googlemail.com> wrote:
> The current focus is all on whether the engine can be recompiled in
> platforms, each with its own idiosyncrasies. That's natural at this stage.
> Most of the developers are responding in like manner.
> I''m rather more concerned with module development, and how this fares
> the software release.
> Unless the testing phase of the release candidate includes checking whether
> a module built with the SWORD utility (e.g. osis2mod) from the same
> build, and is then tested as a module in a front-end that has been
> recompiled with the release candidate of the SWORD engine, how can anyone
> confident that the software is ready to be released?
As a module creator, you are welcome to test that. Troy has been slowly
growing a testsuite of issues when regressions appear and corner cases crop
up that he can run automatically. That doesn't help for any particular
front-end, but if the engine is still producing what we all have agreed is
correct, then any regressions as such would be issues that the frontend
needs to update.
> And how many features does such a module need to have to create such
> Does anyone disagree with this as being a sensible requirement?
> Best regards,
> View this message in context:
> Sent from the SWORD Dev mailing list archive at Nabble.com.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel