(Migrated) Zato Packages for Development Environment

(This message has been automatically imported from the retired mailing list)

Hi all,

After playing with Zato for a while, I finally decided to use it for in my
personal projects.

My development environment is basically:

  • Operating System: OS X 10.9.4
  • Python Version: 2.7.6

And I’m using the following python packages:

  • tox
  • py.test

Following a TDD approach, I need to write unit tests before writing any
production code.

In order to actually write a Zato service, I need to import the zato
package, but I had no luck so far.

It tried to pip install the packages below, but none of them worked:

  • zato
  • zato-client
  • zato-common

Maybe some of the requirements from one of the packages above can be
removed, so I can easily install it on Mac OS X.

Just to make it clear, I don’t expect to have a fully Zato environment
working on my development machine, I just wanted to be able to import the
zato.server.service package.

PS.: I already have a Zato Cluster up and running with Vagrant and
VirtualBox, but I don’t want run my tests in that environment.

On 13/07/14 22:04, Rafael Martins wrote:

Following a TDD approach, I need to write unit tests before writing any
production code.

Hi Rafael,

have you considered using zato-apitest?

This is what I’d recommend instead of unit-tests directly against the
code. That way you can test the actual API instead of a lowest layer alone.

On 13/07/14 22:04, Rafael Martins wrote:

Following a TDD approach, I need to write unit tests before writing any
production code.

Hi Rafael,

have you considered using zato-apitest?

This is what I’d recommend instead of unit-tests directly against the
code. That way you can test the actual API instead of a lowest layer alone.

A blog, huh?

That’s actually a very interesting idea!
I’m sure I’ll have a lot of great stuff to share about zato from now on. :slight_smile:

I’ll get back to you soon.

PS: I forgot to reply to the mailing list before, so I added the email
address again so other users browsing the list will also be able to follow
up.

On Mon, Jul 14, 2014 at 6:12 AM, Dariusz Suchojad dsuch@zato.io wrote:

On 14/07/14 06:38, Rafael Martins wrote:

Hi,

I think I finally managed to get a workaround, check it out:

[…]

Thanks - that looks interesting. Do you perhaps maintain a blog you can
write about it so I could link to it on the project’s mailing list?


Dariusz Suchojad

https://zato.io
ESB, SOA, REST, APIs and cloud integrations in Python

Done: http://fael84.com/mocking-packages-and-modules-in-python.html

On Mon, Jul 14, 2014 at 7:26 AM, Rafael Martins rafael84@gmail.com wrote:

A blog, huh?

That’s actually a very interesting idea!
I’m sure I’ll have a lot of great stuff to share about zato from now on.
:slight_smile:

I’ll get back to you soon.

PS: I forgot to reply to the mailing list before, so I added the email
address again so other users browsing the list will also be able to follow
up.

On Mon, Jul 14, 2014 at 6:12 AM, Dariusz Suchojad dsuch@zato.io wrote:

On 14/07/14 06:38, Rafael Martins wrote:

Hi,

I think I finally managed to get a workaround, check it out:

[…]

Thanks - that looks interesting. Do you perhaps maintain a blog you can
write about it so I could link to it on the project’s mailing list?


Dariusz Suchojad

https://zato.io
ESB, SOA, REST, APIs and cloud integrations in Python