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]: Give an option to user to name testcases #880

Closed
1 task done
charankamarapu opened this issue Sep 26, 2023 · 3 comments · Fixed by #903
Closed
1 task done

[feature]: Give an option to user to name testcases #880

charankamarapu opened this issue Sep 26, 2023 · 3 comments · Fixed by #903
Assignees

Comments

@charankamarapu
Copy link
Member

Is there an existing feature request for this?

  • I have searched the existing issues

Summary

There are many situations where user want to give a proper name their testcases like GetEmployeeSuccessful, GetEmployeeValidationError etc which gives them lot of info regarding their tests. Right now keploy has no such option where we allow user to name the tests . User has to rename the test case manually .

A feature can introduced where user can give the name for tests. This cannot be done at CLI because once record starts there can be n number of tests that user can create and we cannot give an option in CLI to name test in the middle of record command execution. There can be a way at the API level when user will hit a request, user can add an header which says Keploy_Test_Name and we need to handle it where we capture the incoming request and name the test with that Keploy_Test_Name.

Why should this be worked on?

Its a good user exeperience

Repository

keploy

@charankamarapu charankamarapu changed the title [feature]: Give an option to user to name his testcases [feature]: Give an option to user to name testcases Sep 26, 2023
@charankamarapu charankamarapu added the Good First Issue Good for newcomers label Sep 26, 2023
@AkashKumar7902
Copy link
Contributor

@charankamarapu can you please assign me this issue?

@charankamarapu
Copy link
Member Author

ok

@charankamarapu
Copy link
Member Author

Please make an issue in the docs to mention this feature and link that issue here so that I can close this issue . Try if you can also complete the doc issue.

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

Successfully merging a pull request may close this issue.

2 participants