Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
D

Dimash Kudaibergen

@Dimash Kudaibergen
About
Posts
1
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • A new API tool, designed for teamwork
    D Dimash Kudaibergen

    Nowadays, every back-end developer creates APIs, every QA engineer tests APIs, and every front-end developer uses APIs. Our business is becoming more complicated, and the number of APIs has increased enormously in recent years. While working around APIs, the API documentation becomes the developing team’s center. However, no one like to write YAML documentation, although API-first has become popular. In many teams, they use several API tools. Swagger is used for defining APIs; Postman is used for debugging APIs; Jmeter is used for testing APIs. If mocking is needed, they have to set up a mock server and write some Faker.js. It works, but it works not well enough. Consider the teamwork details. A is the API designer, and he outputs a YAML file. B is a Java developer who develops the API, so he has to implement it in the code and copy the URL and the parameters into Postman to debug it. C is a QA engineer. To test the API, he must copy the URL and the parameters into Jmeter or another testing platform. D is a front-end developer. Before the API is developed, he has to write mocking scripts for every field. And that’s not the end. Once there is a new version and the API definition changes, everyone has to update every written request. If you miss one, there will be a bug. Everyone copies and pastes and updates again and again, especially in agile teams. There is so much repeat work and so much wasted time. **These tools are not designed for teamwork.** This is why we decided to build a new **API tool for teamworking**. [![img](https://p3-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/cca0c8f35f9c4bdbbea21d728121358e~tplv-k3u1fbpfcp-zoom-1.image)](https://res.cloudinary.com/practicaldev/image/fetch/s--\_DzhpRdX--/c\_limit%2Cf\_auto%2Cfl\_progressive%2Cq\_auto%2Cw\_880/https://cdn-images-1.medium.com/max/1600/1*dp3YcIb\_hpJh\_FDfdYOwfQ.png) [Apidog](http://www.apidog.com/?utm\_source=dev\_to&utm\_medium=Yukioikeda&utm\_content=API\_tool\_designed\_for\_teamwork) is a better toolkit for developing APIs. You can design, debug, test, publish, and mock APIs in only one tool. Now you can stop ctrl + C/V between API tools. Apidog connects everyone in API development. It’s not only a tool. It’s a **system**. [![Apidog Desktop App](https://p3-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/54d8b5bce3ac4386971165853953e187~tplv-k3u1fbpfcp-zoom-1.image)](https://res.cloudinary.com/practicaldev/image/fetch/s--QZ2T7kZk--/c\_limit%2Cf\_auto%2Cfl\_progressive%2Cq\_auto%2Cw\_880/https://dev-to-uploads.s3.amazonaws.com/u

    The Lounge business beta-testing announcement java javascript
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups