----- Original Message ----- > From: "Dominic Cleal" <[email protected]> > To: [email protected] > Sent: Wednesday, May 25, 2016 10:29:41 AM > Subject: Re: [foreman-dev] Merge foreman-bats into Forklift > > On 23/05/16 21:48, Ewoud Kohl van Wijngaarden wrote: > > Hello all, > > > > With katello-deploy being renamed to Forklift[1], I was wondering if we > > should merge foreman-bats into it. The benefit would be that it already > > contains some bats tests for Katello and if it's going to be the tool to > > deploy a development env or test env, it's a logical fit for all our > > system tests. > > > > Thoughts? > > I'd prefer to keep foreman-bats where it is, I don't want to mix > it with development tools or plugins. foreman-bats serves a limited > purpose well right now.
Well, Katello hosts its bats tests in Forklift, and we share a lot of common code. Katello misses out on new features and changes to bats helpers. I can understand separating it from development tools, so what about moving Katello's bats to foreman-bats? > -- > Dominic Cleal > [email protected] > > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
