rutema version 0.7.0 has been released!
rutema is a test execution tool with a twist.
It allows you to combine test tools while it takes care of logging,
reporting, archiving of results and formalizes execution of automated
and manual tests.
It’s purpose is to make testing in heterogeneous environments easier.
For more information look at http://patir.rubyforge.org/rutema
- Unified test execution environment for automated and manual tests
- Extensible reports and notifications in various formats (email, rss,
pdf, html etc.)
- Web frontend and command line report generation tools for browsing the
test results database
- Comprehensive history of test execution
- A well defined way to create a project specific test specification
See http://patir.rubyforge.org/rutema/distro_test.html for an
- patir (http://patir.rubyforge.org)
- mailfactory (http://rubyforge.org/projects/mailfactory/)
- activerecord (http://ar.rubyonrails.com/)
- sqlite3 (http://rubyforge.org/projects/sqlite-ruby/)
- ramaze (http://www.ramaze.net/)
- ruport (http://rubyreports.org/)
- gem install rutema
- Support for tools, paths and context information in the configuration
- Changes in the configuration for Historian and ActiveRecordReporter.
Check the distro_test samples
- database connection code consolidated in db.rb
- Added support for jdbc/h2 to work with jRuby
- AR-reporter configuration expanded to support different adapters.
Consistent with the Historian db configuration
- rutema unit tests now run under jRuby
- rutemah runs under jRuby
- Updated rutemaweb controller to work with ramaze 0.3.9.1
- Bugfix: duration SQL type adjusted in the model to return proper
- Bugfix: name=step_type for TestStep so that name is assigned a value
in the model step
- Locked the Ramaze version to 0.3.5 until we find out why the new
version breaks us
- Bugfix: specifying a .spec filename on the commandline did not work -
Path expanded before changing directory.
- Bugfix: running an attended .spec on it’s own was not possible -
attended mode is now set for single runs.
- Cleaned up the Runner’s log output
- Parsers derived from Rutema::SpecificationParser now receive the
system configuration so that conventions like tools, paths and context
can be used in element_ methods (this functionality fell through the
cracks with the change in parser implementation)
- rutemaweb now has proper commandline help and connects properly to the
- ExtensibleXMLParser made more tolerant (no exceptions when an element
cannot be handled)
- Bug: Typo in the class name used in the exceptions fixed
- Bugfix: ActiveRecord connection throws an exception that prevented
Historian from establishing a new one. Fixed
- More unit tests
- Added Rutema::ExtensibleXMLParser - this parser simplifies parser
creation immensely. Check the documentation for details
- “Howto create a parser v0.5.0” officially the fastest deprecation of a
document ever. http://patir.rubyforge.org/rutema/parser.html is the new
- Corrected some english spelling mistakes (hey, we’re not native
- Fixed an issue with AR cached connections that interfered with unit