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

Use only one request to save/update tests #256

Closed
utkarsh-dixit opened this issue Aug 1, 2022 · 0 comments
Closed

Use only one request to save/update tests #256

utkarsh-dixit opened this issue Aug 1, 2022 · 0 comments

Comments

@utkarsh-dixit
Copy link
Member

Earlier, we used to allow saving/updating tests without asking the user to login from the recorder. The legacy flow use to look like this,

  1. Saving/Updating test will create a temporary record in backend through /save.temp API.
  2. User would be redirection app.crusher.dev/tests page and once user is Authorised it will create/update the test.

With the new v1.0.5 release, the user is asked to login/connect to cloud account so the legacy workflow is no longer needed. We now only need to call one API, instead of two

@utkarsh-dixit utkarsh-dixit changed the title Use only on request to save/update tests Use only one request to save/update tests Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant