Want to know which steps are running longer than others in your test? Or which sections of your app may be taking longer to load and test than others? In addition to our step-level Speed Index, you can easily view the relative time it took for each step to complete in a test output with the step timeline feature. Located just above the output logs and screenshot, hover over a specific part of the timeline to view the time each step took. Clicking on a step in the timeline will take you the relative step and screenshot, if there is one, in the logs. You can also zoom in.
When using traditional test automation tools, it may be necessary to add a number of waits to your tests to prevent unnecessary failures. With mabl's dynamic waits built-in to every step, it's often not necessary to add waits to the majority of a test. Waits can also slow down tests considerably by adding a static amount of time to a run. By using the step timeline, you can easily identify waits that may be far longer than what is necessary.
The step timeline not only shows how long each step took to execute but also how long each step took relative to the rest of the steps in the test. This means that if you have a step that took 15 seconds to run and one that took only 7 seconds, the 15-second step will appear a little more than twice as long on the timeline. You can use this to easily identify steps which ran slower than others. These slow running steps will often times be associated with some issue or change that took place during testing, such as a network error detected by mabl or even an autoheal that mabl performed. Click on the specific step in the timeline to be brought straight to that step in the output logs.
Since each step is clearly marked in the timeline, it's easy to view groups of steps that may be running slower than usual. You can check the URL or the section of your app that the group of slow steps are testing to determine what may have contributed to the slow down. Take advantage of the Speed Index as well any network errors detected for that step, depending on your mabl subscription.
Updated over 2 years ago