GSOC2024-Automated Regression Tool - May, June

[piyush]

Monday, May 27 Report:

The plan for this week:

1. Invite mainainers to a forked repo to experiment on the prototype
2. Take feedback from the prototype 

What i need from mentors:

1. Insights on how to load the configs for the user to chose from to generate reports
2. How to proceed with the PR as it involves breaking changes: https://github.com/checkstyle/contribution/pull/867

[piyush]

Wednesday, May 30 Report:

Blockers:
1. The discussion on usage of project-to-test-on.properties is being done my maintainers and the impact it would have on backward compatibility

2. A refiend vision document, where there are agreements to arrive on the same page among maintainers on certain aspects like role of BDD, creating a new repo

[piyush]

Friday, May 31 Report:

Task done:
1. Raised a PR for using the script to parse config examples:
    Link: https://github.com/checkstyle/test-configs/pull/2
2. Raised a PR for creating folder structure in test-config
    Link: https://github.com/checkstyle/test-configs/pull/4

Blockers:
I tried to mimick using a github action and execute the groovy script but facing issues with parsing XML. I have had a feedback from maintainer to use all java. 

[piyush]

Saturday, 1st June Report:

Task done:
Raised following PRs and got it merged by the maintainer:
1. Make all Examples configs for SummaryJavadoc
2. Rename 'all-in-one' as 'all-examples-in-one' #13
3. Create all-examples-in-one config

4. Fix all configs to have proper checkstyle xml strucuture

5. Rename "default" to "Example1"

Task to be done:
1. Test all configs follwing the instruction mentioned int he issue
     test all configs that we created in main repo by 'Github, generate report'
2. Work on my script and workflow to understand the larger picture of the regression-tool

[piyush]

Monday, 3rd June Report:

Task done:
1. Testing of Regression testing for all examples by the PR: https://github.com/checkstyle/checkstyle/pull/14931
2. Raised and got merged PR: Merge japan-period into Example3

Discussion
1. Had discussion on mentor on what is next and the deliverables for the month of June

Task to be done
1. Will go on to build a gradle application as an extractor which will automatically generate the configs, which we have been doing manually

[piyush]

Tuesday, 4th June Report:

Task done:
1. Raised and got merged PR: Merge japan-period into Example3

Task to be done
1. Creating series of PRs based on the updated requirements in Create a application what parses xdocs with example config specified

[piyush]

Wednesday, 5th June Report:

Task done:
1. Raised and got merged PR: Part 1: Create a application what parses xdocs with example config specified
2. Completed testing as mentioend in test all configs that we created in main repo by 'Github, generate report'

What I expect from maintainers:
1. Review: Part 2: Create a application what parses xdocs with example config specified


Task to be done
1. Read updated vision document for the automated regression tool and asking questions to maintainers if any on the same

[piyush]

piyush

02:09 (now) 

to checkstyle-devel

Monday, 10th June Report:

Task done:
1. Raised PR: Part 3: Create ConfigSerializer and replace properties and module into config-template.xml
2. Addressed Review comments of PR: Part 3: Create ConfigSerializer and replace properties and module into config-template.xml

Task to be done:
1. Carry on with next PR for the issue: Create a RequiredThis configs for allowing users more flexibility to run regression

[piyush]

Wednesday, 12th June Report:

Tasks done:
1. Raised and Merged PR: https://github.com/checkstyle/test-configs/pull/30
2. Raised PR: https://github.com/checkstyle/test-configs/pull/31
3. Raised PR: https://github.com/checkstyle/test-configs/pull/32

Task to be done:
1. Create readme file for the github repo of checkstyle: https://github.com/checkstyle/test-configs

What I need from maintainers?
1. Review of my existing PR
2. Discussion of remaining task for month of june, and if they require to be divided into chunks

[piyush]

Monday, 17th June Report:

Tasks done:
1. Address review comments on below PR:
https://github.com/checkstyle/test-configs/pull/38
https://github.com/checkstyle/test-configs/pull/37
2. Had discussions with mentor on future course of action for month of June

Task to be done:
1. Use MainsLauncher.java to do the test-configs for SummaryJavadoc

[piyush]

Monday, 24th June Report:

Task done:
1. Raised PR

A> https://github.com/checkstyle/test-configs/pull/53
B> https://github.com/checkstyle/test-configs/pull/51

Task to be done:
1. Work on issue for dealing with Checks without Treewalker
2. Create yml config in extractor to define what projects should be used in specific Example list of projects file
3. Carry on with test-configs for other packages left

[piyush]

Monday, 2nd July

Task done:
1. Raised PR

A> https://github.com/checkstyle/test-configs/pull/95
B> https://github.com/checkstyle/test-configs/pull/93

2. Task to be done:
A> Work on issue https://github.com/checkstyle/test-configs/issues/90

[piyush]

Thursday, 5th July

1. Raised PR for refactoring in main repo of Checkstyle: https://github.com/checkstyle/checkstyle/pull/15198
2. Tested using PR: https://github.com/checkstyle/checkstyle/pull/14935
3. Raised PR for yml parsing of specific projects list: https://github.com/checkstyle/test-configs/pull/101 

[piyush]

Monday, 9th july Report:

Tasks done:
1. Raised PR: https://github.com/checkstyle/test-configs/pull/112
2. Completed testing: https://github.com/checkstyle/checkstyle/pull/15209

Task to be done
Work on the issues of july

On Wednesday 29 May 2024 at 09:37:37 UTC+5:30 piyush wrote:

[piyush]

Task done:
Raised PR: https://github.com/checkstyle/checkstyle/pull/15395
Testing under Test all-in-one bundles
Working on issues mentioned in https://github.com/checkstyle/test-configs/issues