-
Notifications
You must be signed in to change notification settings - Fork 79
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
Create a test project to check new plugin rule in real environment #65
Comments
Hi @jhertout, |
Hi @dedece35, It the same for us, our test projects is almost like the unit tests. The only thing is that we add a comment at the end of a line that should trigger an issue like this :
This enable us to know if the rule is triggered on the good line without thinking and if it it is the rule we expect. |
Hi @jhertout, |
Hello, do you think we should put the test projects in another repository? It's just an idea in order not to overload this repository, maybe a bad one. It depends if we need them during the development phase or not. |
The new repository is ready for Java language : https://github.com/green-code-initiative/ecoCode-java-test-project |
for python plugin, I created the new repo https://github.com/green-code-initiative/ecoCode-python-test-project |
Hi @dedece35, |
Hi, all test projects are up and ok. |
Is your feature request related to a problem? Please describe.
currently, when a developer create a new rule in the plugin, he can test it with unit tests but not on a real SonarQube environment.
Describe the solution you'd like
Create a new project / repository containing an example application (one by language ?) which can be used to push on local development SonarQube environment to check if the new rule is OK.
It would be an integration test.
Maybe we can use all current source files used in unit tests.
The text was updated successfully, but these errors were encountered: