TeamCity vs Test Kitchen

Need advice about which tool to choose?Ask the StackShare community!

TeamCity

1K
901
+ 1
307
Test Kitchen

40
44
+ 1
15
Add tool

TeamCity vs Test Kitchen: What are the differences?

What is TeamCity? TeamCity is an ultimate Continuous Integration tool for professionals. TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

What is Test Kitchen? Integration tool for developing and testing infrastructure code and software on isolated target platforms. Test Kitchen has a static, declarative configuration in a .kitchen.yml file at the root of your project. It is designed to execute isolated code run in pristine environments ensuring that no prior state exists. A plugin architecture gives you the freedom to run your code on any cloud, virtualization, or bare metal resources and allows you to write acceptance criteria in whatever framework you desire.

TeamCity and Test Kitchen can be categorized as "Continuous Integration" tools.

"Easy to configure" is the primary reason why developers consider TeamCity over the competitors, whereas "Automated testing" was stated as the key factor in picking Test Kitchen.

Test Kitchen is an open source tool with 1.62K GitHub stars and 543 GitHub forks. Here's a link to Test Kitchen's open source repository on GitHub.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of TeamCity
Pros of Test Kitchen
  • 60
    Easy to configure
  • 37
    Reliable and high-quality
  • 31
    User friendly
  • 31
    Github integration
  • 31
    On premise
  • 18
    Great UI
  • 16
    Smart
  • 12
    Free for open source
  • 12
    Can run jobs in parallel
  • 8
    Crossplatform
  • 4
    REST API
  • 4
    Great support by jetbrains
  • 4
    Fully-functional out of the box
  • 4
    Projects hierarchy
  • 4
    Chain dependencies
  • 3
    100+ plugins
  • 3
    Free for small teams
  • 3
    Per-project permissions
  • 3
    Personal notifications
  • 3
    Build templates
  • 2
    Ide plugins
  • 2
    GitLab integration
  • 2
    Smart build failure analysis and tracking
  • 2
    Upload build artifacts
  • 2
    Artifact dependencies
  • 2
    Build progress messages promoting from running process
  • 1
    TeamCity Professional is FREE
  • 1
    Powerful build chains / pipelines
  • 1
    Built-in artifacts repository
  • 1
    Repository-stored, full settings dsl with ide support
  • 0
    Official reliable support
  • 0
    High-Availability
  • 0
    Hosted internally
  • 6
    Automated testing
  • 4
    Detect bugs in cook books
  • 2
    Integrates well with vagrant
  • 2
    Can containerise tests in Docker
  • 1
    Integrates well with puppet

Sign up to add or upvote prosMake informed product decisions

Cons of TeamCity
Cons of Test Kitchen
  • 1
    Proprietary
  • 1
    High costs for more than three build agents
  • 1
    User friendly
  • 1
    User-friendly
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is TeamCity?

    TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

    What is Test Kitchen?

    Test Kitchen has a static, declarative configuration in a .kitchen.yml file at the root of your project. It is designed to execute isolated code run in pristine environments ensuring that no prior state exists. A plugin architecture gives you the freedom to run your code on any cloud, virtualization, or bare metal resources and allows you to write acceptance criteria in whatever framework you desire.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use TeamCity?
    What companies use Test Kitchen?
    See which teams inside your own company are using TeamCity or Test Kitchen.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with TeamCity?
    What tools integrate with Test Kitchen?
      No integrations found

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      What are some alternatives to TeamCity and Test Kitchen?
      Jenkins
      In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
      Appveyor
      AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.
      Hudson
      It monitors the execution of repeated jobs, such as building a software project or jobs run by cron. Among those things, currently it focuses on the two jobs
      Octopus Deploy
      Octopus Deploy helps teams to manage releases, automate deployments, and operate applications with automated runbooks. It's free for small teams.
      FinalBuilder
      With FinalBuilder you don't need to edit xml, or write scripts. Visually define and debug your build scripts, then schedule them with windows scheduler, or integrate them with Continua CI, Jenkins or any other CI Server.
      See all alternatives