-
Perhaps the problem is related to the shell that STAFProc is using. In your example where you ran the su command, you were using the bash shell. The default shell used that STAF uses for Unix systems is /bin/sh. Maybe the su command doesn't work properly using the /bin/sh shell on your Solaris system. You should see if that's the case.
2009-11-25 17:01:37 UTC in SW Test Automation Framework
-
You need to think about how you need to test your particular application. STAF (and optionally STAX) can be used to automate how your test your application.
Perhaps you should start by looking at some of the STAF documentation such as "Getting Started with STAF" at [http://staf.sourceforge.net/current/STAFGS.pdf][1].
You may also find it helpful to go through the STAF/STAX education...
2009-11-25 16:52:23 UTC in SW Test Automation Framework
-
slucas committed patchset 4974 of module src to the SW Test Automation Framework CVS repository, changing 2 files.
2009-11-21 02:04:10 UTC in SW Test Automation Framework
-
This problem could be recreated by running a STAX job that started several subjobs in parallel. While multiple STAX jobs are starting, you'll get this error when selecting an option like "Start Monitoring" after selecting a job in the table. The fix was to display a "System Busy" message if fActiveJobsTable.getSelectedRow() returned -1 instead of a valid row index. Once the jobs have started...
2009-11-21 01:57:35 UTC in SW Test Automation Framework
-
The following exception can occur after right clicking on a STAX job and selecting the "Monitor job" action. Occasionally, instead of monitoring the job, we get this exception.
C:\STAF\services\stax>java -jar STAXMon.jar
Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException
at com.ibm.staf.service.stax.STAXMonitorTableSorter.getValueAt(STAXMonit...
2009-11-20 23:00:06 UTC in SW Test Automation Framework
-
slucas committed patchset 4973 of module src to the SW Test Automation Framework CVS repository, changing 1 files.
2009-11-20 21:19:11 UTC in SW Test Automation Framework
-
So, can you have su run a command, e.g. env, as your oracle user from the command line as follows? Note in your example you were not specifying the -c option to specify a command for su to run (so that it could be run automatically, without additional entry of commands).
su - oracle -c env
If so, then STAFProc should also be able to run that same command via a PROCESS START request if...
2009-11-20 16:21:20 UTC in SW Test Automation Framework
-
You can google for more information on su and how to configure it on your operating system (as questions about this are not STAF-specific). Note that you can run su from the command line (without STAF) to test that you have it set up without prompting. For example, on my Linux machine within logged on as root, I can use su to run command "env" as username "staf" without being prompted for a...
2009-11-20 15:37:41 UTC in SW Test Automation Framework
-
Does the user id you're logged in as have write access to /usr/local? It must if you're trying to install STAF to the default location of /usr/local/staf.
e.g. Can you run the following commands?
mkdir /usr/local/staf
echo "#!/bin/sh" > /usr/local/staf/STAFUninst
Otherwise you can specify parameter -target to specify another fully-qualified path to install STAF that you do...
2009-11-19 21:40:54 UTC in SW Test Automation Framework
-
What user was logged in when you started STAFProc? In the example I used, STAFProc was started when logged in as the root user. Only the root user can switch to another user using su without it prompting for a password. So, if you start STAFProc when logged in as the root user, you shouldn't have this issue.
I think you can also tell su not to ask for password in the sudo configuration...
2009-11-19 19:01:56 UTC in SW Test Automation Framework
