Recent changes to feature-requests

Link on each suite to run that suite only

mark stanton — Tue, 11 Jan 2005 08:40:42 -0000

It would be nice to have a link in each <tr
class="testSuite"> that allows you to just that
particular test suite.

I'll attach modified tests.cfm and htmlui.css as examples.

CFCUnit should use GET not POST

mark stanton — Tue, 11 Jan 2005 08:13:41 -0000

Small, simple change - use GET instead of POST to allow
results to be easily bookmarkable.

http://cfcunit.gruden.int/index.cfm?event=runTest&testClassName=kempstrang.model.tests.AllTests&runnerType=HTML

Making a CFCUnit API

mark stanton — Thu, 06 Jan 2005 02:54:34 -0000

Goal: Creating some method of integrating CFCUnit with
other applications.

An example could be Ant integration, running all the
CFCUnit tests for the project and only deploying if
they succeed. The easiest way I can see of doing this
would be to do a GET task [1] or some Anteater task [2]
on the CFCUnit URL and parse out the results.

Another more complex example would be an Eclipse plugin
(haven't thought this through very well yet) or a Flash
projector file running on the desktop (Paul's idea).

I guess we could approach this using REST or RPC/SOAP
(or both?). To me REST seems like the easiest to
implement & most flexible. SOAP is probably better from
the "play nicely and easily with the MM product suite"
perspective.

Option 1 - (the easy way) HTTP Headers:
If some HTTP headers were added to both the existing
runners it at least allow applications to easy see
whether the we had any failures or errors. For example:

X-CFCUnit-StatusCode: 200
X-CFCUnit-StatusText: Tests run: 31, Failures: 0,
Errors: 0

OR:

X-CFCUnit-StatusCode: 500
X-CFCUnit-StatusText: Tests run: 31, Failures: 4,
Errors: 1

Option 2 - XML Output:
If we also had an XML runner we could go a step further
and provide more verbose output. Maybe RSS or Atom [3]
could be hijacked for the purpose? Maybe there are more
appropriate formats? Regardless the idea would be to
provide full information on each test in each suite.

Option 3 - SOAP Interface:
Provide a simple web service interface such as
cfcunit.runTest(testClassName).

[1] http://ant.apache.org/manual/CoreTasks/get.html
[2] http://aft.sourceforge.net/
[3] http://www.intertwingly.net/wiki/pie/FrontPage

Remote service interface for IDE integration

Paul Kenney — Wed, 10 Nov 2004 05:35:44 -0000

Remote service interface for IDE integration.

Allow display of complex data

Paul Kenney — Wed, 10 Nov 2004 05:31:36 -0000

It would be very helpful if a complex value could be
displayed in the test error message. Perhaps a complex
value could specified in addition to a string failure
message. It could be displayed using cfdump.