Bricks are introduced to Molybdenum with release 0.7.0.
Bricks are sniplets you can reuse in several testsuites. This will avoid duplication of command sequences over testsuites and can lead to simpler to read tests.
Such a duplication will lead to hardly to maintain tests - if a command has changed, the change has to be made in several places.
With bricks, the change has to be made in one place only - in the brick itself.
Bricks can be paramterized.
Bricks are stored in a repository, which can be shared between testsuites.
If you are a nontechnician computer user, you could see bricks as macros to simplify recurring tasks.
If you are a programmer/developer, you could see bricks as functions/methods and introducing bricks in already existing testsuites is a kind of refactoring
If you are a tester you'll find bricks similar to concepts like keyword based testing or action based testing.
Bricks in the feature report of version 0.7.0 ...
