Re: [DISCUSS] refactoring the marvin integration library

2013-01-23 Thread Chirag Jog
Interestingly we had evaluated the robot framework : https://code.google.com/p/robotframework/ which isn't really a DSL but more of a keyword driven BDD. One can define key words that map to real actions as mentioned in the above thread. It generates logs in HTML format as well. Regards*,*

Re: [DISCUSS] refactoring the marvin integration library

2013-01-21 Thread Prasanna Santhanam
On Fri, Jan 18, 2013 at 06:51:07PM -0500, Chiradeep Vittal wrote: The idea would be that a dev/QA working on a feature could write a test case like: Feature: AWS-style health checks In order to foo blah blarg Scenario: create health check Given a zone of type Advanced And a user

Re: [DISCUSS] refactoring the marvin integration library

2013-01-18 Thread Prasanna Santhanam
On Fri, Jan 18, 2013 at 07:17:13AM +0530, Chiradeep Vittal wrote: +1. Sounds more like a new feature than a 'refactor'. What I'd like is a DSL-kind of experience (which is what cloudmonkey is tending to) Then we could use Lettuce or Cucumber to write some tests. Thanks Chiradeep, the marvin

[DISCUSS] refactoring the marvin integration library

2013-01-17 Thread Prasanna Santhanam
Marvin is a great tool for simplifying test case writing. The integration library within it over time has become slighlty unweildy to use while adapting to the changing API nature. In order to make test case writing quicker and somewhat intuitive I propose to do a small refactor of the

Re: [DISCUSS] refactoring the marvin integration library

2013-01-17 Thread Chiradeep Vittal
+1. Sounds more like a new feature than a 'refactor'. What I'd like is a DSL-kind of experience (which is what cloudmonkey is tending to) Then we could use Lettuce or Cucumber to write some tests. On 1/17/13 1:01 AM, Prasanna Santhanam t...@apache.org wrote: Marvin is a great tool for