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

Backend + UI: Try out request (multi-step feature) #472

Open
4 tasks
NivLipetz opened this issue Oct 8, 2020 · 7 comments
Open
4 tasks

Backend + UI: Try out request (multi-step feature) #472

NivLipetz opened this issue Oct 8, 2020 · 7 comments
Labels

Comments

@NivLipetz
Copy link
Member

Is your feature request related to a problem? Please describe.
I would like to try out a step's request i define in the Create Test form in order to make sure it's valid and functional before running the actual test and finding out after that the test failed to run as expected.

Describe the solution you'd like
Create a "try it out" solution that would allow Predator to execute any request or flow of requests before running the test and validate that the requests are written properly and functioning as expected.

  • Backend: Create API for running requests. API should include all needed params to run the request (variables/headers/body/etc). Response should include status codes of request/s. Should support both:
    • single: trying out a single request
    • multiple: for trying out an entire scenario
  • UI: add button in the Create Test form next to each request/scenario to "try it out". This button should be next to the "duplicate" buttons and should either:
    1. Execute the request (in case no variables are needed for the request to pass)
    2. Open up following pop-up (check next task)
  • UI: Add a pop-up with input textboxes after clicking the "try it out" button if the request/scenario requires any variables needed to run them. This is how we inject necessary variable values into the request/s that will be tried out
  • UI: Display response to the user (whether it succeeded or failed alongside returned status codes)

Additional context
This feature is a multi-step feature and can be worked on simultaneously by more than one person. Each task of the issue can be a different PR.

@lubomirrozhon
Copy link

Hi, I can take UI part of task if is it still available ?

@NivLipetz
Copy link
Member Author

Hi @lubomirrozhon, great to hear you’re interested! I would suggest starting out with adding the try it out button next to each step and scenario in the create test form and continuing it from there, what do you say?

@lubomirrozhon
Copy link

Hi @NivLipetz I agree with you.

@NivLipetz
Copy link
Member Author

Then sounds great, you can start with that, not assigning because i want the issue to stay open for the backend implementation but you can take the UI part 😃 Let us know if you have any questions and feel free to join our slack workspace

@NivLipetz
Copy link
Member Author

Hi @lubomirrozhon how's it going with the issue? Have you had a chance to take a look at it? If there are any questions i'd be happy to help

@lubomirrozhon
Copy link

lubomirrozhon commented Oct 27, 2020

2020-10-27 (7)
Hi I created button, take a look at it if its good. @NivLipetz

@shikouchen
Copy link
Contributor

I may try the backend part if it is still available.

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

No branches or pull requests

4 participants