Page History
Table of Contents
Enterprise Designer Role in the Software Development Life Cycle
As more and more teams move towards the Agile methodology in software development, we are getting an increased number of questions like:
“Could Enterprise Test Case Designer still be applied, given iterative nature of requirement generation and uncertainty about the final state of the features?”
...
In this article, we would like to discuss related applicability concerns and dive deeper into the benefits Enterprise Designer could deliver in the Agile environment throughout SDLC.
First, let’s talk about broader Enterprise Designer applicability
While the question posed above is reasonable, Agile vs Waterfall is not the best classification criterium for applying Enterprise applying Test Case Designer. The same is true for dividing the apps into GUI, non-GUI, micro services, etc. – it also does not align well with the Enterprise Designer strengths.
...
It is a test design optimization tool which focuses on the early stages of the testing process and then integrates with tools responsible for the subsequent steps, like Ranorex Studio. Speaking about the reduction of effort, the goal of applying Enterprise Designer is to deal with such challenges of manual test creation as prolonged and error-prone scenario selection, gaps in test data coverage, tedious documentation, and excessive maintenance.
The methodology Enterprise methodology Test Case Designer facilitates is based on the research results about the causes of defects in production. Manually written test cases often represent a very fragmented view of the system, focusing on individual inputs while allowing redundancy or omissions in the remainder of the scenario. On the contrary, Enterprise Designer provides complete control and traceability for each of the steps in the test case.
...
While the question posed above is reasonable, Agile vs Waterfall is not the best classification criterium for applying Enterprise applying Test Case Designer. The same is true for dividing the apps into GUI, non-GUI, micro services, etc. – it also does not align well with the Enterprise Designer strengths.
...
An application with numerous parameters (e.g. >=8) and values may not be a good fit for Enterprise Designer if the interactions between the elements are heavily limited, leaving only a few possible paths through the system.
Enterprise Designer Place in Agile
Next, let us focus more on how applying Enterprise Designer is different in the Agile environment. To have an anchor/benchmark, in the waterfall world, by the time you reach testing, most information is well-defined, so you can start moving through all the traditional Enterprise Designer six steps sequentially.
...
It is also worth noting that sometimes a user story does not look applicable but thinking outside of boundaries will quickly change that assessment. For example, if a user story specifies the ability to log in correctly, it looks like a test with 2 parameters, 1 value each. However, if we look deeper, that requirement means a correct login for different allowed formats for usernames and passwords and an incorrect one for invalid options. Suddenly, thoroughly testing a simple user story can fully leverage Enterprise Designer capabilities.
Enterprise Designer as a Catalyst for BDD
At this point, it is also important to keep in mind the general role of the tool in BDD practices (which often accompany the Agile transformation). When we consider common BDD goals, we can think of these 3 as being important:
...