Clean up code for hacky OpenAPI curl test
See original GitHub issueAfter testing deactivate_own_account endpoint, we need to reactivate the client so that other tests are not affected by the deactivated client. In test_curl_examples, this has been hackily implemented and should be replaced by cleaner code. More details at https://github.com/zulip/zulip/pull/17014#discussion_r601173277
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Creating OpenAPI from HTTP Traffic | APIs You Won't Hate
We wrote before about some slightly hacky ways to create OpenAPI from things like Postman Collections, using JSON to JSON Schema converters, and ......
Read more >How to Use curl for Testing REST APIs (Test CRUD Operations)
1. Use curl to Test Retrieval REST APIs ... You can use the -X flag to specify HTTP method of the request. Since...
Read more >OpenAPI generator to spring-boot with custom java validations
This tutorial will show you how to add capability of using custom constraint validation annotations in code generated from OpenAPI specs.
Read more >HTB: Backend | 0xdf hacks stuff - GitLab
To get the location of the web server code, I'll read the environment of the current process at /proc/self/environ : oxdf@hacky$ curl -s...
Read more >API Smoke test - seems no tool available to test response ...
API Smoke test - seems no tool available to test response matches the response format as described in OpenAPI spec 3.0 generated by...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Yes, it was just added for reactivating the client after the deactivation.
Hello @100RABHpy, you claimed this issue to work on it, but this issue and any referenced pull requests haven’t been updated for 10 days. Are you still working on this issue?
If so, please update this issue by leaving a comment on this issue to let me know that you’re still working on it. Otherwise, I’ll automatically remove you from this issue in 4 days.
If you’ve decided to work on something else, simply comment
@zulipbot abandonso that someone else can claim it and continue from where you left off.Thank you for your valuable contributions to Zulip!