The Problem

Automated Tests Run Everywhere. Results Disappear Into Logs.

Your team runs thousands of automated tests every day. The results? Buried in CI output that nobody reads.

Console Output Nobody Reads

Test results scroll by in a terminal and vanish. Passed? Failed? Flaky? Good luck finding out after the fact.

JUnit XMLs Rotting in CI Artifacts

Your frameworks already generate structured results. They sit in artifact storage for 30 days, then get deleted.

Manual Copy-Paste Circus

Someone has to manually update the test management tool after every CI run. They do not. Or they miss failures. Or they quit.

Zero Visibility for the Team

Managers, QA leads, and product owners have no idea what your automation actually covers. No trends. No dashboards.

CI/CD Integrations

Native Plugins. Not Shell Scripts.

Official, maintained plugins for the CI/CD platforms your team actually uses.

GitHub Actions
GitLab CI
CircleCI
Jenkins
.github/workflows/test.yml
Official Action
# .github/workflows/test.yml
steps:
  - name: Run tests
    run: npm test
  - name: Submit results to TestFiesta
    uses: testfiesta/tacotruck-action@v1
    with:
      provider: testfiesta
      handle: your-org
      project: your-project
      results-path: ./test-results/*.xml
.gitlab-ci.yml
Official Component
# .gitlab-ci.yml
include:
  - component: gitlab.com/testfiesta/tacotruck-gitlab/submit@1.0.0
    inputs:
      provider: testfiesta
      handle: your-org
      project: your-project
      results-path: test-results/*.xml
.circleci/config.yml
Official Orb
# .circleci/config.yml
orbs:
  tacotruck: testfiesta/tacotruck@1.0.0
jobs:
  test:
    executor: tacotruck/default
    steps:
      - checkout
      - run: npm test
      - tacotruck/submit:
          provider: testfiesta
          results-path: test-results/*.xml
Jenkinsfile
Official Plugin
// Jenkinsfile (Declarative Pipeline)
pipeline {
    stages {
        stage('Test') {
            steps {
                sh 'npm test'
            }
            post {
                always {
                    tacotruck provider: 'testfiesta',
                             project: 'your-project',
                             resultsPath: 'test-results/*.xml'
                }
            }
        }
    }
}

Jenkins Freestyle users: add the "Execute Tacotruck" build step in your job configuration. No Groovy required.

Beyond Results

Full Test Management CLI

TacoTruck isn't just for submitting results. Manage your entire TestFiesta setup from the command line. Infrastructure as code for your test management.

Projects

Create, list, and delete projects programmatically. Spin up new projects from CI or provisioning scripts.

$ tacotruck testfiesta project:create --name "API Tests"

Custom Fields

Full CRUD for custom fields -- text, number, boolean, select, multiselect, and date types.

$ tacotruck testfiesta field:create --name "Priority" --type select

Tags & Milestones

Organize with colors, due dates, and status tracking tied to your release schedule.

$ tacotruck testfiesta milestone:create --name "v2.4" --due "2026-06-01"

Templates

Create reusable test-case and test-run templates. Standardize across teams without manual setup.

$ tacotruck testfiesta template:create --name "Smoke" --type test-run
Migration

Already on TestRail?

No big-bang migration required. Evaluate TestFiesta in parallel with your current setup.

Run Both

Dual-Provider Mode

Submit test results to TestFiesta AND TestRail simultaneously during your evaluation period. Compare side by side.

Drop-In

TestRail API Shim

TestFiesta provides full TestRail v2 API compatibility. Your existing TestRail scripts work unchanged.

Your Pace

Gradual Migration

Start with one project. Move teams at your own pace. TacoTruck handles the data migration when you are ready.

Learn About Migration

Connect Your Tests to TestFiesta Today

One CLI. Every Framework.

22 frameworks. 5 CI/CD platforms. One command. Your automated test results finally have a home.

Start Free TrialBook a Demo