Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log failure and store -2 in case of problems with build or tests #17

Open
snadi opened this issue Aug 29, 2018 · 2 comments
Open

Log failure and store -2 in case of problems with build or tests #17

snadi opened this issue Aug 29, 2018 · 2 comments

Comments

@snadi
Copy link
Contributor

snadi commented Aug 29, 2018

If you could not run the build or test for any reason, or the repo doesn't support mvn, then store -2 (And update documentation in ReadMe or data schema description) and log a failure

https://github.com/ualberta-smr/code-owhadi-msr19/blob/1724d8a2ff6b334c0775a8498359ce892249d320/merge_excavator/code_quality.py#L33

@mkareshk
Copy link
Collaborator

mkareshk commented Sep 9, 2018

@snadi Do you have any idea about the ways of "counting" the number of test cases? I think parsing the output of mvn test is not a good idea.

@snadi
Copy link
Contributor Author

snadi commented Sep 10, 2018

Unfortunately, I don't think there's a direct command you can use to give you the number of tests (At least that I know of and based on some quick searching) so I guess we have two options:

(1) grep for things in the output of mvn test
(2) count the number of @test annotations inside of java files in the test directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants