Home

Welcome to the Go4Api Wiki!

Why another API Testing Tool?

Go4Api aims to the testing difficulty faced to QA, which is different from Developers. That is, plan and execute a single api test is easy, a bunch of tools can help on it. But how about if we have hundreds of API(s) and thousands of test data to manage and execute, and more, regression them during the API(s) lifetime?

Patterns for using Go4Api:

1. Basic Execution (no data dependency)

• Single data hard-coded test case (json)
• Multiple data hard-coded test cases (jsons), with priority and dependency
• Single template json with csv data files(s), the csv data to render the json
• Multiple template jsons with csv data files(s), the csv data to render the json, with priority and dependency

2. Scenario Execution (has data dependency)

• Parent case with outputs file
• Child case with inputs file, along with dependency

3. Fuzz testing

• Mutation testing, based on a snapshot of working test data
• Random testing, based on the definition of the API and its required fields

4. Conversion

• Convert Har file to file can be recognized by Go4Api
• Convert Swagger API file to file can be recognized by Go4Api