Plan for Functional Testing

Warning: Input from the XWiki developers and users would be greatly appreciated. Which are the features you think that should receive the most care, or which are the test cases which we should not leave out?

Catalin: I personally think that for the beginning we should focus on core functionality, and especially on the basic features that are very important for end-users but the developers tend to overlook when testing, like the WYSIWYG editor.

Basic Features

The basic features are also specified by the User's Guide

Advanced Features

  • Document Templates & Forms
  • Creating and changing classes
    • Adding a new property (tests for each type)
    • changing a property
    • removing a property (not yet implemented)
    • Testing the new class by creating an object
  • Internationalization
  • Tags
  • Printing - seems very hard to test (if possible at all)
The advanced features are specified by the User's Guide

Administration Features

The administration features are specified by the Administrator's Guide

Developers' Features

XMLRPC API

Even if not related to the Selenium tests, the amount of bugs present in the XMLRPC Interface justifies giving this high priority.

Version 1.58 last modified by Sergiu on 12/12/2007 at 13:46

Comments 0

No comments for this document

Attachments 0

No attachments for this document

Creator: hritcu on 2007/06/08 11:10
This wiki is licensed under a Creative Commons license
1.5.2.12758