Instead they’ll be taken to the exact breakpoint at the step level, reducing the time required to review user paths and resolve errors. Should an issue occur or an application change requires a script update, users can avoid playing back the entire user path. Errors can then be addressed from directly within the Step Debug window via the “fix parameters” option, or users can choose to “skip this action” and resume playback, or “stop checking” to halt the playback. There they’ll be able to access our Step Debug window, where the error is displayed along with remediation prompts and relevant options to ensure that appropriate objects are being targeted. Now, as playback occurs, users can be taken directly to error points at the step level. We designed our new Step Debug feature to help users become more autonomous in their ability to handle errors after recording. This includes a new Step Debug feature for simplified recording error identification and remediation, as well as features to help improve the overall recording experience for users creating RealBrowser tests. RealBrowser enhancementsĪs we continue to build on our initial release of RealBrowser, NeoLoad 9.2 brings additional enhancements focused on ease of use and a streamlined user experience. This release delivers several important features, including enhancements to RealBrowser (see the NeoLoad 9.0 release blog for more information on RealBrowser) as well as integrations with opensource performance testing tools like JMeter and Gatling. We are excited to announce the release of NeoLoad 9.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |