3 simple configuration steps to view test execution triggered by Oracle Test Manager

Like Tweet Pin it Share Share Email

Assuming that you are aware of triggering OATS test automation script execution in Oracle Test Manager, in a specific associated system. The system which you might have added @  Oracle Test Manager’s Tools>Systems menu => Add option.

In the initial stages of building the scripts and want to make sure that everything is working fine, i.e. a dry run, you would surely want to view the entire execution once especially when a new system is added or if OTM is freshly configured for the test automation project.

So now, lets see the 3 simple configuration steps that you need to perform


  1. Stop OATS Agent Service in the system where you want to view the script execution.
  2. Run the Agent Service Command in Command Prompt
  3. Logout & Login out of  Oracle Test Manager

Lets see how to perform each of the above and trigger the execution.

1. Stop OATS Agent Service in the system where you want to view the script execution.

  • Open windows run command window & type “services.msc” and press enter.
  • Search for “Oracle ATS Agent” select “Stop” option in the context menu(right click) and wait till the service is stopped completely.

2. Run the Agent Service Command in Command Prompt

  • Open Command Prompt and execute below command

  • Wait for the service to start completely.

3. Finally Logout and Login Oracle Test Manager

Now you need to navigate to tests tab and trigger execution of the desired script by selecting the machine in which above configurations are available.

By doing above mentioned steps, you are telling OATS that do not start any interactive desktop ( where the execution is triggered by default ) option but trigger the execution directly in the machine / system it self.

Please do revert to us in case of any queries through the comments, we would be more than happy to help.

Comments (4)

  • Hi Srinivas,
    I am following the steps and able to run the scripts from OTM. While execution, i have to pass command line settings and passing the settings while individual script execution and working fine.

    While executing the batch mode, for ex: If i select more than 1 test case for execution and provide the cmd line run settings, then its not working. Getting relative to repository path not found error.

    cmd line using: -env_file_path “EAS\Env File\Default Env XML\ENV_XML.xml”
    my env file is in location: C:\EASAutomation\Regression Scripts\EAS\Env File\Default Env XML\ENV_XML.xml

    Repo added: C:\EASAutomation\Regression Scripts

    • Author

      Are you running scripts in multiple machines or only in single machine?
      IF you are running the scripts in multiple machines, please make sure that each machine has the Repository created.

      Now if you want to use settings from external file, can you please try with this option

      -propertiesPath “C:/settings.properties”

      the properties file should contain (name=value) pairs and also try by giving full path and not the relative path.
      Kindly let us know if this had worked or not?

  • i am running the scripts from one machine only and selecting 10 test scripts from OTM.
    Other thing, we are using XML and in the script, we are reading from the XMl. If we need to use the properties, we need to change the complete framework/ function to read the properties from the config.

    • Author

      Can you share with me the content of XML, want to understand what exactly you are dealing with?


Leave a Reply

Your email address will not be published. Required fields are marked *