Hi Hieu, You may have noticed I checked in a file for testing detokenization. The usage is:
trunk/regression-testing/run-test-detokenizer.t --results-dir <RESULTS-DIRECTORY> [--detokenizer <DETOKENIZER-SCRIPT>] If the --detokenizer option is omitted, then it looks for the detokenizer script in the appropriate repository checkout path relative to itself. The individual tests are defined within the testing file itself, not in separate input/truth files in the repository, though it could be changed to be like that or extended to allow for both possibilities. It uses the Test::More framework, which means that the exit status is the number of test failures. At the moment, it runs eight tests, so the exit status should be between 0 and 8. Do you think it can be incorporated into the overall test suite in its current form? Ben On Tue, Jul 19, 2011 at 4:23 AM, Hieu Hoang <hieuho...@gmail.com> wrote: > At the moment, the regression test on test the various functionality of the > 2 decoders. Ideally, it should be testing all other aspects of the moses > toolkit too, so a regression test for detokenizer would be great. > > If you write a such a test, I'll make sure it's add with the current test > set. > > To answer your questions > 1. No, scripts/tests hasn't been used since the JHU workshop 2006! > 2. The regression test is run with the command > ./regression-testing/run-test-suite.pl > --decoder-phrase=moses-cmd/src/moses > --decoder-chart=moses-chart-cmd/src/moses_chart > This executes > run-single-test.perl > For each test in > regression-testing/tests > > I suggest you write a script that mimic the behaviour of > run-single-test.perl > > > > _______________________________________________ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
