Running a subset of all test suites?

Hey,
What is the best way to setup FlexUnit/Flex Builder/whatever else so only a subset of all the suites will be run?
For example, if I'm working on a particular class, I may only want to run that class' test suite (instead of waiting for my entire application's test suite to run).
PS: thanks for the quick responses!

This is the functionality that I want... But how I get a good user-interface for it? For example, when I'm writing Java in NetBeans there is a button for "run tests associated with this module", and when I'm writing Python I can run `nosetests` in the current directory to run tests associated with the code in that directory.
Is there an Eclipse plugin? Or some other trick for doing this with Flex code?
(thanks again for all the quick replies – they are much appreciated)
Edit: Of course, I forgot about this: http://www.codesquared.com/eclipse/installinstructions.html
Are there any other ways?

Similar Messages

Error while running ADF-BC Test Suite from command line

Hi,
I have created a separate test project containing the Test Suite for the Model componenet of my ADF-BC application.
I need to run this test project separately from jmeter.
The tests run fine from Jdev, But when I package the test project into a jar and try to run from command line, I get the following error:
java.lang.NoClassDefFoundError: oracle/jbo/ApplicationModule
 at com.oracle.cs.cap.module.applicationModule.ServiceAMFixture.<init>(ServiceAMFixture.java:36)
 at com.oracle.cs.cap.module.applicationModule.ServiceAMFixture.<clinit>(ServiceAMFixture.java:15)
 at com.oracle.cs.cap.module.view.EntitlementReportDurationViewVO.EntitlementReportDurationViewVOTest.<init>(EntitlementReportDurationViewVOTest.java:11)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
 at java.lang.reflect.Constructor.newInstance(Unknown Source)
 at org.junit.internal.runners.JUnit4ClassRunner.createTest(JUnit4ClassRunner.java:72)
 at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:79)
 at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51)
 at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44)
 at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
 at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
 at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42)
 at org.junit.internal.runners.CompositeRunner.runChildren(CompositeRunner.java:33)
 at org.junit.runners.Suite.access$000(Suite.java:26)
 at org.junit.runners.Suite$1.run(Suite.java:93)
 at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
 at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
 at org.junit.runners.Suite.run(Suite.java:91)
 at org.junit.internal.runners.CompositeRunner.runChildren(CompositeRunner.java:33)
 at org.junit.internal.runners.CompositeRunner.run(CompositeRunner.java:28)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:130)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:109)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:100)
 at org.junit.runner.JUnitCore.runMain(JUnitCore.java:81)
 at org.junit.runner.JUnitCore.main(JUnitCore.java:44)
Caused by: java.lang.ClassNotFoundException: oracle.jbo.ApplicationModule
 at java.net.URLClassLoader$1.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(Unknown Source)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 ... 27 more
The Test project jar is created as ADF Library JAR File with Model.jpr as the dependent project. This takes care of project class dependencies
All the adf library dependencies are added to the manifest file of the Test Project jar referring to a location lib/ in the jar file directory.
I tried creating the ApplicationModule using both Configuration class (Configuration.createRootApplicationModule) as well as using the JDBC Connection String but both fail when I run the test cases independently from jmeter.
Anybody came across such an error? Please help.
Thanks,
Sapna

Hi Timo,
Im using JDev version 11.1.1.6.0.
I checked the class path on the jdev console. All the library references are mentioned in the manifest.mf classpath of the test project like below:
Manifest-Version: 1.0
Class-Path: lib/identitystore.jar
lib/adfm.jar
lib/groovy-all-1.6.3.jar
lib/adftransactionsdt.jar
lib/adf-dt-at-rt.jar
lib/adfdt_common.jar
lib/adflibrary.jar
lib/xmlparserv2.jar
lib/db-ca.jar
lib/jdev-cm.jar
lib/ojmisc.jar
lib/commons-el.jar
lib/jsp-el-api.jar
etc...
So I expect the library references should be resolved looking at the manifest file.
Another set of entries that I see in the jdev classpath are related to the Model project which is under test.
-classpath
D:\CurrentProject_1\16_7_2013_3pm\11_7_2013\.adf;
D:\CurrentProject_1\16_7_2013_3pm\11_7_2013\Model\classes;
How do I put these entries into my class path? Will it be sufficient if I add the Model.jar into my test project classpath?
Thanks,
Sapna

Is it possible to run test suite B based on test Suite A?

There are 2 test suites:
A & B
I want to run the test suite B only when test suite A is successful.
Please give me some hints how to achieve this.

