Jelly?
- From: Andy Dingley <dingbat@xxxxxxxxxxxxxx>
- Date: Wed, 27 Feb 2008 08:53:57 -0800 (PST)
Anyone using Jelly? Any experience to impart?
We're looking to move to it, from a background with FitNesse. Our app
is a mix of web app (tech is old JSP tech right through to Facelets)
and also Swing GUI. So far we've built protoypes, now we're moving to
roll it out as our mainstream automatic acceptance testing platform.
I'm particularly excited by how it seems to offer a way for us to do
TDD (Test Driven Development), without the usual restrictions. Most
"hardcore" TDD that I've seen has assumed 1 or 2 person teams
developing a greenfield product. We have a large product, large team,
lots of legacy product already out in the field and a separate QA
team. We simply can't use any approaches like the "Add a single new
test that fails, fix code until the test works" cycle. We must always
maintain the ability to ship product with lots of known bugs still in
effect, as they pass through their fix lifecycle.
I'm wondering about the best way to organise our codebase (in
Subversion) against our Jelly tests (also in Subversion). To maintain
the ability to constantly deliver a product, yet also to be able to
extend the test suite for new bugs or features, I see this as
requiring a continuum of a developing test suite, with Subversion tags
at intervals to mark our "acceptance tests" (must be passed before
shipping product) and "candidate tests" (known to fail, as they
represent the current planned workload to fix). These tags would roll
forward incrementally, one becoming the other as work is completed.
Thanks for any advice or experience you can share
.
- Prev by Date: New Survey Confirms Increased Agile Adoption
- Next by Date: Re: V-model, V&V standard and CMMI
- Previous by thread: New Survey Confirms Increased Agile Adoption
- Next by thread: Test Data
- Index(es):
Relevant Pages
|
