gaelyk/gaelyk-spock

A spock plugin for the Gaelyk framework

Welcome to the Gaelyk project infrastructure


Gaelyk is a lightweight toolkit for developing applications in Groovy for the Google App Engine environment.

You can learn more about the project by going to the project website.

In particular, you'll quickly get started by reading the tutorial.

And downloading the latest version of the toolkit.

If you wish to discuss or contribute, please fill free to join us on the Gaelyk Google Group.

Gaelyk is hosted at GitHub:

• Sources
• Issue tracker

gaelyk-spock's Issues

missing response and out variables in groovlets under test

in tested groovlets, there should be out and response variables available by default

let user pick which appengine API will be used

setting full appengine stack like datastore is pretty inefficient. user should be able to specify which features will be enabled in setup method.

def setup(){
   enable 'datastore', 'memcache'
}

ConventionalGaelykUnitSpec should check package declaration as well

ConventionalGaelykUnitSpec checks only if groovlet is in proper location e.g. same/package/groovlet.groovy but sould also check if the groovlet declares the package e.g. package same.package

GaelykUnitSpec expects the groovlet is in default package

If you create a new gaelyk unit spec it creates a new variable with the same name as the script. but if the script is in the package the name will be something like 'tasks/doIt' which is note useful. The right name should be just 'doIt'.

Resolve groovlet by convention

There is no need to force users to always specify the path to the groovlet. The default groovlet name should always be the name of the spec w/o the spec suffix and with the lowercased first letter. If the spec is in the package the groovlet should reside also in the same package.

For example

tasks.DoItSpec

class will be by default testing following groovlet

tasks/doIt.groovy

let user pick which appengine API will be used

currently no plugins are enabled in groovlets specs. there should be easy way how to enable them.

testing routes defined in plugins

related to #9

routes defined by plugin should be easy testable as well as these defined in routes.groovy

testing support for plugins

there should be easy way how to test created plugins.