Forum Discussion

at062084's avatar
at062084
New Contributor
5 years ago

readyapi 3.0 testrunner.sh: Startup sequence

I'm executing a single testcase from a SoapUI project with testrunner.sh using the -s and -c arguments. While the actual soap test request only takes a few ms to complete, testrunner.sh startup and ...
nmrao's avatar
nmrao
Champion Level 3
Just few pointers (may not be a solution)
1. May be new features that are part of booting the might add additional startup time.
2. Open Source tool does not required to check the licensing which is additional in pro tool
3. Change log level to INFO or Error from current DEBUG.
4. Longer startup time, should not affect actual execution time of the tests. Isn't it the case?
at062084's avatar
at062084
New Contributor
5 years ago

Presumably loading of the readyapi 3 load and security modules  (not included in soapui pro) adds to startup time.

-> So question is these modules can be disabled somehow

-> preferred option would be a new feature to pass a list of Projects/Suites/Cases to testrunner.sh

    • at062084's avatar
      at062084
      New Contributor
      5 years ago

      From what i understand:

       

      - The TestEngine curl client needs to have the soapui project file plus any required files packed into a zip, that is created by export from the gui

      --> we've got quit a few projects, so rerunning the export on each update is not really an option

       

      - The TestEngine jenkins plugin allows to specify one project, testsuite and testcase

      --> we need to run TestCases from several/many projects, so not really an option either

       

      What would be more usefull is to have the TestEngine server access the Git repo that holds all the soapui projects, check these out, and then wait for instructions (curl requests) which project/testsuite/testcase to execute.

       

      Our automation setup loops over a list of projects, testsuites and testcases (csv file), calls testrunner for each, creates JUnit style reports,  parses the <TestSuite>-<TestCase>-<TestStep>.*.txt result files for status, response time and error message into a csv file, runs statistical analysis and publishes results to Confluence.