>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
(Have been out travelling so trying to catch up so I might miss some
details. Nice to see some mail activity... keep it up!)
If the feature is in core, it should be tested when we build core.
Of course but then de package dependencies should be removed so that
it only depends on core functionality. (As I get it you have fixed
this for some cases right?)
[...]
There are four issues (that I know of) at present in the
test-harness
framework that are buildbot-relevant.
[1, 2, 3, 4 ...]
OK. So your saying that by applying KnownBug, SkipIf and rewriting
tests consistently we could come to a situation where we could start
letting buildbot signal a failure on error code from "make check"?
Sounds like a small project to do that.
Isn't there some way to tell XEmacs to ignore the package paths
completely so developers would see the same environment as buildbot
does when running "make check"? So that it will be obvious that you
have used a non core function in the unit test?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta