Show HN: We built a tool that automatically generates API tests

#1

Post by Wissmueller » Mon, Oct 10, 2022, 1:57 PM UTC

Hi, this is Mish and Sebastian. We are working on Step CI - a fully automated API testing platform for developers.

Step CI works programming-language independent and for different API paradigms (REST, GraphQL, XML).

Our CLI and test runner are available on GitHub (https://github.com/stepci) under the MPLv2 license.

Since our last launch, Step CI is now able to generate automated tests for your API based on your OpenAPI (Swagger) spec. This saves you a lot of time as you never have to write and maintain your tests again!

We would like to invite you to try our tool and give us feedback! Please star us on GitHub, if you like what we are working on!

We are very thankful for your attention and any feedback or suggestions we receive from you :)

Mish and Sebastian from Germany

Show HN: We built a tool that automatically generates API tests
stepci.com

Re: Show HN: We built a tool that automatically generates API tests

#2

Post by fernandorojo » Mon, Oct 10, 2022, 2:30 PM UTC

Cool idea. I’ll definitely check it out. We’ve been thinking of making something similar internally.

Re: Show HN: We built a tool that automatically generates API tests

#3

Post by inglor » Mon, Oct 10, 2022, 2:34 PM UTC

How do you deal with state between API calls? (For example, a user filling a shopping cart, getting discounts based on their geo/products and then checking out)

Re: Show HN: We built a tool that automatically generates API tests

#4

Post by ushakov » Mon, Oct 10, 2022, 2:35 PM UTC

fernandorojo wrote: post #2

Cool idea. I’ll definitely check it out. We’ve been thinking of making something similar internally.

Hello Fernando, this is Mish from Step CI

We're glad you liked the idea! I had this idea in my head for about 2 years until I met Sebastian and we decided to give it a try!

We already support sending GraphQL queries and validating the responses

Soon we will also be able to generate automated API tests based on your GraphQL Schema. You can watch our main repository (https://github.com/stepci/stepci) or subscribe to our newsletter to follow our progress!

Thanks in advance for checking out our tool!

Re: Show HN: We built a tool that automatically generates API tests

#5

Post by ushakov » Mon, Oct 10, 2022, 2:40 PM UTC

inglor wrote: post #3

How do you deal with state between API calls? (For example, a user filling a shopping cart, getting discounts based on their geo/products and then checking out)

Hello, this is Mish from Step CI

Thanks for your question!

We allow you to capture content like headers, response and cookies between steps using captures, check out the "Captures" example in our Demo

Here's a documentation with examples for all capture types: https://github.com/stepci/stepci/blob/main/docs/workflow-syn...

also: we manage cookies for you automatically

Re: Show HN: We built a tool that automatically generates API tests

#6

Post by manishrana » Mon, Oct 10, 2022, 3:30 PM UTC

This is really a useful tool

Re: Show HN: We built a tool that automatically generates API tests

#7

Post by LeonidBugaev » Mon, Oct 10, 2022, 3:37 PM UTC

If you are looking for a more general tool, which can do not only API tests, but also interact with Databases and etc, but still use declrative syntax, try Venom https://github.com/ovh/venom

Re: Show HN: We built a tool that automatically generates API tests

#8

Post by mrwnmonm » Mon, Oct 10, 2022, 3:37 PM UTC

love the design

Re: Show HN: We built a tool that automatically generates API tests

#9

Post by airocker » Mon, Oct 10, 2022, 3:42 PM UTC

LeonidBugaev wrote: post #7

If you are looking for a more general tool, which can do not only API tests, but also interact with Databases and etc, but still use declrative syntax, try Venom https://github.com/ovh/venom

Why use venom? Why not just pytest ?

Re: Show HN: We built a tool that automatically generates API tests

#10

Post by airocker » Mon, Oct 10, 2022, 3:44 PM UTC

Hi , I tried to build cli from swagger, it was a disaster: very verbose and did not really work. I am wondering what’s the verbosity of your tool. How do you deal with imperfect specs?