Pre and Post Hooks is a mechanism to implicitly perform test dependent operations at different points of the test initialization and termination. 
Even before your test starts you may need to create and initialize some common resources, connect to your setup etc.
At termination stage both normal and unexpected, you need to release application resources, lab equipment, or logout from communication interfaces.
As well, hooks are necessary for integration with 3rd party integration like HP QC.
 

You can convert any test flow to Sub-Test Case (STC) for multiple re-use by other test cases.

The STC incorporated into your test case flow is presented by Flow Editor as a single step.

The idea is similar to the software sub-routines – all callers use the same copy of the implementation. Any STC update is immediately reflected at all callers.

Take advantage of coordinated parallel testing. To perform parallel actions drug steps into separate Task frames and insert rendezvous conditions.
When your test runs, all Task frames will start at once each as a separate process.
As soon as all parallel flows have completed, the test flow will continue from the rendezvous synchronization point.

It’s a good practice to have all your test steps properly documented. Coronys provides you with a simple built-in HTML Editor that allows you to incorporate pictures, links to files and even video clips.

When you drag test steps to the test flow editor, it optionally incorporates properties “Purpose” and “Description” and into the test flow documentation generated automatically each time you view the test case. Actually this documentation looks like pseudo-code explaining flow conditions, parameters, decisions points etc. This way you can understand the test case logic even though he you did not develop it.