Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
codegen/ | 22-Nov-2023 | - | 149 | 40 | ||
codegen-expected/ | 22-Nov-2023 | - | 34 | 21 | ||
IGNORE_CHECKSTYLE | D | 22-Nov-2023 | 0 | |||
README.txt | D | 22-Nov-2023 | 1 KiB | 16 | 14 |
README.txt
1The webkit-codegen module represents a code generation tool, so the tests in 2this module ensures the code generated by the tool is correct. We do this by 3using two types of test-resource files: input and output files. The input files 4live under codegen/ while the output files live under codegen-expected/. 5Each test consists of parsing the input file, then passing that file to the tool 6to perform some code transformation/generation, and finally validating the 7output against one or several output file. 8The input and output files are named in such a way that they correspond to how 9the tool names its generated files, e.g. running boundary interface generation 10for Foo.java will generate a file named FooBoundaryInterface.java. 11 12The folder deps/android/webkit/ contains classes that should be seen as 13android.webkit classes. These classes are special because they need special 14treatment by the code generation tool (since the support library will never 15reference those classes directly, but instead create its own versions of them). 16