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

Make the test generation great (4) - use static code analysis to better handle the sources, tests, imports, etc ... #45

Open
mrT23 opened this issue May 25, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@mrT23
Copy link
Contributor

mrT23 commented May 25, 2024

No description provided.

@mrT23 mrT23 added the enhancement New feature or request label May 25, 2024
@EmbeddedDevops1
Copy link
Collaborator

@mrT23 Can we close this issue?

@ramsey-coding
Copy link

@mrT23 @EmbeddedDevops1 what do you really want with static analysis?

@ramsey-coding
Copy link

@mrT23 @EmbeddedDevops1 it is very vague. Can you explicitly mention what exactly you want to do with static analysis?

@GerniVisser
Copy link

I believe @mrT23 means using somthing similar to SonarCube that can analize the generated code to ensure that the test not only runs but is written well. I suggest if this be taken up that the report generated by the static analyzer should also be brought into considiration when deciding if a new test should be generated. These static analyzers can check for quite a few scenarios and just ensures that the code that eventually gets generated is of better quality..

Anyway Hello I'm new here and is quite interested in this project and would like to contribute. Im new to open source and learning the ropes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
4 participants