cf-charmers team mailing list archive

[Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>]

stop me when this sounds strange. we know when the cf-release for 153 was
made as a point in time, we can find the revision of cats that was current
at the time, and try to run it as it presumably was at the time of release?

-k



On Wed, Apr 23, 2014 at 7:10 AM, Manuel Garcia <mgarciap@xxxxxxxxx> wrote:

> Hi guys,
>
> There is no tags/versions relationship between CF RELEASE and CF
> Acceptance Tests project.
>
> Our current situation is that there is no way to make CATS work agains our
> Bundle (cf release 153) without us modifying CATS which does not make any
> sense at all.
> You can take a look at James answer email below.
>
> Alternatives:
> A) Identify if passing tests are enough and custimize CATs to only run
> ‘compatible’ tests
> B) Develop a very simple script to test the following CLI actions: target
> api, login, create org, create space, switch to space, push a our simple
> app example, curl and test output, delete app.
>
> Action Items:
> - Spend few hours with ‘A' only identifying if compatible tests are enough
> - Share results and suggestion with the team
>
> Any comments, feedback will be much appreciated.
>
> Manuel
>
>
>
> Begin forwarded message:
>
> *From: *Alexander Lomov <lomov.as@xxxxxxxxx>
> *Subject: **Re: [vcap-dev] Running latest CATs tests on CF v153.*
> *Date: *April 23, 2014 at 7:03:53 AM GMT-3
> *To: *<vcap-dev@xxxxxxxxxxxxxxxx>
> *Reply-To: *<vcap-dev@xxxxxxxxxxxxxxxx>
>
> Thank you, James. It really make sense.
>
>
>
> On 22 April 2014 20:28, James Bayer <jbayer@xxxxxxxxxxxxx> wrote:
>
>> i appreciate the difficulty. there is a story under consideration to put
>> CATS as a submodule of cf-release [1] so that you'll always know the
>> compatible CATS version for the release # of cloud foundry you are using.
>>
>> [1] https://www.pivotaltracker.com/story/show/69934952
>>
>>
>> On Tue, Apr 22, 2014 at 8:15 AM, Alexander Lomov <lomov.as@xxxxxxxxx>wrote:
>>
>>> Hi, all.
>>>
>>> We've found an error in the way how latest CATs works with CF v153. The
>>> thing is that CATs creates names for orgs, users and apps with upper case.
>>> As I see CF v153 is designed to work with names that have lower case. To
>>> fix this issue I made some changes to CATs (https://github.com/allomov/
>>> cf-acceptance-tests/commit/0411c77e822ec1dd0eee3601169b75
>>> c8a9975e80#diff-b5c76fbd59b67a63c2e4080cbb9c7148L49) and after this
>>> changes we was able to run tests that was falling.
>>>
>>> I see that the latest version of CATs is incompatible with CF v153, but
>>> CATs repo doesn't have any tags or references to cf release it supports.
>>> The question is about CATs version we need to use to validate our
>>> deployment. Do we need to checkout older version of CATs or we need to
>>> patch latest version? I guess I'll also write to vcap-dev google group
>>> about it?
>>>
>>>
>>> Thank you,
>>> Alex.
>>>
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to vcap-dev+unsubscribe@xxxxxxxxxxxxxxxx.
>>>
>>
>>
>>
>> --
>> Thank you,
>>
>> James Bayer
>>
>
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vcap-dev+unsubscribe@xxxxxxxxxxxxxxxx.
>
>
>
> --
> Mailing list: https://launchpad.net/~cf-charmers
> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~cf-charmers
> More help   : https://help.launchpad.net/ListHelp
>
>