Test cases » History » Version 4

« Previous - Version 4/20 (diff) - Next » - Current version
Max Milbers, 04/22/2011 07:47 PM

Test cases

System Requirements:

It is useful to test virtuemart installed in a subdirectory of your http directory. For exampel localhost/vm2. This is for testing if the pathing is working correct.

Use joomla 1.5 or 1.6 (latest)

As tester you should have installed your joomla with a custom prefix (not jos_) this quite important to find tables with hardcoded prefix.

Use different browsers. Virtuemart should work without glitches at least on IE8, FF, chrome, safari and opera.


Test installer with and without sampel data.
Test the All-in-one Modules and Plugin installer.


Test the frontend with java script enabled and disabled.
Test what happens, when you change the post data. For exampel when you remove it, or enter a product which is not published.
Test the frontend as anoymous and registered shopper.

Backend Testing

The relative url /administrator/index.php?option=com_virtuemart&view=config means that it points to the Backend (/administrator) and that it points on the view named config.

Most backend views have a "list view" and an "edit view"

list views have always the buttons: New, Edit, Publish, Unpublish, Delete
New => create new item
publish/unpublish => make selected items accessible (or not) from frontend
delete => delete selected items

Every edit view in the backend has the buttons apply, save and close.
Apply => store the data and show the same view and same item
Save => store the data and show the reagarding listing view
Cancel => just show the regarding listing view

Backend configuration

Test shop configuration (view=config)

Test currencies (view=currency)

Test Payment Methods (view=paymentmethod)

Test Credit Card List (view=creditcard)

Test Shipper (view=shippingcarrier)

Test Shipping Rates (view=shippingrate)

Test Countries (view=country)

Test userfields (view=userfields)

Test order status (view=orderstatus)