You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gsoc@community.apache.org by "Nianjun Sun (Jira)" <ji...@apache.org> on 2024/03/01 06:29:00 UTC
[jira] [Updated] (GSOC-265) [GSOC] [ShardingSphere] Scan and create issues for classes that have not implemented unit tests
[ https://issues.apache.org/jira/browse/GSOC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nianjun Sun updated GSOC-265:
-----------------------------
Description:
h2. 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|https://shardingsphere.apache.org/]
{*}Github{*}: [https://github.com/apache/shardingsphere]
{*}Discussion{*}: https://github.com/apache/shardingsphere/discussions/30252
h2. 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.
h2. 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.
h2. Relevant Skills
1. Master Java language
2. Have a basic understanding of GitHub action
h3. Mentor
Nianjun Sun, Committer of Apache ShardingSphere, sunnianjun@apache.org
was:
h2. 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|https://shardingsphere.apache.org/]
{*}Github{*}: [https://github.com/apache/shardingsphere]
h2. 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.
h2. 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.
h2. Relevant Skills
1. Master Java language
2. Have a basic understanding of GitHub action
h3. Mentor
Nianjun Sun, Committer of Apache ShardingSphere, sunnianjun@apache.org
> [GSOC] [ShardingSphere] Scan and create issues for classes that have not implemented unit tests
> -----------------------------------------------------------------------------------------------
>
> Key: GSOC-265
> URL: https://issues.apache.org/jira/browse/GSOC-265
> Project: Comdev GSOC
> Issue Type: Task
> Reporter: Nianjun Sun
> Priority: Major
> Labels: ShardingSphere, gsoc2024, mentor
>
> h2. 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|https://shardingsphere.apache.org/]
> {*}Github{*}: [https://github.com/apache/shardingsphere]
> {*}Discussion{*}: https://github.com/apache/shardingsphere/discussions/30252
> h2. 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.
> h2. 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.
> h2. Relevant Skills
> 1. Master Java language
> 2. Have a basic understanding of GitHub action
> h3. Mentor
> Nianjun Sun, Committer of Apache ShardingSphere, sunnianjun@apache.org
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: gsoc-unsubscribe@community.apache.org
For additional commands, e-mail: gsoc-help@community.apache.org