We get a lot of questions related to OATS. A recent question was “Can OATS scripts run in the background to avoid manual intervention?” Our Testing Consultant, Sai Prabha answered the question in the following blogpost where she talks about testing, scheduling tests in OATS and running scripts in OTM.
Testing and its Importance
Testing helps us identify the root cause errors and helps us prevent them. Testing also helps in finding defects and bugs before the system gets in to production and goes live. But does testing provide us processes and control procedures to control bugs? Absolutely! Not only does testing help identify bugs but also goes into finding the root cause so that it can be minimized.
In any generic functional testing, when we automate a script, we view the application running at the time of script execution. This let’s us see the current screens and also the point at which the scenario failed (if a failure occurs). OATS (Oracle Application testing Suite) has a special feature where testing execution provides the ability to create test sets, specify which tests to run and execute tests at a scheduled date and time with minimal human effort. How does one do it? We have the answers!
Scheduling Tests in OATS
Oracle Application testing Suite (OATS) has three components.
- Oracle Openscript
- Oracle Load testing (OLT)
- Oracle Test manager (OTM)
The scheduling tests feature in Oracle Test Manager (OTM) in OATS highlights how to run scripts on the server in the background at a scheduled future date & time with minimal effort.
We can schedule Oracle Open Script tests to run once on a specified day and time or daily at a specified time, or weekly at a specified day and time by listing the tasks that are scheduled for the displayed week. Any of the options can be selected by giving appropriate parameters. After the schedule is executed in Scheduling Tests, there is a feature called Send Report To, which gathers the email addresses of the people that the report can be sent to.
Running scripts in OTM
The scripts developed in Openscript are then imported in OTM, where we can run the OATS (Openscript) scripts from the web browser in OTM collaboratively. We can also submit the OATS scripts on the server in the background and continue to work and check for the results after the script execution completes.
In both OTM and OLT, we can and play the scripts in the background to avoid manual intervention. When we run a test, we can specify the workstation to run it on and playback the desired scripts.
That’s how we can run scripts in OATS without manual intervention. If you have any other questions related to testing, email us at email@example.com.
You can also request for a 20% Discount on a 1 Week Qa Strategy Assessment* where you can get your testing and QA strategy assessed with ITC experts who will:
- Establish a QA Road Map
- Provide Best Practices Recommendation
- Present an Assessment Report
*Offer valid only up to 15th May, 2015. Visit www.itconvergence.com/qa-assessment