Page tree
Skip to end of metadata
Go to start of metadata

Last updated: Sep 11, 2018 14:48

by Nato Vasilevski

If you don’t have proper reporting results, because your tests get cut in Digital Zoom in small parts and you cannot have a general overview of the whole test in the reporting site, this article is for you.

Please do not forget to hit the “Like” button if you found what you have been searching for. Thank you in advance!

To create this, I have used a priory written scenario where the reporting was marking most of the results as unknown and none of them was marked as failed.



When writing a Protracto-based test, you can create multiple scenarios in a single test as shown on the Protractor official site. What you need to know is that a different it() statement is a different scenario and therefore it gets translated by Digital Zoom as a different test. This is to be seen in the provided example as the provided examples are different equations, that do not continue one after the other, but instead they are observed as different scenarios. If you implement the different it() statements to separate the steps of your test, you might end up in the situation where your test gets represented in Digital Zoom as multiple small tests and therefore you wouldn’t be able to perform an end-to-end observation on the actions you have programmed.

How to solve this?

There are two options on how to solve this:

  1. The first one is to remove the unnecessary it() statements and replace them with comments about the steps, so you can retain visibility.
  2. You can put additional lines that will provide the test with the ability to interpretate and recognize the separate steps. For example:


reportingClient.stepStart(‘x.y.Name-of-your-step’);
<Your Code here>
reportingClient.stepEnd();