diff --git a/pages/user-guide/post-install-healthchecks.rst b/pages/user-guide/post-install-healthchecks.rst
index 2c287d3..3b395bd 100644
--- a/pages/user-guide/post-install-healthchecks.rst
+++ b/pages/user-guide/post-install-healthchecks.rst
@@ -262,6 +262,23 @@ To prepare Murano for testing:
 
 Murano is ready for testing.
 
+Preparing Heat for Testing
++++++++++++++++++++++++++++
+
+The platform tests are run in the tenant you've specified in
+'OpenStack Settings' tab during OpenStack installation. By default that is
+'admin' tenant. Perform in that tenant the following actions to prepare Heat
+for testing of its autoscaling feature:
+
+1. Download the following image of Linux Fedora with pre-installed
+   cloud-init and heat-cfntools packages:
+
+http://fedorapeople.org/groups/heat/prebuilt-jeos-images/F17-x86_64-cfntools.qcow2
+2. Then upload the image into OpenStack Image Service (Glance) into
+     'admin' tenant and name it 'F17-x86_64-cfntools'.
+
+Now Heat autoscaling is ready for testing.
+
 Platform Tests Details
 ++++++++++++++++++++++
 
@@ -290,21 +307,71 @@ Platform Tests Details
   For more information, see:
   `Savanna documentation <http://savanna.readthedocs.org/en/0.2.2/>`_ 
 
-.. topic:: Create stack, check its details, then update and delete stack
+.. topic:: Typical stack actions: create, update, delete, show details, etc
+
+  The test verifies that the Heat service can create, update and delete a stack
+  and show details of the stack and its resources, events and template.
+
+  Target component: Heat
+
+  Scenario:
+
+  1. Create a stack.
+  2. Wait for the stack status to change to 'CREATE_COMPLETE'.
+  3. Get the details of the created stack by its name.
+  4. Get the resources list of the created stack.
+  5. Get the details of the stack resource.
+  6. Get the events list of the created stack.
+  7. Get the details of the stack event.
+  8. Update the stack.
+  9. Wait for the stack to update.
+  10. Get the stack template details.
+  11. Get the resources list of the updated stack.
+  12. Delete the stack.
+  13. Wait for the stack to be deleted.
+
+.. topic:: Check stack autoscaling
+
+  The test verifies that the Heat service can scale the stack capacity
+  up and down automatically according to the current conditions.
+
+  Target component: Heat
+
+  Scenario:
 
-  The test verifies that the Heat service can create, launch, and delete a stack.
+  1. Image with cfntools package should be imported.
+  2. Create a flavor.
+  3. Create a keypair.
+  4. Save generated private key to file on Controller node.
+  5. Create a security group.
+  6. Create a stack.
+  7. Wait for the stack status to change to 'CREATE_COMPLETE'.
+  8. Create a floating ip.
+  9. Assign the floating ip to the instance of the stack.
+  10. Wait for cloud_init procedure to be completed on the instance.
+  11. Load the instance CPU to initiate the stack scaling up.
+  12. Wait for the 2nd instance to be launched.
+  13. Release the instance CPU to initiate the stack scaling down.
+  14. Wait for the 2nd instance to be terminated.
+  15. Delete the file with private key.
+  16. Delete the stack.
+  17. Wait for the stack to be deleted.
+
+.. topic:: Check stack rollback
+
+  The test verifies that the Heat service can rollback the stack
+  if its creation failed.
 
   Target component: Heat
 
   Scenario:
 
-  1. Create stack.
-  2. Wait for stack status to become 'CREATE_COMPLETE'.
-  3. Get details of the created stack by its name.
-  4. Update stack.
-  5. Wait for stack to be updated.
-  6. Delete stack.
-  7. Wait for stack to be deleted.
+  1. Start stack creation with rollback enabled.
+  2. Verify the stack appears with status 'CREATE_IN_PROGRESS'.
+  3. Wait for the stack to be deleted in result of rollback after
+     expiration of timeout defined in WaitHandle resource
+     of the stack.
+  4. Verify the instance of the stack has been deleted.
 
 .. topic:: Murano environment with AD service deployment