There isn't any official way to do this at this time. Pre-release we supported this but tools like FlashBuilder and some other interface points needed to know, before the testing began, how many tests they were expecting and that sort of derailed us.
However, if you want to know how to do this in a quick and dirty sort of way, and you don't mind doing a little work, here is an approach you can refine.
First, create yourself a static class or a singleton which implements IRunListener. Objects of this type can receive updates as tests run, fail, etc. So in your object you could keep track of any failure conditions which were important decision points. Call the addListener() method of the FlexUnitCore and pass your object in.
var core:FlexUnitCore = new FlexUnitCore()
core.addListener( mySpecialSingletonListener.getInstance() );
This will register your object to receive the updates I mention above. Next step, create a new runner which extends Suite. So, for example PotentiallyIgnoreMeRunner extends Suite.
Inside of here you are going to add a new function which I have provided here called ignoreRecursively:
protected function ignoreRecursively( notifier:IRunNotifier, description:IDescription ):void {
if ( description.isTest ) {
 notifier.fireTestIgnored( description );
} else {
 var children:Array = description.children;
 for ( var i:int=0; i<children.length; i++ ) {
 ignoreRecursively( notifier, children[ i ] );
Basically, it will cause each test in this suite to be marked as ignored in the output and will not execute it.
Then you will need to override the protected runChild() method to do something like this:
override protected function runChild( child:*, notifier:IRunNotifier, childRunnerToken:AsyncTestToken ):void {
var mySpecialSingleton:MySpecialSingleton = MySpecialSingleton.getInstance();
//Here you will need to call some function that accepts the current testClass and decides if it should be run or ignored
if ( mySpecialSingleton.shouldIRunThisSuite( testClass ) ) {
 super.runChild( child, notifier, childRunnerToken );
} else {
 var description:IDescription = describeChild( child );
 ignoreRecursively( notifier, description );
 childRunnerToken.sendResult();
Almost done, decorate your suite classes to use your new runner instead of ours:
[Suite]
[RunWith("some.package.PotentiallyIgnoreMeRunner")]
public class SuiteB {
Finally, make sure you include a reference to the PotentiallyIgnoreMeRunner somewhere in your application. Metadata is just a string to FlashBuilder and it will not automatically know to include the PotentiallyIgnoreMeRunner in the final swf file.
I just did a quick prototype and it will successfully ignore all tests based on the result of another.
Mike

Run several test suites in sequence

Hi,
I have several test suites. I would like to run each of them in sequence because each has its own configuration. If I did the following, tests from different suites will be mixed with others while running.
testRunner.test = new Suite1();
testRunner.startTest();
testRunner.test = new Suite2();
testRunner.startTest();
testRunner.test = new Suite2();
testRunner.startTest();
Anyone has ideas how to solve this?
Thanks,
Dina

Hi, Surely the ability to add test suites to test suites (the composite pattern) already allows this? Cheers, Ali On 01/02/2009 02:03, "Daniel Rinehart" <[email protected]> wrote: A new message was posted by Daniel Rinehart in FlexUnit Development -- Run several test suites in sequence A couple of suggestions. Dynamically create a new testRunner for each TestSuite, that way you can run them in sequence. Each test runner could be thrown into a tab navigator to easily view the results. The TestRunnerBase fires a TestsCompleteEvent which could be used to execute the next suite. The reporting of total tests across all suites could be done with a custom TestListener. -- Daniel R. <[email protected]> [http://danielr.neophi.com/] > I have several test suites. I would like to run each of them in sequence > because each has its own configuration. If I did the following, tests from > different suites will be mixed with others while running. > > testRunner.test = new Suite1(); > testRunner.startTest(); > testRunner.test = new Suite2(); > testRunner.startTest(); > testRunner.test = new Suite2(); > testRunner.startTest(); ------------------------------------------------------ View/reply at <a href=http://www.adobeforums.com/webx?13@@.59b799c6/0> Replies by email are OK. Use the unsubscribe form at <a href=http://www.adobeforums.com/webx?280@@.59b799c6!folder=.59b62b92> to cancel your email subscription.

Error while running test suite

Hi,
I have installed TCL-8.5 on unix platform and configured Berkely DB with test suite.
I then followed steps given in guide to run the test suite. On running the command
"% source ../test/test.tcl", following error occurs.
% source ../test/test.tcl
couldn't load file ".libs/libdb_tcl-4.6.so": .libs/libdb_tcl-4.6.so: ELF file OS ABI invalid
Could you please help me on this?
Thanks
Aman

I have compiled tcl8.5 and run some simple tests using Berkeley DB, and it appears that Berkeley DB is fine with tcl8.5 (as well as tcl8.4).
Searching for the error "ELF file OS ABI invalid" it seems to arise when people mix binaries from different platforms, for example attempting to use a Linux binary on a FreeBSD platform. Did you compile Tcl8.5 on the same platform you used for compiling Berkeley DB?
Regards,
Carol

Running berkeley db test suite

Hi
I'm new to berkeley db.
I'm an intern student who has to develop berkeley db and visual c++.
Is it necessary to run test suite after installing berkeley db?
why do we need to do so ?
another question.
how do i know that berkeley db is working ???
Thanks
Kevin
Edited by: 839384 on Feb 23, 2011 11:01 PM

Hello,
You do not have to run the BDB test suite. The directions
for doing so are in the documentation for the various platforms
under the "Build, Installation, and Upgrade Guide" at:
http://download.oracle.com/docs/cd/E17076_02/html/installation/index.html
For example:
"Running the test suite under UNIX" is at:
http://download.oracle.com/docs/cd/E17076_02/html/installation/build_unix_test.html
"Running the test suite under Windows" is at:
http://download.oracle.com/docs/cd/E17076_02/html/installation/build_win_test.html
You will also find a directory containing sample programs
under your distribution home directory and you can run any
of the programs there as a sanity check.
Thanks,
Sandra

Posix test suite run on solaris?

Has anyone run the posix test suite on solaris? or OpenSolaris?
http://posixtest.sourceforge.net/

Has anyone run the posix test suite on solaris? or OpenSolaris?
http://posixtest.sourceforge.net/

Running Fluint Test Suites in FlexUnit4

Hey, I am currently looking at migrating from Fluint to FlexUnit4 and have been experimenting with trying to get my test suites run using the Fluint1ClassRunner. However, I can't seem to find an example that will just let me pass in an array of TestSuites (like FlexUnitTestRunnerUI does) and have them executed. Is there any sample code out there that can get me up and running?
Thanks!

Hi,
You just pass them to the core, you can pass a test, a suite, an array, a combination of those, etc.
ar = [ t1, t2, t3, t4 ];
core = new FlexUnitCore();
core.run( ar );
Mike

How to run a test suite in JUnit?

I am newbie to JUnit. I am running JUnit 4 in eclipse 3.2.1. I have created test cases in a package called "testsuite". Moreover, I have created a test suite in the same package to run these test cases.
Sample code for a test case:
package testsuite;
import junit.framework.TestCase;
import org.junit.Before;
import org.junit.Test;
import system.NodeItem;
public class NodeItemTest extends TestCase {
    NodeItem aNode;
    @Before
    public void setUp() throws Exception {
        aNode = new NodeItem();
        aNode.setMinTempTherm(2);
    @Test
    public void testSetMinTempTherm() {
        assertEquals(2, aNode.getMinTempTherm());
Sample code for the test suite I have created to run this case and another one:
package testsuite;
import junit.framework.Test;
import junit.framework.TestSuite;
public class AllTests {
    public static Test suite() {
        TestSuite suite = new TestSuite("Test for testsuite");
        //$JUnit-BEGIN$
        suite.addTestSuite(CommunicationTest.class);
        suite.addTestSuite(NodeItemTest.class);
        //$JUnit-END$
        return suite;
The problem is:
When I run the test cases separetly, everything runs without any problems, but when I try to run the test suite I get the follwing ERROR:
In the Failure Trace window I get *"java.lang.Exception: No runnable methods".*
In the other winodw if I double click the error, a dialog pop up which says *"Method 'testsuite.AllTests' not found. Openning the test class"*.
I have followed some tutorials to reach the point I am at now. Please help me proceed.
Thanks in advance.

I didn't know I don't have to extend. Here is how I modified the code after your advace and it worked. Any other good advaces?
package testsuite;
import static org.junit.Assert.assertEquals;
//import junit.framework.TestCase;
import org.junit.Before;
import org.junit.Test;
import system.NodeItem;
public class NodeItemTest /*extends TestCase*/ {
     NodeItem aNode;
     @Before
     public void setUp() throws Exception {
          aNode = new NodeItem();
          aNode.setMinTempTherm(2);
     @Test
     public void testSetMinTempTherm() {
          assertEquals(3, aNode.getMinTempTherm());
package testsuite;
import org.junit.runner.RunWith;
import org.junit.runners.Suite;
//import junit.framework.Test;
//import junit.framework.TestSuite;
@RunWith(Suite.class)
@Suite.SuiteClasses({
     CommunicationTest.class,
     NodeItemTest.class,
//    TestClass3.class
public class AllTests {
//     public static Test suite() {
//          TestSuite suite = new TestSuite("Test for testsuite");
//          //$JUnit-BEGIN$
//          suite.addTestSuite(CommunicationTest.class);
//          suite.addTestSuite(NodeItemTest.class);
//          //$JUnit-END$
//          return suite;
}Thanks again!

Is my test suite configured properly?

I am building db-4.6.19 from source on Novell SuSE Linux 9.2 on ia64 (Intel Itanium2) hardware, then running the test suite with tclsh 8.4. Here’s my configuration line:
cd build_unix
../dist/configure prefix=/home/mark/WORKAREAS/webplatform/build/dev/20070924 with-test --with-tcl=/usr/lib
I run make and that goes well, then I run the standard test in tclsh via:
echo 'info tclversion; source ../test/test.tcl; run_std; exit' | tclsh; tail ALL.OUT
Most of the tests pass, but the tail of ALL.OUT is at db-4.6.19/build_unix/ALL.OUT (below) produces many error messages for a few tests. They seem to be variations on the same issue, and I’m not sure how to fix it at this point – can someone point me to help? It appears that a command isn't parsing properly.
I'm not sure how to troubleshoot further, it seems to be a syntax error.
Thanks!
eval test119 -hash "119" ; verify_dir ./TESTDIR "" 1
FAIL:14:29:10 (00:00:00) run_method: -hash test119: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
eval test120 -hash "120" ; verify_dir ./TESTDIR "" 1
FAIL:14:29:10 (00:00:00) run_method: -hash test120: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
eval test121 -hash "121" ; verify_dir ./TESTDIR "" 1
FAIL:14:29:10 (00:00:00) run_method: -hash test121: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
eval test122 -hash "122" ; verify_dir ./TESTDIR "" 1
FAIL:14:29:10 (00:00:00) run_method: -hash test122: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
Regression Tests Failed
Test suite run completed at: 14:29 09/24/07

Thanks, I have built in a new directory and ammended my configuration line to:
../dist/configure prefix=/home/mark/WORKAREAS/webplatform/build/dev/20070926 with-test enable-tcl with-tcl=/usr/lib
Results in:
checking build system type... ia64-unknown-linux-gnu
checking host system type... ia64-unknown-linux-gnu
checking if building in the top-level or dist directories... no
checking if --disable-cryptography option specified... no
checking if --disable-hash option specified... no
checking if --disable-mutexsupport option specified... no
checking if --disable-queue option specified... no
checking if --disable-replication option specified... no
checking if --disable-statistics option specified... no
checking if --disable-verify option specified... no
checking if --enable-compat185 option specified... no
checking if --enable-cxx option specified... no
checking if --enable-debug option specified... no
checking if --enable-debug_rop option specified... no
checking if --enable-debug_wop option specified... no
checking if --enable-diagnostic option specified... no
checking if --enable-dump185 option specified... no
checking if --enable-java option specified... no
checking if --enable-mingw option specified... no
checking if --enable-fine_grained_lock_manager option specified... no
checking if --enable-o_direct option specified... no
checking if --enable-posixmutexes option specified... no
checking if --enable-pthread_api option specified... no
checking if --enable-rpc option specified... no
checking if --enable-smallbuild option specified... no
checking if --enable-tcl option specified... yes
checking if --enable-test option specified... no
checking if --enable-uimutexes option specified... no
checking if --enable-umrw option specified... no
checking if --with-mutex=MUTEX option specified... no
checking if --with-tcl=DIR option specified... /usr/lib
checking if --with-uniquename=NAME option specified... no
checking for chmod... chmod
checking for cp... cp
checking for ln... ln
checking for mkdir... mkdir
checking for rm... rm
checking for sh... /bin/sh
checking for a BSD-compatible install... /usr/bin/install -c
checking for cc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether we are using gcc version 2.96... no
checking whether g++ requires -fhandle-exceptions... no
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ld used by cc... /usr/ia64-suse-linux/bin/ld
checking if the linker (/usr/ia64-suse-linux/bin/ld) is GNU ld... yes
checking for /usr/ia64-suse-linux/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... cc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 131072
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking whether the cc linker (/usr/ia64-suse-linux/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
appending configuration tag "F77" to libtool
checking SOSUFFIX from libtool... .so
checking MODSUFFIX from libtool... .so
checking JMODSUFFIX from libtool... .so
checking whether stat file-mode macros are broken... no
checking whether time.h and sys/time.h may both be included... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for struct stat.st_blksize... yes
checking for inttypes.h... (cached) yes
checking for stdint.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for unistd.h... (cached) yes
checking for char... yes
checking size of char... 1
checking for unsigned char... yes
checking size of unsigned char... 1
checking for short... yes
checking size of short... 2
checking for unsigned short... yes
checking size of unsigned short... 2
checking for int... yes
checking size of int... 4
checking for unsigned int... yes
checking size of unsigned int... 4
checking for long... yes
checking size of long... 8
checking for unsigned long... yes
checking size of unsigned long... 8
checking for long long... yes
checking size of long long... 8
checking for unsigned long long... yes
checking size of unsigned long long... 8
checking for char *... yes
checking size of char *... 8
checking for u_char... yes
checking for u_short... yes
checking for u_int... yes
checking for u_long... yes
checking for u_int8_t... yes
checking for u_int16_t... yes
checking for int16_t... yes
checking for u_int32_t... yes
checking for int32_t... yes
checking for u_int64_t... yes
checking for int64_t... yes
checking for FILE... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for time_t... yes
checking for size_t... (cached) yes
checking size of size_t... 8
checking for ssize_t... yes
checking for uintmax_t... yes
checking for uintptr_t... yes
checking for socklen_t... yes
checking for ANSI C exit success/failure values... yes
checking for mutexes... POSIX/pthreads/library
checking for main in -lpthread... yes
checking for library containing sched_yield... none required
checking for library containing fdatasync... none required
checking for library containing getaddrinfo... none required
checking for library containing hstrerror... none required
checking for main in -lm... yes
checking for main in -lnsl... yes
checking for main in -lpthread... (cached) yes
checking for main in -lsocket... no
checking for abort... yes
checking for atoi... yes
checking for atol... yes
checking for getcwd... yes
checking for getenv... yes
checking for getopt... yes
checking for isalpha... yes
checking for isdigit... yes
checking for isprint... yes
checking for isspace... yes
checking for memcmp... yes
checking for memcpy... yes
checking for memmove... yes
checking for printf... yes
checking for qsort... yes
checking for raise... yes
checking for rand... yes
checking for strcasecmp... yes
checking for strcat... yes
checking for strchr... yes
checking for strdup... yes
checking for strerror... yes
checking for strncat... yes
checking for strncmp... yes
checking for strrchr... yes
checking for strsep... yes
checking for strtol... yes
checking for strtoul... yes
checking for _fstati64... no
checking for directio... no
checking for fchmod... yes
checking for fclose... yes
checking for fcntl... yes
checking for fdatasync... yes
checking for fgetc... yes
checking for fgets... yes
checking for fopen... yes
checking for fwrite... yes
checking for getaddrinfo... yes
checking for getrusage... yes
checking for gettimeofday... yes
checking for getuid... yes
checking for hstrerror... yes
checking for localtime... yes
checking for mprotect... yes
checking for pstat_getdynamic... no
checking for pthread_yield... yes
checking for sched_yield... yes
checking for select... yes
checking for sigaction... yes
checking for snprintf... yes
checking for stat... yes
checking for strftime... yes
checking for sysconf... yes
checking for time... yes
checking for vsnprintf... yes
checking for yield... no
checking for ftruncate... yes
checking for clock_gettime... no
checking for ctime_r... yes
checking for 2 or 3 argument version of ctime_r... 2-argument
checking for pread... yes
checking for pwrite... yes
checking for fcntl/F_SETFD... yes
checking for special C compiler options needed for large files... no
checking for FILEOFFSET_BITS value needed for large files... no
checking for mlock... yes
checking for munlock... yes
checking for mmap... yes
checking for munmap... yes
checking for shmget... yes
checking for existence of /usr/lib/tclConfig.sh... loading
checking for 64-bit integral type support for sequences... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating db_cxx.h
config.status: creating db_int.h
config.status: creating clib_port.h
config.status: creating include.tcl
config.status: creating db.h
config.status: creating db_config.h
So I believe configuration is fine. Make also completes fine.
~/WORKAREAS/webplatform/build/dev/20070926/db-4.6.19/build_unix> tclsh
% source ../test/test.tcl
% run_std
Test suite run started at: 09:51 09/26/07
Berkeley DB 4.6.19: (August 10, 2007)
Running environment tests
Running archive tests
Running backup tests
Running file operations tests
Running locking tests
Running logging tests
Running memory pool tests
Running transaction tests
Running deadlock detection tests
Running subdatabase tests
Running byte-order tests
Running recno backing file tests
Running DBM interface tests
Running NDBM interface tests
Running Hsearch interface tests
Running secondary index tests
Running replication tests
Running security tests
Running recovery tests
FAIL:09:51:09 (00:00:00) r: recd: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
Running join test
Running btree tests
Running rbtree tests
Running queue tests
Running queueext tests
Running recno tests
Running frecno tests
Running rrecno tests
Running hash tests
UNEXPECTED OUTPUT: Berkeley DB 4.6.19: (August 10, 2007)
UNEXPECTED OUTPUT: FAIL:09:51:06 (00:00:00) r: env: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
UNEXPECTED OUTPUT: FAIL:09:51:06 (00:00:00) r: archive: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
UNEXPECTED OUTPUT: FAIL:09:51:06 (00:00:00) r: backup: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
UNEXPECTED OUTPUT: FAIL:09:51:06 (00:00:00) r: fop: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
UNEXPECTED OUTPUT: FAIL:09:51:06 (00:00:00) r: lock: bad command "handles": must be dbremove, dbrename, env, envremove, open, sequence, version, rand, random_int, srand, or debug_check
...and so on to the end. This seems to be the same issue I'd originally reported in this thread. Is there anything else I can do to troubleshoot this? I'm not a tcl expert, unfortunately.
Thanks again for your help or pointers!
--Mark

URGENT Please help with weird behavior of test suite

Hi All,
I have a composite involving three operations of two different services. The weird behavior comes by the time on which I run the test suite on the EM, if I try to emulate two different operation response from one service, by the time that the flow, tries to emulate the second one, I always receive this error:
part name="summary">
<summary>oracle.fabric.common.FabricException: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Error writing stream: java.io.IOException: Can only write attribute within a tag.: WSDLException: faultCode=OTHER_ERROR: Error writing stream: java.io.IOException: Can only write attribute within a tag.</summary>
</part>
On the other hand if I emulate two responses of the same operation it works.
Does any one have any idea of how to deal with this kind of test? Which seems a very simple test.
Best regards,

Hi thanks for your response, in detail my problem is as follows:
1- I have a simple composite with two services and three invokes, all of the operations are two ways operations. Here´s the BPEL (Service1 Demandas, operation Actualizar; Service 2 Aviso, operations buscar, actualizar):
<scope name="SINAUT_Aviso_SRV_Demandas_Actualizar">
<bpelx:annotation xmlns:bpelx="http://schemas.oracle.com/bpel/extension">
<bpelx:pattern patternName="bpelx:automated"/>
<bpelx:analysis>
<bpelx:property name="LastUpdateDate">9/10/10 9:35:50 AM</bpelx:property>
<bpelx:property name="BusinessId">Scope_151babe7-bc1e-11df-3ca0-0015c5fce8ce</bpelx:property>
</bpelx:analysis>
</bpelx:annotation>
<sequence>
<bpelx:annotation xmlns:bpelx="http://schemas.oracle.com/bpel/extension">
<bpelx:analysis>
<bpelx:property name="BusinessId">Sequence_151babe7-bc1e-11df-3ca0-0015c5fce8ce</bpelx:property>
<bpelx:property name="LastUpdateDate">9/10/10 9:35:50 AM</bpelx:property>
</bpelx:analysis>
</bpelx:annotation>
<assign name="Assign_1">
<copy>
<from variable="inputVariable"
query="/client:process/client:input/idDemada"
part="payload"/>
<to variable="Invoke_2_actualizar_InputVariable"
part="payload" query="/payload/demanda/idDemanda"/>
</copy>
<copy>
<from variable="inputVariable"
query="/client:process/client:input/estadoDemanda/codigo"
part="payload"/>
<to variable="Invoke_2_actualizar_InputVariable"
part="payload"
query="/payload/demanda/estadoDemanda/codigo"/>
</copy>
</assign>
<invoke name="Invoke_2"
inputVariable="Invoke_2_actualizar_InputVariable"
outputVariable="Invoke_2_actualizar_OutputVariable"
partnerLink="SRV_Demandas"
portType="ns2:SINAUT_Aviso_SRV_Demandas"
operation="actualizar"/>
</sequence>
</scope>
<scope name="SINAUT_Aviso_SRV_Avisos_Actualizar">
<bpelx:annotation xmlns:bpelx="http://schemas.oracle.com/bpel/extension">
<bpelx:pattern patternName="bpelx:automated"/>
<bpelx:analysis>
<bpelx:property name="LastUpdateDate">9/10/10 9:35:57 AM</bpelx:property>
<bpelx:property name="BusinessId">Scope_c235386b-bc1f-11df-3ca0-0015c5fce8ce</bpelx:property>
</bpelx:analysis>
</bpelx:annotation>
<sequence>
<bpelx:annotation xmlns:bpelx="http://schemas.oracle.com/bpel/extension">
<bpelx:analysis>
<bpelx:property name="BusinessId">Sequence_c235386b-bc1f-11df-3ca0-0015c5fce8ce</bpelx:property>
<bpelx:property name="LastUpdateDate">9/10/10 9:35:57 AM</bpelx:property>
</bpelx:analysis>
</bpelx:annotation>
<assign name="Assign_2">
<copy>
<from variable="inputVariable"
query="/client:process/client:input/ReferenciaPly"
part="payload"/>
<to variable="Invoke_1_actualizar_InputVariable"
part="payload" query="/payload/aviso/referenciaPlyAviso"/>
</copy>
<copy>
<from variable="inputVariable"
query="/client:process/client:input/estadoAviso/codigo"
part="payload"/>
<to variable="Invoke_1_actualizar_InputVariable"
part="payload" query="/payload/aviso/estadoAviso/codigo"/>
</copy>
</assign>
<invoke name="Invoke_1"
inputVariable="Invoke_1_buscar_InputVariable_1"
outputVariable="Invoke_1_buscar_OutputVariable_1"
partnerLink="SRV_Aviso"
portType="ns1:SINAUT_Aviso_SRV_Avisos"
operation="buscar"/>
<assign name="Assign_4">
<copy>
<from expression="'12345'"/>
<to variable="Invoke_3_actualizar_InputVariable"
part="payload" query="/payload/aviso/referenciaPlyAviso"/>
</copy>
</assign>
<invoke name="Invoke_3"
inputVariable="Invoke_3_actualizar_InputVariable"
outputVariable="Invoke_3_actualizar_OutputVariable_1"
partnerLink="SRV_Aviso"
portType="ns1:SINAUT_Aviso_SRV_Avisos"
operation="actualizar"/>
</sequence>
</scope>
2- My test suite is as follows:
<wireActions wireSource="SINAUT_Aviso_PR_DemandasActualizar_TO_BE_/SRV_Demandas" operation="actualizar">
<emulate duration="PT0S">
<message>
<part partName="payload">
<content>
<payload xmlns=""/>
</content>
</part>
</message>
</emulate>
</wireActions>
<wireActions wireSource="SINAUT_Aviso_PR_DemandasActualizar_TO_BE_/SRV_Aviso" operation="buscar">
<emulate duration="PT0S">
<message>
<part partName="payload">
<filePath>prueba_busqueda.xml</filePath>
</part>
</message>
</emulate>
</wireActions>
<wireActions wireSource="SINAUT_Aviso_PR_DemandasActualizar_TO_BE_/SRV_Aviso" operation="actualizar">
<emulate duration="PT0S">
<message>
<part partName="payload">
<filePath>prueba_actualizar.xml</filePath>
</part>
</message>
</emulate>
</wireActions>
3- When the test suite executes the second operation of the second service it throws this exception:
<bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>oracle.fabric.common.FabricException: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Error writing stream: java.io.IOException: Can only write attribute within a tag.: WSDLException: faultCode=OTHER_ERROR: Error writing stream: java.io.IOException: Can only write attribute within a tag.</summary></part><part name="detail"><detail>Can only write attribute within a tag.</detail></part></remoteFault></bpelFault>
4- if I change the second operation with the first one(buscar), it doesn't throws any exception.
5- If this is a limitation , how can I test a composite that involves n operations of the same service?
Kind regards and thanks for all of your support

Help!Jdbc test suite problem

hi,all
we have developed a jdbc driver for our DBMS.we used jdbc test suite which we downloaded it from sun web site to test our driver.when jdbc test run,we found many exception logged in jdbc-tests.log file,such as:
Beginning Test: testAddBatch01
Fatal: Problem with connection: java.io.FileNotFoundException: http://localhost:8000/servlet_vehicle/servlet_vehicle
End Test: testAddBatch01...........FAILED
I use jdbc-tests-suite1.2.1 version.do you encouter the problem?I am looking for your response!
thanks
sheidon

Hi,
I think you haven't start the server.So the program is trying to connect to the server and is raising the exception.
For a complete list of steps to be taken for installation and to run the tests, please visit our web site at http://java.sun.com/products/jdbc/jdbctestsuite-1_2_1.html#Steps to Install and Run the Tests
Hope this helps.
Good Luck.
Gayam.Srinivasa Reddy
Developer Technical Support
Sun Micro Sysytems
http://www.sun.com/developers/support/

[New Release] Oracle Application Testing Suite 12.5.0.1.0

Hi All,
OATS new release available, please check : http://www.oracle.com/technetwork/oem/app-test/index-084446.html
From Release Notes
Oracle Application Testing Suite 12.5.0.1 - New Features and Updates
Support for Chrome 32 browser - Oracle OpenScript includes support for the Chrome 32 browser for playback.
Support for Firefox 31 browser - Oracle OpenScript includes support for the Firefox 31 browser for record and playback.
Support for Internet Explorer 10 and 11 browser - Oracle OpenScript includes support for Internet Explorer 10 browser for playback on Windows 7 SP1 and Windows 8.
New movie recording of playback feature - Oracle OpenScript includes a new movie recording feature that allows recording and playback of a movie file showing the playback of OpenScript functional test scripts.
New advanced VU start, stop, and ramp features added to Oracle Load Testing - Oracle Load Test includes new features that provide advanced control over script start, stop, and ramp up conditions a the script level.
Support for Internet Explorer 10 and 11 browser - Oracle Load Testing and Oracle Test Manager include support for Internet Explorer 10 browser for playback on Windows 7 SP1 and Windows 8.
New Lightweight Directory Access Protocol (LDAP) authentication feature added for Oracle Test Manager - Oracle Test Manager Administrator tool includes new features for configuring the LDAP server to use for authentication.
-POPS

I have a similar problem with the OATS v9.20 installation. I did manage to install it on our main load generator (running Windows 2003 Server) but when it came to installing OpenScript on my laptop (XP SP3) the install 'hangs' at 78%.
I did raise a support call with Oracle about this (there was a bug report generated) but the case is still open.
I've been waiting to hear when the next version was due (in the hope that this might have been resolved) but by the sounds of it there could still be an issue on WinXP with v9.21?
For reference I originally logged this with the following in the description:
The installation looks like it is failing because of a double backslash in a path ending "OATS920\\bin\copyOUI.bat". We then get an error in javaw.exe which when OK'ed then stops the installation at the stage "creating 'Uninstall Oracle Application Testing Suite' in folder 'Oracle Application Testing Suite' ".

Simple test suite for regression testing

Hi,
I was wondering if anyone has a simple test suite available.
I'm after these main areas:
1. arbitary script lanching (or just firing off ud32 files)
2. database comms (inserting test data, extracting final status)
3. comparison (ala diff) for regression tests.
I have knocked out a partial (i.e. not 100% finished!) one myself in perl, but was wondering what else other people have created .
i'm Looking for insparation / use what has already been done!
Thank in adavance,
Wayne

Subclass the test case itself, and have a factory method to return instances of the correct class you wish to test, or, use a protected instance variable to put it in
e.g
public class TestMyClass extends TestCase {
   public MyClass getMyClass() {
     return new MyClass();
public void testSomething() {
       MyClass myClass = getMyClass();
       assertTrue(myClass.isWorking());
public class TestSubclass extends TestMyClass {
     @Override
     public MyClass getMyClass() {
        return new Subclass(); // assume this extends MyClass
     // all the superclass test methods still get run
}or
public class TestMyClass extends TestCase {
protected MyClass myClass;
public void setup() {
    this.myClass = new MyClass();
public void testSomething() {
       assertTrue(myClass.isWorking());
public class TestSubclass extends TestMyClass {
public void setup() {
    this.myClass = new SubClass();
     // all the superclass test methods still get run
}

Is there in JCOP a test suit for javacard OS?

Dear all,
I'm an newbie on this major and i need your help to clarify my situation:
Image that I have an applet on a java card... and there is no proprietary OS... only Javacard OS
now, i want to validate this using JCOP
is there any ready test suite available in JCOP for a general OS validation?
or we need to create the test suite? any patch or add-on available?
One more thing, There are many experts on JAVA CARD and i would like to make a friend with all of you.
Please send me your skype ID... or send to me a request to add friend with the following ID:
Skype: nobitagammer
safarmer, langkhachkenshin, Jean-Damien LEBUI, Sebastien_Lorquet , hoan_micheal ,.....
Thanks and Best Regards

I am not aware of any but I have not needed such a tool. The test cases we generally run are to validate applet behaviour on a given card platform so are very specific. We looking at new platforms we just want to know existing code works as expected.
- Shane

Running a subset of all test suites?

Similar Messages

Maybe you are looking for