One of the most important phases of a development life cycle is the testing phase. To ensure a quality release all the codes developed to build a software have to go through rigorous and extensive testing before releasing a new version.
For each version release of a software product there can be a huge number of test cases to verify and validate the code. These test cases are a part of a test run and will vary from version to version depending on the new release. Now, imagine a situation where a test run has hundreds of test cases and the test run fails because of some errors in the code. It will be a humongous effort to pinpoint the exact test case and the part of the code which caused the error.
This is where the test use case analysis feature of OES helps you to quickly identify why the test run failed. Once you identify the reason for a failed test run it is much easier to figure out the solution. A typical testing tool will show you whether the test run passed or failed but OES will help you to figure out why it failed. What we are trying to do is get the information for each test case and analyze in depth to understand why a test case failed.
In short, there is a famous saying as “trying to find a needle in a haystack”, the test use case analysis makes it possible to find the needle quickly and effectively for better solutions.
Let’s see another benefit of using this feature. Modern software is built using multiple components. Not necessarily each version release will have changes to all the components. For example - A software has 10 components, in V1 all the components were tested. Now in V2 of the software only 4 components out of the 10 has code changes done. The rest are unchanged. So, if a test run fails for V2, OES can specifically provide you with the link of that particular component out of the 4 for which the test case failed along with the link to the source code of that component.
Now that you have the idea about the value addition of the feature, next we will see how to setup and use it.