hisaak
Occasional Contributor
Joined 16 years ago
User Profile
User Widgets
Contributions
Re: Testrunner doesn't export result for failed JDBC DataSource
Ok, I understand your point. As a workaround, your suggestion might work and the implementation is quite easy. However, I plan to train some "not so skilled" testers to work with soapUI on their own so they can create simple TestCases without any coding. And I think it wouldn't be much intuitive for them to use special TearDown script for TestCases including JDBC and not use any script for the rest of TestCases. This is the main reason why I'd like to use JDBC data sources just like any other data sources we use (CSV, Excel). Let's call it convenience or uniformity. Regards, hisaak1.7KViews0likes0CommentsRe: Testrunner doesn't export result for failed JDBC DataSource
SmartBear Support wrote: Hi! ok, thanks for this - the problem is that the runner outputs files for failed TestSteps but your TestCase fails before running any steps at all (it fails during initialization) No, that's not the case. JDBC connect is within the first step of the TestCase so I expect it to throw some FAILED output file when it fails. Just compare it to File based Data Source. When I replace JDBC step by File data source step and the file is not found, then I get FAILED file in output for this TestCase step. And that's what I want for database based data source as well.1.7KViews0likes0CommentsRe: Testrunner doesn't export result for failed JDBC DataSource
do you get any errors in the console output of the test when this teststep executes? Yes, i do. The error output in the test console is just fine as you can see in attached output.txt. I got this file from this command: $ /opt/soapui-pro-4.0.1/bin/testrunner.sh -F HTML -R 'TestSuite Report' -Pdatabase=my_oracle_database -Penvironment=my_environment -I -a -s 'TestSuite - CheckLogin' -f output -r CheckLoginWS-soapui-project.xml > output.txt 2>&1 $ ls output TestSuite--CheckLogin TestSuite__CheckLogin-TestCase__Existing_userName_file-checkUserName__existing_userName-0-OK.txt TestSuite__CheckLogin-TestCase__Existing_userName_file-DataSource__CUID_userName_file-0-OK.txt TestSuite__CheckLogin-TestCase__Incorrect_userName-checkUserName__spaces-0-OK.txt TestSuite__CheckLogin-TestCase__Incorrect_userName-DataSource__CUID-0-OK.txt TestSuite__CheckLogin-TestCase__New_userName-checkUserName__new_userName-0-OK.txt TestSuite__CheckLogin-TestCase__New_userName-DataSource__CUID_file-0-OK.txt As you can see there are only "OK" files under output directory. I also checked soapui.log and soapui-errors.log files and there is nothing interesting at first glance. Anyway, if you want I can attach them as well. Hope that helps ...1.7KViews0likes0CommentsTestrunner doesn't export result for failed JDBC DataSource
I use -a -A -I options with testrunner.sh to run a test suite with multiple test cases. These options should advise testrunner.sh to write results for all test steps into the separate files. However, when DataSource step of JDBC type fails somewhere in the middle of a test suite, it doesn't write any file for the whole test case. Such a test case is correctly marked as failed in the final short summary (-r) and also test suite report contains appropriate error message. So the only one problem lies in missing test case results. This is a serious issue for me since I detect failure (within Jenkins job) for whole test suite by looking for files ending with "FAILED.txt". If someone wants to replicate the issue, it just takes to set wrong credentials for database connection. In my case, I get the following error from Oracle database: java.sql.SQLException: ORA-01017: invalid username/password; logon denied. Any help is appreciated. soapUI Pro 4.0.1 on Fedora Linux x86_648.3KViews0likes12CommentsRe: JDBC DataSource charset problem
I exported 3 db records to a file. This file is attached. I've also tried to use File DataSource and read this file. This way there is no problem with charset. Only direct database access makes troubles. David System Properties: GRE_HOME=/opt/soapui/xulrunner-linux apple.laf.useScreenMenuBar=true com.apple.mrj.application.apple.menu.about.name=SoapUI file.encoding=UTF-8 file.encoding.pkg=sun.io file.separator=/ groovy.source.encoding=iso-8859-1 java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment java.awt.printerjob=sun.print.PSPrinterJob java.class.path=/opt/soapui/bin/soapui-pro-3.0.1.jar:/opt/soapui/lib/activation-1.1.jar:/opt/soapui/lib/javamail-1.4.jar:/opt/soapui/lib/wsdl4j-1.6.2-fixed.jar:/opt/soapui/lib/junit-4.4.jar:/opt/soapui/lib/log4j-1.2.14.jar:/opt/soapui/lib/opencsv-1.8.jar:/opt/soapui/lib/rsyntaxtextarea-1.3.4.jar:/opt/soapui/lib/looks-2.2.0.jar:/opt/soapui/lib/binding-2.0.1.jar:/opt/soapui/lib/forms-1.0.7.jar:/opt/soapui/lib/jcalendar-1.3.2.jar:/opt/soapui/lib/commons-logging-1.1.1.jar:/opt/soapui/lib/commons-collections-3.2.1.jar:/opt/soapui/lib/commons-lang-2.4.jar:/opt/soapui/lib/commons-io-1.3.2.jar:/opt/soapui/lib/not-yet-commons-ssl-0.3.10.jar:/opt/soapui/lib/commons-cli-1.0.jar:/opt/soapui/lib/commons-beanutils-1.7.0.jar:/opt/soapui/lib/commons-httpclient-3.1.jar:/opt/soapui/lib/json-lib-2.2.2-jdk15.jar:/opt/soapui/lib/ezmorph-1.0.5.jar:/opt/soapui/lib/xom-1.1.jar:/opt/soapui/lib/swingx-soapui.jar:/opt/soapui/lib/l2fprod-common-fontchooser-7.3.jar:/opt/soapui/lib/l2fprod-common-directorychooser-7.3.jar:/opt/soapui/lib/commons-codec-1.3.jar:/opt/soapui/lib/groovy-all-1.6.4.jar:/opt/soapui/lib/js-1.7R2.jar:/opt/soapui/lib/jetty-6.1.15.jar:/opt/soapui/lib/jetty-util-6.1.15.jar:/opt/soapui/lib/servlet-api-2.5-20081211.jar:/opt/soapui/lib/jxl-2.6.10.jar:/opt/soapui/lib/idw-1.5.0.jar:/opt/soapui/lib/xbean-fixed-2.4.0.jar:/opt/soapui/lib/xbean_xpath-2.4.0.jar:/opt/soapui/lib/xmlpublic-2.4.0.jar:/opt/soapui/lib/jsr173_1.0_api-xmlbeans-2.4.0.jar:/opt/soapui/lib/soapui-3.0.1.jar:/opt/soapui/lib/soapui-xmlbeans-3.0.1.jar:/opt/soapui/lib/soapui-coverage-xmlbeans-3.0.1.jar:/opt/soapui/lib/license4j-1.3.jar:/opt/soapui/lib/ext-xmlbeans-1.1.jar:/opt/soapui/lib/policy-xmlbeans-1.5.jar:/opt/soapui/lib/soap-xmlbeans-1.2.jar:/opt/soapui/lib/wadl-xmlbeans-1.1.jar:/opt/soapui/lib/j2ee-xmlbeans-1.4.jar:/opt/soapui/lib/saxon-9.1.0.6j.jar:/opt/soapui/lib/saxon-dom-9.1.0.6j.jar:/opt/soapui/lib/xmlunit-1.2.jar:/opt/soapui/lib/xmlsec-1.4.3.jar:/opt/soapui/lib/xalan-2.7.1.jar:/opt/soapui/lib/xercesImpl-2.9.1.jar:/opt/soapui/lib/xml-apis-2.9.1.jar:/opt/soapui/lib/serializer-2.7.1.jar:/opt/soapui/lib/wss4j-1.5.8.jar:/opt/soapui/lib/opensaml-1.1.jar:/opt/soapui/lib/bcprov-jdk15-143.jar:/opt/soapui/lib/jtidy-r820.jar:/opt/soapui/lib/jxbrowser-1.3.21478.301.jar:/opt/soapui/lib/jniwrap-3.7.3.jar:/opt/soapui/lib/tuxpack-0.2.jar:/opt/soapui/lib/winpack-3.7.1.jar:/opt/soapui/lib/xulrunner-win32.jar:/opt/soapui/lib/xulrunner-linux-i686.jar:/opt/soapui/lib/xulrunner-mac-un-i386-ppc.jar:/opt/soapui/lib/MozillaGlue-jxbrowser-1.3.jar:/opt/soapui/lib/MozillaInterfaces-jxbrowser-1.3.jar:/opt/soapui/lib/netcomponents-1.3.8a.jar:/opt/soapui/lib/commons-digester-1.7.jar:/opt/soapui/lib/jasperreports-3.5.2.jar:/opt/soapui/lib/itext-2.1.0.jar:/opt/soapui/lib/jfreechart-1.0.13.jar:/opt/soapui/lib/jcommon-1.0.16.jar:/opt/soapui/lib/reports-1.0.jar:/opt/soapui/lib/wsi-test-tools-1.0.jar java.class.version=50.0 java.endorsed.dirs=/opt/bea/jdk160_05/jre/lib/endorsed java.ext.dirs=/opt/bea/jdk160_05/jre/lib/ext:/usr/java/packages/lib/ext java.home=/opt/bea/jdk160_05/jre java.io.tmpdir=/tmp java.library.path=/opt/soapui/bin java.runtime.name=Java(TM) SE Runtime Environment java.runtime.version=1.6.0_05-b13 java.specification.name=Java Platform API Specification java.specification.vendor=Sun Microsystems Inc. java.specification.version=1.6 java.vendor=Sun Microsystems Inc. java.vendor.url=http://java.sun.com/ java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi java.version=1.6.0_05 java.vm.info=mixed mode java.vm.name=Java HotSpot(TM) Server VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Sun Microsystems Inc. java.vm.specification.version=1.0 java.vm.vendor=Sun Microsystems Inc. java.vm.version=10.0-b19 line.separator= os.arch=i386 os.name=Linux os.version=2.6.28-15-generic path.separator=: soapui.ext.actions=/opt/soapui/bin/actions soapui.ext.libraries=/opt/soapui/bin/ext soapui.ext.listeners=/opt/soapui/bin/listeners soapui.home=/opt/soapui/bin soapui.properties=soapui.properties sun.arch.data.model=32 sun.awt.xembedserver=true sun.boot.class.path=/opt/bea/jdk160_05/jre/lib/resources.jar:/opt/bea/jdk160_05/jre/lib/rt.jar:/opt/bea/jdk160_05/jre/lib/sunrsasign.jar:/opt/bea/jdk160_05/jre/lib/jsse.jar:/opt/bea/jdk160_05/jre/lib/jce.jar:/opt/bea/jdk160_05/jre/lib/charsets.jar:/opt/bea/jdk160_05/jre/classes sun.boot.library.path=/opt/bea/jdk160_05/jre/lib/i386 sun.cpu.endian=little sun.cpu.isalist= sun.io.unicode.encoding=UnicodeLittle sun.java.launcher=SUN_STANDARD sun.jnu.encoding=UTF-8 sun.management.compiler=HotSpot Tiered Compilers sun.os.patch.level=unknown user.country=CZ user.dir=/home/hisaak/soapui user.home=/home/hisaak user.language=cs user.name=hisaak user.timezone=Europe/Bratislava wsi.dir=/opt/soapui/wsi-test-tools1.5KViews0likes0CommentsJDBC DataSource charset problem
Hi all, I'm trying to create test case with JDBC DataSource. Everything works just fine, but I get my data in incorrect charset probably. I attached two screenshots that demonstrate this soapUI issue. The first screenshot is from my DbXaminer Eclipse plug-in and contains correct data. The second screenshot is from soapUI. The same query, the same database, the same Thin driver, but different data in result. Any help would be appreciated. soapUI Pro 3.0.1 on Linux, Oracle 10g database David3.1KViews0likes3Comments