Greg H. wrote:
Just wondering what the recommended approach would be to carry out ad hoc
testing of one’s application via the web interface, but noting you want to
leverage use of the various test data you have put together in test fixtures
(i.e. used for automated testing).
Would the concept be to use the test environment but run a unit test first
which setup test data in the database via fixtures?
The old-school, pre-TDD technique here is to configure a
development-only mode for the site. I use a CSS class of
‘developmental’, and set it to display:none in production mode.
Then I put a couple extra buttons in the banner that load sample data
and trigger various states.
I can’t use db:fixtures:load anymore because I want my client to enter
data and preserve it between manual tests, and the fixture system
wipes every named table. So I just dumped the database and trimmed it
down to an ugly stack of SQL INSERT statements.
Oh, and my automated tests have the option to hit those buttons, too…
http://c2.com/cgi/wiki?ZeekLand <-- NOT a blog!!