Regression testing for keyboards was such a good idea. I can't begin to list
the number of times I've tweaked the KeyMagic source, then re-run the tests to
see if this tiny change affected Ayar/Myanmar3, etc.
That said, we need to be able to tests other types of input and conversions.
For example, if I want to test Ayar input and Zawgyi output, I have to COPY the
Ayar test suite and change the encoding.
There's two main types of tests we'll need.
1) Encoding tests. (We'll need KeyMagic arrays for this). Something like:
"မြန်" => ["ျမန္" + "ြမန်" + "jref"]
...with the order (Uni->[Zawgyi,Ayar,WinInnwa) defined in the header somewhere.
2) Roman Input method tests. We should eventually convert the entire "Compatibility checklist" to a test file. This can also be done with arrays:
"kote" => ["ကုက်" + "ကုဋ်" + "ကုတ်" + "ကုပ်" + "ကုဗ်"]
...however, we'll need more, like the ability to represent "space" and arrow keys. We can use arrays on the left for this, I think:
["ko" + "1" + "ko"] => ["ကိုယ်" + "ကို"] #Main window test
["ko" + "1" + "ko" + "2"] => "ကိုကို" #Sentence window test
This will REALLY help when adding a new converter, input method, etc. It can
probably all be specified in the header params.
Original issue reported on code.google.com by seth.h...@gmail.com on 27 Nov 2010 at 4:43
Original issue reported on code.google.com by
seth.h...@gmail.comon 27 Nov 2010 at 4:43