simpletest

Is there any thoughts about running SimpleTest test cases on current Drupal(6.x) database without creating separate environment for each test?
Some ideas can be found here:
Using a test database with Drupal unit tests: http://patshaughnessy.net/2009/1/16/using-a-test-database-with-drupal-un...
and here:
Using MySQL transactions with Drupal unit tests: http://patshaughnessy.net/2009/1/19/using-mysql-transactions-with-drupal...

Converting Drupal tables from MyISAM to InnoDB to have the possibility to use transactions?

Motivation:
I'm going to grow quality of products we get in company I working in.
I'm going to make ability to show bugs free product when client what. (functionality that marked "done" realy 100% done)
I'm going to make code clear and developement process managing.
I'm going to make regressive testing cheap.
I'm going to remove trivial round things from my live.

CI can help us.

"A Drupal Module Developer's Guide to SimpleTest" - http://www.lullabot.com/articles/drupal-module-developer-guide-simpletest
"An Introduction to Unit Testing in Drupal" - http://www.lullabot.com/articles/introduction-unit-testing

Curioso como esses links me passaram despercebidos ao longo de meses desenvolvendo com Drupal, mas é uma ótima referência para quem já percebeu o valor de se testar as coisas..rsrs

Falando sobre o valor disso, segue um trecho:

"Writing unit tests helps produce higher quality code on many levels.

Arkadaşlar Drupal modülleri ile ilgili 2 sorunum var yardımcı olursanız memnun olurum:

1- Drupal 6.14 içinde Simpletest 6.2.9( http://drupal.org/project/simpletest ) modülünü çalıştıramadım, Modüller listesinde görüyorum ama aktif hale getirmek için checkbox kapalı durumda görünüyor,
* CURL extension for PHP
* DOM extension for PHP. DOM support is included by default in php5.
* Recommended PHP memory limit of 256MB (not exact)
bunlar tamam, hepsi aktif durumda. eksik olan nedir?

Hey all,

Ive been exploring the wonderful Drupal framework for some weeks now, been reading alot about modules, module development and theming. In the last few weeks i have developed some small modules that i want to test using the Simpletest module.
Ive read the documentation and the tutorial to get some sense of how to set up Simpletest for my modules. So i thought i would start by making some functional tests for my custom CCK types. So far i haven't had much luck, ive been wrestling Simpltest for a while now and its not returning the love so far :P

Several core tests (contact, comment, poll) have a need to be to adjust the permissions for anonymous users. We can easily adjust permissions for users by calling drupalCreateUser() with different permissions, but we don't have an easy way to do the same thing for anonymous users. As of now, the tests have to add an admin user with the permission 'administer user permissions' and use drupalPost() to adjust the admin/user/permissions page. This implementation is ugly and wasting effort by duplication.

Since we provide the drupalCreateUser() and drupalCreateRole() methods in DrupalWebTestCase, I proposed adding a drupalSetPermissions() that could be easily reused throughout core tests and would be very handy for a lot of contrib module tests. But it needs more reviews.

I am writing a test for one of my contrib modules that has a feature that is enabled when another contrib module (we'll call it OtherModule) is enabled. I want other people other than myself to be able to run the entire test suite, but what if they didn't have OtherModule installed or even present in their Drupal installation? The test is going to fail spectacularly in that case. So here's what I came up with for my module:

As announced, we've begun the Media Code Sprint to put better media handling into Drupal core!

It's been a great time so far. In the morning, drewish compiled a file function guessing game (free beer!), and andreiashu took the bait and completed the first round with great feedback about how unusable the current state is.

Next, we've sat down and begun writing SimpleTests for the hook_file patch. This has been great fun for me personally; though drewish is an old hand at building tests, this is completely new for me. And to top it off, webchick, Queen of Drupal testing, dropped by our table and got involved!

Even the process of writing tests has been helpful; we found at least one case for validation that had been missed in the original patch, and drewish decided that file_scan_directory needed refactoring. (He's currently chasing other problems as well, and cursing about finding himself going down rabbit holes.)

There's more fun to be had for all! If you want a quick 15 minute task that everyone is qualified to do, go play the File API Function Guessing Game. If you want to do more, then ping me (aaronwinborn), drewish, or dopry at #drupal in IRC, or leave a comment here!

(Cross-posted at AaronWinborn.com.)

We're running SimpleTests on various core modules, to get a baseline of what is fine, and what breaks with the hook_file patch.

I'm going to comment to this thread with results. The first run is on a clean installation of the build of Drupal 7.x-dev, Last updated: July 24, 2008 - 08:03.

Tests to run:

blog api
simpletest
system
upload
user
cache

Now that SimpleTest is apart of Drupal core issues related to the 7.x development have been moved to the core issue queue. If you would like to be involved I have included two links which will filter the issues to only display SimpleTest related issue. You can obviously used the advanced search feature to narrow your results to the SimpleTest related components instead of using the links.