lp:~jameinel/gouda/create-to-python

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:gouda at revision 26

Gouda (Go u1db implementation) hackers: Pending requested 2012-10-26

Diff: 164 lines (+51/-13)

4 files modified

test_serv/db_manager.go (+9/-7)
test_serv/db_manager_test.go (+6/-6)
test_serv/gouda_serv.py (+5/-0)
test_serv/test_gouda_serv.py (+31/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

36. By John A Meinel on 2012-10-26

Bring the abstraction up a level.

This now let's us have a simpler way of specifying
arguments to the database, and sending the message
through the system.
The next level is probably adding a Database object,
but we'll need to do a fair number of tricks because of
the lack of default params and different capitalization
schemes.

35. By John A Meinel on 2012-10-26

A full integration that we can start in python
send a message to go, and handle the result.
It turns out that json.Unmarshal() treats []byte as an
array of integers, rather than an array of characters,
so you really do need to use 'string' or you get some very
strange 'not an integer' results.

34. By John A Meinel on 2012-10-26

Cleanup the Op function quite a bit.

Pull out the code into helpers that parse json into
Values, and call the function and give you raw bytes
again.
This now should be proper reflection for any methods
that we end up implementing. We can take an array
of arbitrary arguments, and return an array of arbitrary
results.
Unfortunately, Go doesn't support named parameters,
so everything is positional, but we'll survive.

33. By John A Meinel on 2012-10-26

Get the basic reflection code working.

We use json.RawMessage to parse out the individual strings,
then we iterate over them and json.Unmarshal them into
concrete types. That way we don't need to 'know' anything
about JSON encoding.

32. By John A Meinel on 2012-10-26

Get some reflection working, but it is a bit manual.

31. By John A Meinel on 2012-10-26

InvalidOp test.

30. By John A Meinel on 2012-10-26

Pull out the functionality into a 'Fixture' that you can then re-use.

29. By John A Meinel on 2012-10-26

Inspired by juju-core's logging infrastructure,

Set up logging that can actually be overridden and reset.
Now the test suite won't actually produce stipple, but the
log output will be included if a test case fails.

This does seem to provide enough infrastructure to keep things clean.

28. By John A Meinel on 2012-10-26

Add the ability to push logs into test suite details.

Turn the Gouda service into a test suite Fixture, and with any
luck we can add cleanup stuff that allows us to run without having
to actually reset everything. That is for the future, though.
The big win is getting logging to avoid stipple on output.

27. By John A Meinel on 2012-10-26

Finish hooking up the python test suite infrastructure.