[development] DAST - What tests would you like to see
victorkane at gmail.com
Sun Jul 29 09:50:08 UTC 2007
I am preparing an installation profile release of my Project Flow and
Tracker (which is a Drupal based document wiki disciplined around the agile
approach to software development) before the start of DrupalCon Barcelona.
So I will definitely use DAST to make a script to build it (as described in
your project page).
I am wondering if DAST could provide the glue to link my project iterations,
user stories, tasks and acceptance tests with SVN (or CVS) commits, which is
part of my roadmap.
I will have to wait until actually trying out DAST, because it is not clear
to me once the site is built how the cli-run DAST could be run from inside
of Drupal (I suppose in the same way as update.php, import scripts, etc) and
whether that would respect administrative permissions in some way. What I am
wondering is whether DAST could help with importing configuration (would
that be a straight database import?) and such things as importing CCK fields
and views. I suppose the running of an SQL dump would be one simple way, but
I would be interested in something more granular.
As an Ant enthusiast, the use of Phing and its emergence in the Drupal world
is very exciting to say the least.
Lastly, I would second what Dries says about automated aspects of testing.
It occurs to me that checking the files directory against a manifest (list
of files) would be interesting, since multimedia files are sometimes left
out of version control on some application installs, since they are often
created and deleted by users who would have no access to version control. A
phing task to create a manifest of files and the appropriate permissions,
and then check an installed site against that manifest (maybe even download
them maven-like from a centralized repository in the same way you are
working with modules) could be interesting for production sites.
On 7/28/07, Allister Beharry <allister.beharry at gmail.com> wrote:
> The 0.2 DAST release is going to feature automatic code testing using
> SimpleTest. The goal of this feature is to create a repeatable process
> for verifying code behaviour. A batch of unit tests can be run against
> against core HEAD, or core HEAD + module or core HEAD + module + patch
> or any Revision + module + patch...In addition to the 11 tests that
> ship with the simpletest module, I've been perusing the issue queue
> and picking out several patches, as well as some basic db tests for
> the current MSSQL and Oracle drivers. If you're an issue owner or a
> module maintainer, what tests would you like to see? Think of the
> tests you now do manually - what test do you wish could be automated?
> While you're at it, check out the project at
> http://www.drupal.org/project/DAST if you haven't yet - I'd love to
> get some feedback on it.
> Muppet Show > Monty Python
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development