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

[feature]: test command with coverage flag to serve command internally #1292

Closed
1 task done
Sarthak160 opened this issue Jan 2, 2024 · 1 comment · Fixed by #1300 or #1344
Closed
1 task done

[feature]: test command with coverage flag to serve command internally #1292

Sarthak160 opened this issue Jan 2, 2024 · 1 comment · Fixed by #1300 or #1344
Assignees
Labels
Enhancement New feature or request keploy

Comments

@Sarthak160
Copy link
Member

Sarthak160 commented Jan 2, 2024

Is there an existing feature request for this?

  • I have searched the existing issues

Summary

  • Currently in all other 3 languages except go we use serve command for eg-
    sudo -E keploy serve -c "python3 -m coverage run -m pytest test_keploy.py" --delay 10
    Also for Java - refactor: Add new methods according to new approach of keploy serve  java-sdk#159
  • But from the user point of view it will be more relevant to use just one common command which can be of test only, so whenever user will give flag --coverage along with test command it will internally call serve method instead of actual test method . So the command can look like -

sudo -E keploy test -c "python3 -m coverage run -m pytest test_keploy.py" --coverage --delay 10

  • Also refactor the common methods which are duplicate in both test and serve command.

Why should this be worked on?

To improve the user experience for using native frameworks for coverage purposes.

Repository

keploy

@Sarthak160 Sarthak160 added the Enhancement New feature or request label Jan 2, 2024
@github-actions github-actions bot added the keploy label Jan 2, 2024
@EraKin575
Copy link
Contributor

please assign this to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment