Skip to main content
← Back to workflows

How to Utilize CI for API Test Automation

stepci-stepci -
GitHub Action
2.8.1
1,635
Contributors
Contributor - mishushakovContributor - npostulartContributor - Dinoosawruss
Categories
CICUBE ANALYTICS INSIGHTS
Engineering Velocity: 25% Team Time Lost to CI Issues
View Platform →
3.5h
Time Saved/Dev/Week
40%
Faster Releases
Click for next insight
Usage
name: 'Usage of Step CI GitHub Action'
on:
push:
branches:
- main
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Step CI Action
uses: stepci/stepci@main
with:
workflow: "tests/workflow.yml"

stepci logo

Step CI

Automated API Testing and Quality Assurance


What is Step CI?

Step CI, an open-source API Quality Assurance framework that's ideal for our needs in security, performance, and load testing APIs. Here's how you can integrate Step CI into our workflow.

Step CI is designed to be language-agnostic, supporting multiple configuration formats like YAML, JSON, or JavaScript. It can handle various types of APIs, including REST, GraphQL, gRPC, tRPC, and SOAP, all within a single workflow.

Key Features:

  • Language-Agnostic: Easy configuration with YAML, JSON, or JavaScript.
  • Supports Multiple API Types: Compatible with REST, GraphQL, gRPC, tRPC, and SOAP.
  • Self-Hosted: Can be deployed to test services on local networks, locally, and within CI/CD pipelines.
  • Integrated: Designed to integrate smoothly with other tools and systems.