Bricks

A brick consists of a sequence of commands which is intended to be reused in different tests and testsuites.
Bricks are stored in a repository independently from the testsuite.
If a brick is inserted in a testsuite, its just a reference to the sequence of commands inside the brick. So each change on commands in a brick will propagated to all references of that brick automatically.
Bricks can be parameterized.

Extract a brick from existing testcases

Select a continuous sequence of commands inside one test, press Ctrl+Shift*M or choose Extract brick... from context menu , pass a name for the new brick --> a brick will be created and will replace the selected commands

Add a brick to the repository

Select the Brick Repository tab, press Ctrl+Shift+Insert, create a new brick.

Add commands the same way as for tests in a testsuite.

Add an existing brick to a test

Press Ctrl*Shift*Insert inside the Testsuite tab, choose a brick from the list

Saving a brick repository for testsuites

If a testsuite with a repository was newly created, Molybdenum will ask for saving both and will link them together.

Molybdenum tries to hold the link as a relative path, for repositories linked with relative path, the repository can be loaded independently from the place an protocol the suite is loaded again.

Linking to an existing brick repository

Save your testsuite if not already done, goto Edit-->Script Properties..., choose a repository you want to use.

Parameterize Bricks

Use @{<name>} constructs as you would use ${<name>} in normal tests. each <name> will appear in the Add Brick dialog to be filled while adding a birck to a suite.

Bricks in the report

Bricks are shown in the report.

Usability

Messages are immediately shown in its own panel now - no need to open a dialog to see the message.

Recently used autostart argumets are shown in a completion box

Confirm dialog on exit has a Save button now

Test Window will be focused before starting a testrun

Report will be opened in a tab after saving the report automatically

Report has buttons to immediately rerun a suite

Cursor will be placed more intuitive after remove and insert operations

Stopping on a breakpoint will bring the cursor just before the breakpoint to allow seamless recording

Multiselection for Extract Brick..., Copy, Cut, Remove and new paste commands

Paste Flat

Paste selected nodes without container inside a container.
Copy selection:

Paste flat:

Result:

Explanation:

Paste

Paste selected nodes with its container after the selected container.
Copy selection:

Paste:

Result:

Explanation:

Failures will have linked screenshots too, additionally to Errors. The whole scroll area will be shown

Screenshot command

new command captureScreenshot. The whole scroll area will be captured as for Errors and Failures. The screenshot will be linked in the report.

Console logging

If Molybdenum is started via commandline, the output of the Firefox Error Console can be redirected to the console and therefore written to a log file.
Additionally, include and exclude patterns can be applied.