[GSOC-265] [GSOC] [ShardingSphere] Scan and create issues for classes that have not implemented unit tests

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: ShardingSphere gsoc2024 mentor small
• Assignee: Unassigned
• Reporter: Nianjun Sun
• Created: 29/Feb/24 03:21
• Updated: 29/Mar/24 08:34

Description

Apache ShardingSphere

Apache ShardingSphere is positioned as a Database Plus, and aims at building a standard layer and ecosystem above heterogeneous databases. It focuses on how to reuse existing databases and their respective upper layer, rather than creating a new database. The goal is to minimize or eliminate the challenges caused by underlying databases fragmentation.

Page: https://shardingsphere.apache.org

Github: https://github.com/apache/shardingsphere 

Discussion: https://github.com/apache/shardingsphere/discussions/30252

Background

The ShardingSphere community has been striving for high unit test coverage, so ShardingSphere community needs a scanning tool to identify all classes without implemented unit tests, then generate a report based on the results, and create corresponding issues in the ShardingSphere community.

Task

Here are the steps for the scannning tool:
1. Scan the ShardingSphere project for classes that have not implemented unit tests(exclude the enum, constant, entity, interface and so on) in GitHub action;
2. Generate report base on these scan result;
3. Create issues automatically.

Relevant Skills

1. Master Java language
2. Have a basic understanding of GitHub action

Mentor

  Nianjun Sun, Committer of Apache ShardingSphere, [e-mail]

 
Difficulty: Major
Project size: ~175 hour (medium)