Opened 10 years ago
Closed 9 years ago
#11063 closed enhancement (wontfix)
submitting dojox.bdd module
| Reported by: | foobarfighter | Owned by: | Adam Peller |
|---|---|---|---|
| Priority: | high | Milestone: | future |
| Component: | Dojox | Version: | 1.5.0b1 |
| Keywords: | Cc: | Tom Trenka | |
| Blocked By: | Blocking: |
Description
I created a dojox.bdd module for BDD style testing using doh.
The code and README are located here: http://github.com/foobarfighter/dojox/tree/master/bdd/
It's not much code, but it's something that I use a lot when I write tests for doh. The BDD style syntax for defining a test is a little bit nicer for people coming from a ruby background that are used to writing tests in rspec. I found myself including this module in all of my dojo/rails projects because it's less of a context switch for me when I switch from writing server side tests to client side tests.
This code helps me out a lot, so maybe it will help somebody else too. I would like you to consider adding my dojox.bdd project to the dojox project.
Regards, foobarfighter
Change History (4)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
| Cc: | Tom Trenka added |
|---|
would it make sense to offer this as part of doh? should we just offer it on git and hook it up to Dojo xtensions? are there any examples?
comment:3 Changed 10 years ago by
| Milestone: | tbd → future |
|---|
comment:4 Changed 9 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
the git repo is the way to go for 2.0. Need to include package.json and license info, and you can submit a listing to the Dojo package repository.
One last thing... I submitted this ticket http://trac.dojotoolkit.org/ticket/8599 quite a while ago, but now the code is rearranged so that it fits within the dojox.subproject convention. I also added a README. If there is anything else that I need to do in order to get this code into dojox, then let me know.