3
6 Comments

Need help in validating problems in existing API testing tools. Curating an idea!

Hello, I have been developing a no-code API testing tool for last 6 months to solve some really painful problems I felt in API Testing. Please give me your honest and toughest feedback.

The problems I feel are -

  1. There are a lot of tools, but none of them covers all the aspects of API Testing i.e. Functional (hit-n-trial), assertions, scenario (flow of APIs) and load testing
  2. Because of lots of tools, its redundant to do configurations in each tool separately
  3. All different tools requires us to go through a new learning curve
  4. JMeter has a complicated UI for 2021
  5. Devs don't do load testing because its too much hassle
  6. Existing tools don’t show details about errors other than APIs HTTP response
  7. Existing tools are overpriced
on February 1, 2021
  1. 1

    Tried to convery the problems better in this short comic about problems in existing API testing tools - Checkout comic on imgur

  2. 1

    Can't say much about this, because I come from a design background. But it definitely helps in increasing productivity when you can do more things in less tools. So you have my vote to solve these issues.

  3. 1

    Postman is the real player in this space. They did a great job collecting the low hanging fruit in terms of engaging all types of users in working with APIs.

    They also make it simple, if not necessarily easy. So having worked in this space for the past decades, and quite recently felt a lot of those same pain points. It is about time for something to emerge as Postman alternative.

    1. 1

      That said, I'll certainly take a look at your project, should you share it.

  4. 1

    You need to learn/work on getting this more concise.
    Can you convince a company to sign a 50k$/yearly licence for this? Plus all the teams like testing and dev to use this?
    Would you be replacing a specific set of services? How much do they cost? Do you completely 100% replace them for a company?

    1. 1

      Thanks @hatkyinc, I've reduced content in half.

      I plan to keep it free to use with non-cloud features, and also release a opensource self-hostable service for essential cloud features.
      Hoping testers will adopt it for its no-code benefit and devs for the in-depth analysis of errors during testing.
      Targetting API testing, development and collaboration features only, as a better completely replacable alternative to Postman, ReadyAPI etc for these use cases for the starter