Testopia:Documentation

Back to Testopia

User's Manual

The main document is at http://landfill.mozilla.org/testopia/testopia/doc/Manual.pdf

Import Documentation is here on the wiki at Testopia:Documentation:XMLInput

XMLRPC API Documentation is here on the wiki at Testopia:Documentation:XMLRPC

The readme is at Testopia:README

Release Notes for 1.1

• Added support for Environments. A complete user defined tree of environment attributes can now be difined.
• Environments can now be added to individual case-runs
• Added filtering of case-runs in the run view and test cases when creating new runs and adding cases to existing runs.
• Added environment search
• XML import is now available for test cases and plans
• A webservice is now available for searching and updating cases, runs, plans, and case-runs. Uses SOAP::Lite and extends Bugzilla's webservice interface.
• Updates to database include new fields for tracking setup and breakdown steps in test cases.
• New install script updates existing 1.0 databases (not Testrunner 0.7 unfortunately)
• Numerous bug fixes

Release Notes for 1.0

• Almost a complete rewrite of the Testrunner code base.
• Foundational release. This includes basic support for creating, editing and searching for test cases, test runs, test plans etc.
• Powerful search capabilities based on Bugzilla's search engine.
• Better support for cloning of objects
• Added sortable, paged tables to search results.
• Tag based classification on test cases, runs, and plans.
• Web 2.0 enabled, using the Dojo toolkit and Ajax for a more seamless user experience.
• Ability to track builds with test runs.
• Support for test case dependencies.
• Support for attachments to test cases and test plans.
• Full history of changes on cases, plans, and runs as well as status of case runs.
• Ability to update multiple objects at once.
• Added numerous fields and normalized database.
• Moved UI into templates

Known Bugs

• Clicking the back button on a test case or a test plan causes changes in WYSIWYG editors to be lost. Happens with Internet Explorer and Firefox -- probably other browsers also.
• Adding and removing components produces a javascript error in Internet Explorer. Works fine in Firefox.