We use the solution to help automate our test cases. What we used to do was get manual test cases from the manual testers. They would provide step-by-step descriptions of what application to test and how to launch it, as well as what needs to be tested. The applications were both web-based and Oracle Forms-based. These are the applications that need to be automated in order to be tested. The basic reason why automation was needed was to make this process faster and cheaper. The testers would provide us with test cases, and we would then perform those tests using Java code in a scripting tool. After scripting, we would put them into batch execution mode, or somewhere just from the command line we would trigger them. There was no need of sitting back there and seeing if the test cases were running fine or not. We only focused on the test results in HTML customized reports where we would monitor which test cases had been passed or failed and then we would report those particular test cases.

We use the solution for functional testing. We have scenarios related to Oracle applications where we need to create a purchase order, for example, and we use it for the automation perspective. We use it for regression testing.

We currently have five projects that we are working on. Each project requires ten members. We have approximately 60 people using the solution. The teams are made up of leads, software developers, and engineers. The experience level is anywhere from intermediate to growth level.

I've been using this tool for both government and private projects. It's generally used in organizations that have implemented Oracle applications such as Business Suite or Oracle Fusion because of its forms-based structure. We are users but our partner company in Australia has a partnership with Oracle. I've been an Oracle consultant for 10 years and I'm a test architect. 

We provide this product as a demo solution to clients who are designing, modifying and implementing applications, to allow them to test the install and changes before they are deployed.

We mainly use this solution for clients that are involved with Oracle ERP. There are some customers who have Oracle ERP, and they have some applications that aren't based on Oracle ERP. We use OATS for testing non-Oracle products. For a client that has non-Oracle or non-ERP products, we automate them using OATS.

You don't need to be in Oracle to use the tool. You have options to create types of scripts like web applications, Oracle applications, or EDF applications. 

Oracle has a vast amount of products. They have PeopleSoft, retail, and Fusion, so there are different types of scripts for everything. They give you an option to create different types of scripts. They enable a lot of flexibility for creating scripts for any applications in the market except desktop applications. For any web application, you can use Oracle for automation.

This tool will only work for Oracle EBS, for Oracle ERP financials applications.

We're using this integration with OBIEE. We use these applications for uploading, testing, and for obtaining and understanding how our business intelligence application works. We are golden partners with Oracle and I am a solution architect.

Oracle Application Testing Suite is used for automating.

We use the cloud deployment model for this solution. 

We use OATS for Oracle Forms, for functional testing. It is integrated with several other Oracle products. Sometimes we use it on a daily basis, although it depends on the projects that are being worked on at the time. We also use it for training and development purposes.