Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

License

NotificationsYou must be signed in to change notification settings

checkstyle/regression-tool

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

75 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Regression-tool is an automation tool to do regression testing based on proposed patch(Pull Request)of checkstyle project. The tool could generate configuration based on Git changes, which is used togenerate diff report between the base and the patch branch.

Setup

Requirements

  • Checkstyle repository which including both master and patch branch need to be cloned.In most case, it should be your forked repository.
  • Contribution repository need to be cloned.
  • Regression-tool uses environment variableM2_HOME or system propertymaven.home to find the maven binary files.You need to specify eitherM2_HOME ormaven.home in advance. You could get the path of maven home by runningmvn -v.

Clone

Just clone this repository to your local.

$ git clone git@github.com:checkstyle/regression-tool.git

Or use HTTPS mode.

$ git clone https://github.com/checkstyle/regression-tool.git

Generate Jar

Generate aregression-tool-XX-all.jar(XX means the version of regression-tool) in thetarget folder.

$cd /path/to/regression-tool$ mvn clean package -Passembly

Usage

$ java -jar regression-tool-XX-all.jar -r<arg> -p<arg> [-t<arg>] [--stopAfterConfigGeneration]

Arguments

checkstyleRepoPath (r)

The path of the checkstyle repository.Required, one argument.

patchBranch (p)

The name of the PR branch, which would be compared with the master.Required, one argument.

stopAfterConfigGeneration

Indicates that regression-tool would stop after generating config. By default, the tool would generatethe diff report after generating config.Optional, no argument.

The report generation might requires network and be time-consuming.If you are not able to connect to network or just don't want to do the generation right now,you could use this mode.

checkstyleTesterPath (t)

The path of the checkstyle-tester directory. If you areNOT using--stopAfterConfigGeneration mode, thisoption is required, otherwise this could be absent.Optional, one argument.

Example

Here is an example in CI.

Generate regression report for branchissue1234.

$ java -jar target/regression-tool-XX-all.jar -r /path/to/checkstyle/ -p issue1234 -t /path/to/contribution/checkstyle-tester/

You could also use long options.

$ java -jar target/regression-tool-XX-all.jar --checkstyleRepoPath /path/to/checkstyle/ --patchBranch issue1234 --checkstyleTesterPath /path/to/contribution/checkstyle-tester/

Generate only the config file and don't generate the report.

$ java -jar target/regression-tool-XX-all.jar -r /path/to/checkstyle/ -p issue1234 --stopAfterConfigGeneration

Output

The config file would be generated in current working directory.

The report would be generated somewhere in TBD.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors6


[8]ページ先頭

©2009-2025 Movatter.jp