Plans for Test Kitchen


#1

Hey Chefs,

I want to let all you Chef hackers know about changes that are happening
with Test Kitchen.

Fletcher Nichol recently started work on a new project called “jamie”,
which is an integration test runner that has about 99% the same goals as
Test Kitchen. It’s also very close to the same functionality. Fletcher is
awesome, and the jamie project is awesome, and in the interest of a single
tool/stack for running project integration tests (including cookbooks OR
other projects) we’re going to merge test-kitchen and jamie, and use the
"test-kitchen" name.

The jamie project has a number of plugins already, named "jamie-something"
and we plan to have these be “kitchen-something”.

This isn’t ready for release quite yet, as we want to make sure that we
have feature parity with test-kitchen as it stands now.

Development discussion will largely happen through the #chef-hacking IRC
channel and the test-kitchen repository itself.


Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman


#2

fuck. yes.

The Jamie LXC work is amazing

–AJ

On 26 January 2013 12:54, Joshua Timberman joshua@opscode.com wrote:

Hey Chefs,

I want to let all you Chef hackers know about changes that are happening
with Test Kitchen.

Fletcher Nichol recently started work on a new project called “jamie”,
which is an integration test runner that has about 99% the same goals as
Test Kitchen. It’s also very close to the same functionality. Fletcher is
awesome, and the jamie project is awesome, and in the interest of a single
tool/stack for running project integration tests (including cookbooks OR
other projects) we’re going to merge test-kitchen and jamie, and use the
"test-kitchen" name.

The jamie project has a number of plugins already, named "jamie-something"
and we plan to have these be “kitchen-something”.

This isn’t ready for release quite yet, as we want to make sure that we
have feature parity with test-kitchen as it stands now.

Development discussion will largely happen through the #chef-hacking IRC
channel and the test-kitchen repository itself.


Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman


#3

Ohai!

A brief update for those who are interested (or if you’re not, you got
this anyway ;)).

  • Fletcher has migrated the “jamie” code to the test-kitchen repository
    under the “1.0” branch; this will be a prerelease gem, too (alpha)
  • To prevent using the non-released 1.0, all Opscode cookbooks that have a
    Gemfile specifying test-kitchen are updated to pin the version (<= 1.0)
  • The jamie-vagrant driver is migrated to opscode/kitchen-vagrant

As with anything related to chef development, #chef-hacking is
irc.freenode.net channel to participate.

We’ll have more updates at the end of the week.

Cheers,
Joshua

On 1/25/13 4:54 PM, “Joshua Timberman” joshua@opscode.com wrote:

Hey Chefs,

I want to let all you Chef hackers know about changes that are happening
with Test Kitchen.

Fletcher Nichol recently started work on a new project called “jamie”,
which is an integration test runner that has about 99% the same goals as
Test Kitchen. It’s also very close to the same functionality. Fletcher is
awesome, and the jamie project is awesome, and in the interest of a single
tool/stack for running project integration tests (including cookbooks OR
other projects) we’re going to merge test-kitchen and jamie, and use the
"test-kitchen" name.

The jamie project has a number of plugins already, named "jamie-something"
and we plan to have these be “kitchen-something”.

This isn’t ready for release quite yet, as we want to make sure that we
have feature parity with test-kitchen as it stands now.

Development discussion will largely happen through the #chef-hacking IRC
channel and the test-kitchen repository itself.


Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman