Mentor: Pablo Estrada
Contributor: Aisulu Karimbaeva
Apache Beam maintains a static capability matrix to track which Beam features are supported by which set of language SDKs + Runners. The Runners/Beam Capability Matrix Page needed to be updated. The goal: Tighter coupling of the matrix portion of the comparison with tags on ValidatesRunner tests
Action: Create a completely new Capability Matrix that is based on the ValidatesRunner tests that run on the various Apache Beam runners. Improve UI/UX of Matrix Table. Use the test in ./test-infra/validates-runner/ to generate a JSON file that contains the capabilities supported by various runners and tested by each individual test.
Design:
How do we reformat test results into the file we need?
- “flink”/”spark”/”dataflow” are the COLUMNS
- The Categories are the ROWs
- If a test has no categories, then
- Each element is a unit test. Each test has a category or more.
- Status: “PASSED” / “FAILED” / “NOT RUN”
- Get familiar with the code and tools especially Docker, and Hugo framework
- Get familiar with the manually generated capability matrix and ValidatesRunner test results
- Get ValidatesRunner tests results and save as local file, reformat test results to the needed format and create with that data a new Capability Matrix table - Single and Big tables: commited code1 , commited code2
- Instead of locally imported reformatted test results use uploaded data from Gcload, add links to test names in the new Capability Matrix (based on runner testing) Big table. committed code
- Added a command line utility: for generating reformatted data from test results, and uploading to GCloud. committed code
- Reported a bug related to Validate-Runner test results
All my GSoC commited code are in #22930 pull request(in review)
Contact:
Email: alive.k001@gmail.com
Linkedin