The Oracle Application Testing Suite is a legacy suite of tools. Oracle Application Testing Suite 13.1.0.1 shipped in 2017 was the last major release. Since then, two minor releases 13.2.0.1 and 13.3.0.1 were released with only smaller sets of new features.
N/A
Selenium
Score 8.1 out of 10
N/A
Selenium is open source software for browser automation, primarily used for functional, load, or performance testing of applications.
The Oracle Application [Testing Suite] is used heavily in our organization for independent regions to perform Oracle upgrades. Baseline performance can be monitored before the upgrade and compared to a production query load, we are able to easily monitor server performance and make an accurate prediction of upgrade performance. DBA's are able to use the testing suite for ongoing validation of database performance during peak times.
When you have to test the UI and how it behaves when certain actions are performed, you need something that can automate the browsers. This is where Selenium comes to the rescue. If you have to test APIs and not the frontend (UI), I would recommend going with other libraries that support HTTP Requests. Selenium is good only when you have no choice but to run the steps on a browser.
The application is ideal for places that have already contracted with Oracle, however, OATS is much more expensive than other software available on the market.
The setup and configuration for OATS requires a lot of technical expertise and in depth knowledge.
Recognize Adobe Flash and MS Silver Light elements without additional help
Detect and locate Java applets ingredients
Having the "Wait-till-Displayed" or "Wait-till-Present" as a built in Web Driver function instead of requirement for writing loops and defining expliccit wait, visiblewait, invisiblewait, etc.
We love this product mainly because of its high customization abilities and the ease of use. Moreover, its free and can be learned easily through online communities and videos. The tests are more consistent and reliable as compared to Manual tests. It has enabled us to test a large number of features all in one go, which would have impossible through manual tests. The reports generated at the end of the tests are really helpful for the QA and the development teams to get a fair view of the application.
As I mentioned earlier, the reason I use Selenium is because there is a fairly widespread community of users, and user support services are at a good level. because the application is open source, it works on many platforms (Windows, Linux, IOS) without any problems. In addition, it gives us a lot of options for writing functional tests. For errors that we receive through the application, we can easily find the reasons for errors in the forums.
Selenium does not have technical support available easily. You have to go through forums to get the information you need. However, there are excellent forums out there that make it easy to troubleshoot. The open-source flexibility makes it difficult to have dedicated support.
We did everything we needed to use it. Now we can execute our tests on different operational systems and browsers running few tests simultaneously. We also implemented Appium framework to execute our tests on mobile devices, such as iPhones, iPads, Android phones and tablets. We use SauceLabs for our test execution and Jenkins for continuous integration.
We buy all things ORACLE in order to have a consistent experience and reduce the training and learning curve. We believe in ORACLE Corporation's commitment to quality and innovation and would not consider any other products. We are a large company and saving a few dollars on licensing is penny wise but pound foolish as we cannot afford unplanned downtime.
At the time of adoption, there were not many other alternatives that were even close to being competitive when it comes to browser testing. As far as I know now to this day, there is still little competition to Selenium for what it does. Any other browser-based testing still utilises Selenium to interact with the browser.
Oracle testing suite had a positive ROI immediately, as our web application downtimes were reduced dramatically after we could do automated regression and load testing.
The learning curve for OpenScript was steep for our team, and we had to spend a lot of work hours training staff and learning the product.
After users were trained properly, we were able to leverage the benefits of the suite immediately.
Generation of detailed finding reports helped in cost savings in regard to direct labor.
Quality Assurance technicians found value in repeating mundane duties that they perform daily. It saved mental energy due to the automation process.
The value was established in high volume usage in setting up meetings as well as new accounts with A/B testing. Also merely cleaning up old test documents by evaluating them and organization or deletion.
