Skip to content

Conversation

@Sarthak160
Copy link
Member

Pull Request Template

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Additional Context (Please include any Screenshots/gifs if relevant)

...

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings
  • I have tagged the reviewers in a comment below incase my pull request is ready for a review
  • I have signed the commit message to agree to Developer Certificate of Origin (DCO) (to certify that you wrote or otherwise have the right to submit your contribution to the project.) by adding "--signoff" to my git commit command.

```
mvn clean install -Dmaven.test.skip=true
```
:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove this

#### Spin up the MySQL database

```
docker run command - docker run -e MYSQL_USER=mysql -e MYSQL_PASSWORD=123456 -e MYSQL_ROOT_PASSWORD=123456 -e MYSQL_DATABASE=testdb -p 3306:3306 --rm mysql:latest
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Docker run command - " should be out of the codeblock.

spring.datasource.url=jdbc:mysql://localhost:3306/testdb?useSSL=false&allowPublicKeyRetrieval=true
```

2) Currently best experience for using MySQL support of keploy is to use default settings which where
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make this point clear or remove it.


1) Please note that SSL is currently not supported in the MySQL integration. To use the package without SSL, you can include the following parameters in your database URL like the following example -
```
spring.datasource.url=jdbc:mysql://localhost:3306/testdb?useSSL=false&allowPublicKeyRetrieval=true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Insteading of righting the same code block again, reference the above code block here, or mention this point above itself.

@keploy-staging
Copy link

⚠️ Oops! We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

8 similar comments
@keploy-staging
Copy link

⚠️ Oops! We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@keploy-staging
Copy link

⚠️ Oops! We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@keploy-staging
Copy link

⚠️ Oops! We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@keploy-staging
Copy link

⚠️ Oops! We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@keploy-staging
Copy link

⚠️ Oops! We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@keploy-staging
Copy link

⚠️ Oops! We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@keploy-staging
Copy link

⚠️ Oops! We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@keploy-staging
Copy link

⚠️ Oops! We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@keploy-staging
Copy link

Nice Pr 😄. We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

3 similar comments
@keploy-staging
Copy link

Nice Pr 😄. We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@keploy-staging
Copy link

keploy-staging bot commented Apr 14, 2025

Nice Pr 😄. We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@keploy
Copy link

keploy bot commented Apr 15, 2025

Nice Pr 😄. We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

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

Successfully merging this pull request may close these issues.

3 participants