User:Popcorndude/GSoC2021Proposal - Revision history

Popcorndude: /* UNIt-Testing Framework */

2021-04-17T13:35:24Z

UNIt-Testing Framework

Popcorndude: update timeline

2021-03-02T23:32:49Z

update timeline

Popcorndude: /* UNIt-Testing Framework */ link gathering

2021-03-02T15:56:51Z

UNIt-Testing Framework: link gathering

Popcorndude: /* Coding Challenge */

2021-03-02T15:55:19Z

Coding Challenge

Popcorndude: /* Coding Challenge */

2021-02-23T23:24:43Z

Coding Challenge

Popcorndude: /* Work Plan */ typo

2021-02-23T16:11:36Z

Work Plan: typo

Popcorndude: /* Coding Challenge */

2021-02-23T16:08:02Z

Coding Challenge

Popcorndude: /* UNIcode Support */

2021-02-11T17:13:20Z

UNIcode Support

Popcorndude: /* Coding Challenge */

2021-02-09T21:15:35Z

Coding Challenge

Popcorndude: /* UNIversal Dependencies-Based Structural Transfer */ links

2021-02-09T21:12:38Z

UNIversal Dependencies-Based Structural Transfer: links

@@ Line 31: / Line 31: @@
 I would also plan to enable this testing on all existing repositories unless the maintainers really didn't want it. This will entail converting any existing tests from whatever state they are currently in.
-See also https://github.com/apertium/apertium-init/issues/51 [[User:Ilnar.salimzyan/On_testing]] https://github.com/TinoDidriksen/regtest/wiki [[Testvoc]] https://github.com/apertium/apertium-ckb-eng/tree/master/t https://github.com/giellalt/regtest-kal
+See also https://github.com/apertium/apertium-init/issues/51 [[User:Ilnar.salimzyan/On_testing]] https://github.com/TinoDidriksen/regtest/wiki [[Testvoc]] https://github.com/apertium/apertium-ckb-eng/tree/master/t https://github.com/giellalt/regtest-kal [[Github_Actions]]
 === UNIversal Dependencies-Based Structural Transfer ===

@@ Line 27: / Line 27: @@
 === UNIt-Testing Framework ===
-Our regression tests are few and far between and almost none of them are run automatically. This part of the project would be the creation of a Grand Unified Unit-Testing Framework™, probably mainly derived from https://github.com/TinoDidriksen/regtest (though I have included time in the schedule for bikeshedding the exact feature set).
+Our regression tests are few and far between and almost none of them are run automatically. This part of the project would be the creation of a Grand Unified Unit-Testing Framework™, probably mainly derived from https://github.com/TinoDidriksen/regtest (<s>though I have included time in the schedule for bikeshedding the exact feature set</s> bikeshedding has been rescheduled to before the coding period begins).
 I would also plan to enable this testing on all existing repositories unless the maintainers really didn't want it. This will entail converting any existing tests from whatever state they are currently in.
@@ Line 68: / Line 68: @@
 Mar 2: Unit-testing draft is probably nearly ready to send to the mailing list for discussion.
+Mar 2 again: This slight generalization of Tino's regression system should cover pretty much everything we need [[User:Popcorndude/Regression-Testing]] without separate unit tests.
 == Work Plan ==
@@ Line 87: / Line 89: @@
 * Figure out how ICU custom normalizers work
 * Determine which ICU types to make default
+* Propose Grand Unified Unit-Testing Framework™
+* Bikeshed Grand Unified Unit-Testing Framework™
 | Draft of string-handling guidelines (= updated version of [[Code style]])
 |-
@@ Line 116: / Line 120: @@
 * Deal with anything that comes up in testing
 * Finalize string-handling coding guidelines
+* Implement/port regression test system
-* Start documenting existing unit testing frameworks
 | Unicode transition branches ready for merging
 |-
 | Week 5
 July 4-10
-| Propose Grand Unified Unit-Testing Framework™
+| Prepare Grand Unified Unit-Testing Framework™
 |
+* Test regression system
-* Present proposed framework on the mailing list
+* Figure out continuous integration setup
-* Begin bikeshedding
-* Begin prototyping UD compiler for apertium-recursive
+* Incorporate regression tests into apertium-init
+* Use apertium-init to begin updating existing repos
-| Nothing terribly concrete
+| Working test framework
 |-
 | '''midterm evaluation'''
@@ Line 135: / Line 140: @@
 | Week 6
 July 11-17
+| Roll out Grand Unified Unit-Testing Framework™
-| Finish initial UD compiler
 |
