Skip to content

Added CI workflow for auto-test #96

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

himashuraj2004
Copy link

@himashuraj2004 himashuraj2004 commented Jun 18, 2025

Pull Request Template

Description

Added a GitHub Actions CI workflow to automate the Keploy record mode for the Employee Manager project. This workflow spins up PostgreSQL using Docker, runs the Spring Boot app in record mode, and triggers a sample API call to start Keploy test recording.
This improves the project by adding CI support for API testing using Keploy.

Fixes # No issue was officially open, but it aligns with the need for automated testing.

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

This workflow has not been executed locally due to environment limitations, but it is written following GitHub Actions best practices.

I have reviewed the syntax and structure to ensure it aligns with other working Java-based CI workflows.

Requesting maintainers to kindly run and validate the workflow in the GitHub Actions environment.

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 checked my code and corrected any misspellings

@pratik-mahalle
Copy link

Hi @himashuraj2004, Thank you for raising the pr. Unfortunately, we can merge this pr as this pr does not contain the appropriate changes which will benefit the project. We really appreciate your effort . This being a part of an assignment in api fellowship would be counted since you were supposed to create a pr but wont be merged since this is not that relevant of a change. I’m sure you understand, and I appreciate your cooperation on this. We will be closing this PR for now.

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.

2 participants