DuffPane now has the start of a unit test suite. Invoke it via 'ant
clean check'. Right now there are tests to ensure that typing certain sequences of keys in the Extended Wylie keyboard gives the expected Extended Wylie back when "Tools/Convert Tibetan to Wylie" is invoked. The syntactically illegal d.wa now converts to Tibetan and then back to d.wa (not dwa, as it did); likewise with the illegal g.wa. wa doesn't take any prefixes, but I prefer clean end-to-end behavior. (jeskd doesn't go end-to-end, though.) Note that you cannot successfully run the DuffPane tests on a Linux box unless your DISPLAY variable is set correctly. Thus, my nightly builds will fail with an Error (as opposed to a Failure).
This commit is contained in:
parent
d9b22a43d6
commit
efa8fc1f25
8 changed files with 444 additions and 109 deletions
|
@ -34,13 +34,14 @@
|
|||
<!-- This creates output files TEST* in the Jskad/ directory. -->
|
||||
<target name="run-all-junit-tests"
|
||||
description="Assuming that compilation of appropriate classes has been done, this target runs all the JUnit tests in the project.">
|
||||
<junit fork="no" printsummary="yes" haltonfailure="yes" haltonerror="yes">
|
||||
<junit fork="no" printsummary="yes" haltonfailure="yes" haltonerror="no">
|
||||
<classpath>
|
||||
<pathelement location="${junitbin}"/>
|
||||
<path refid="entire.class.path"/>
|
||||
</classpath>
|
||||
<formatter type="xml"/><!-- If not XML, then 'ant -buildfile
|
||||
build.xml check-report' will fail. -->
|
||||
<test name="org.thdl.tib.input.DuffPaneTest"/>
|
||||
<test name="org.thdl.util.ThdlLazyExceptionTest"/>
|
||||
<test name="org.thdl.util.TrieTest"/>
|
||||
<test name="org.thdl.tib.text.tshegbar.UnicodeUtilsTest"/>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue