Open GoogleCodeExporter opened 8 years ago
Okay. Started.
Original comment by aale...@gmail.com
on 12 Oct 2010 at 4:36
Okay. The next checkin is going to have all of the current (remarkably
ill-defined) bridgetest code moved into a new module, called legacytest. That
new module will begin life deprecated. Bridgetest will get some initial
checkins of the new-style stuff.
The new test base classes must provide equivalent coverage to the existing ones
(which is certainly going to be hard to judge). Basically: don't worry about
the typed stuff yet (we need to finish adding tests in API/core anyway), but do
have complete contract coverage for all the interfaces defined or referenced in
base and base/mutable.
Original comment by aale...@gmail.com
on 15 Dec 2010 at 6:58
Move the priority up. This seems to be doing a fine job of uncovering problems
and provoking improvements, so let's agree that it's higher priority. Also
give it a clear milestone.
Original comment by aale...@gmail.com
on 16 Dec 2010 at 9:15
Bridgetest is in adequate condition for conformance testing, although it
contains a bunch of TODO-s, and only for untyped and mutable APIs.
I'm marking this as blocked on 43, now, because we need the typed API to be
stabilized before we can add typed testing.
Original comment by aale...@gmail.com
on 31 Mar 2011 at 5:18
43 is resolved, and I've just now resolved 60, which simplifies the structure
of the tests needed somewhat (separating the functions of the typed context
from the schema cache). So we're moving ahead, now, on implementing testing
for the typed API.
Original comment by aale...@gmail.com
on 12 Oct 2011 at 6:48
Should also improve tests to cover
http://code.google.com/p/genxdm/issues/detail?id=66
Original comment by eric%tib...@gtempaccount.com
on 30 Jul 2012 at 8:53
Won't be completed in 1.0. Defer to 1.1
Original comment by aale...@gmail.com
on 24 Oct 2013 at 5:18
Original issue reported on code.google.com by
aale...@gmail.com
on 12 Oct 2010 at 4:36