Baseline models for existing SUT quickly
- P Tejaswi Hebbar
- Suhas Deshpande
For an ongoing project/release/sprint, the changes to the model will take lesser time compared to writing new or, even identifying and updating existing manual test cases. This is the core advantage of Creator. However, this is with the assumption that baseline models (ie., models that are equivalent to existing production version of the application) exist.
Creating a model for the System Under Test (SUT) for the very first time - when the SUT exists in production -has been done by teams manually till now, thereby increasing the overall project timelines and additional cost incurred. This also means longer time period to start showcasing ROI.
Recommendation: With Creator 4.6.0, we have introduced a new utility “Import Web Page Scan”, where each web page/screen can be scanned, and all web page objects be captured with a single mouse click. The process can be repeated in a single go to scan the entire SUT and Structure Diagrams be created in a matter of hours. |
In the backend, we scan the DOM of the web page.
See https://youtu.be/5j1vAiUU1Ew for demonstration of this new utility.
Recommendation: For Activity Diagrams, model and baseline only those flows that are impacted by the next immediate project/release/sprint. Enhance the model as and when needed in the future. |
The utility also identifies and saves the Object Locator information into Creator, thus helping to avoid additional task of manually doing the same on per web page object basis. See section “Achieve Scriptless Automation with Creator” for more information on how this utility can positively impact the overall process.
With Creator 4.6.2, user can now configure to customize and fine-tune the SD creation process for existing applications based on their teams' needs: Please Seehttps://youtu.be/zvHdgmcLycs for demonstration of related features.
Related content
Copyright © 2023 Conformiq and its subsidiaries. All rights reserved.