+* Use apertium-init to update existing repos
-* Get parser working
+| Partial rollout of testing framework
-* Converter to CONLL-U
-* Figure out how to describe and implement transfer
-* More bikeshedding
-| Preliminary UD-based transfer system
 |-
 | Week 7
 July 18-24
-| Implement Grand Unified Unit-Testing Framework™
+| Probably more Grand Unified Unit-Testing Framework™ rollout
 |
+* Use apertium-init to update existing repos
-* Incorporate mailing list bikeshedding
+* Probably declare undying hatred of makefiles
-* Finish implementing/porting/whatevering the system
+| Working regression tests in all repositories
-* Begin applying to repos
-| Working unit-testing framework
 |-
 | Week 8
 July 25-31
+| UD experimentation
-| Framework rollout
 |
+* Convert parser output to CONLL-U
-* Enable unit-testing in all languages and pairs
+* Transfer of some sort
-* Convert existing tests to new format
+* Deal with the inevitable issues that arise from rolling out changes to several hundred repositories
-| Test reports everywhere
+| Yet Another Transfer System
 |-
 | Week 9
@@ Line 167: / Line 169: @@
 ** See how well it translates with no pair-specific rules, just the reorderings specified by the monolingual grammar
 ** See how fast or slow it ends up being
+* Port compiler and whatnot to C++ if it turns out to be any good
-* Deal with the inevitable issues that arise from rolling out changes to several hundred repositories
 | Preliminary evaluation of the effectiveness of UD transfer
 |-

@@ Line 31: / Line 31: @@
 I would also plan to enable this testing on all existing repositories unless the maintainers really didn't want it. This will entail converting any existing tests from whatever state they are currently in.
-See also https://github.com/apertium/apertium-init/issues/51 [[User:Ilnar.salimzyan/On_testing]]
+See also https://github.com/apertium/apertium-init/issues/51 [[User:Ilnar.salimzyan/On_testing]] https://github.com/TinoDidriksen/regtest/wiki [[Testvoc]] https://github.com/apertium/apertium-ckb-eng/tree/master/t https://github.com/giellalt/regtest-kal
 === UNIversal Dependencies-Based Structural Transfer ===

@@ Line 66: / Line 66: @@
 Feb 23: the coding challenge listed at [[Ideas_for_Google_Summer_of_Code/Robust_tokenisation]] can be found [https://github.com/mr-martian/gsoc2021-coding-challenge here] and a draft of the file structure for the unit-testing framework can be found at [[User:Popcorndude/Unit-Testing]].
+Mar 2: Unit-testing draft is probably nearly ready to send to the mailing list for discussion.
 == Work Plan ==

@@ Line 65: / Line 65: @@
 Status as of Feb 9: working Python compiler from minimal formalism to trx.
-Feb 23: the coding challenge listed at [[Ideas_for_Google_Summer_of_Code/Robust_tokenisation]] can be found [https://github.com/mr-martian/gsoc2021-coding-challenge here].
+Feb 23: the coding challenge listed at [[Ideas_for_Google_Summer_of_Code/Robust_tokenisation]] can be found [https://github.com/mr-martian/gsoc2021-coding-challenge here] and a draft of the file structure for the unit-testing framework can be found at [[User:Popcorndude/Unit-Testing]].
 == Work Plan ==

@@ Line 171: / Line 171: @@
 August 8-14
 | Unknown
-| What I write here will have little bear on what actually happens and also by not making a plan for this week, I ensure that my overall plan can be at most 90% wrong.
+| What I write here will have little bearing on what actually happens and also by not making a plan for this week, I ensure that my overall plan can be at most 90% wrong.
 | Unknown
 |-

@@ Line 19: / Line 19: @@
 === UNIcode Support ===
-This portion of the project is [[Ideas for Google Summer of Code/Robust tokenisation]]. All string processing would be transferred to ICU and all inputs would be normalized.
+This portion of the project is [[Ideas for Google Summer of Code/Robust tokenisation]]. All string processing would be transferred to ICU and all inputs would be normalized. A program would be inserted at the beginning of the pipeline which normalizes incoming text and compilers would emit warnings for non-normalized input.
 The normalization will likely be a modified version of NFC. See https://github.com/apertium/organisation/issues/24 for discussion.

@@ Line 40: / Line 40: @@
 There's probably also cool stuff we could do with treebanks.
+See also [https://github.com/flammie/leg-ape-ud] [https://www.aclweb.org/anthology/2020.acl-main.134.pdf] [https://github.com/taruen/apertium-kaz/blob/master/dev/parse.cg3] [https://github.com/flammie/fud] [http://taruen.com/apertium-kaz/#(part._.A_.Constraint_.Grammar-based_.Universal_.Dependencies_parser_for_.Kazakh__experimental_)]
 == Background ==