From FCOHEN at PUSHTOTEST.COM Sun Dec 2 16:01:05 2007 From: FCOHEN at PUSHTOTEST.COM (Frank Cohen) Date: Sun Dec 2 16:28:54 2007 Subject: [Dev] TM 5.1 source update, final change pending Message-ID: <568937B4-BEB0-4C28-B51E-2E3A8EA4D246@PUSHTOTEST.COM> Hi TestMaker Developers: I committed fixes to problems with the summary reports, a problem where the TestNodes icons were not appearing, and a problem where newly created TestScenarios were throwing XML validation errors. I have one more issue to solve: Implementing the TestGen4Web Interpreter as a script runner. I'll be doing that tomorrow. I hope to post TestMaker 5.1 Release Candidate 1 on Monday night. -Frank -- Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 871 0122 TestMaker open-source test automation From fcohen at pushtotest.com Tue Dec 4 14:29:20 2007 From: fcohen at pushtotest.com (Frank Cohen) Date: Tue Dec 4 14:57:47 2007 Subject: [Dev] TestMaker 5.1 completed Message-ID: <5A138F86-21AF-4E20-AEC6-C644459D9ED5@pushtotest.com> Hi TestMaker Dev heads: I finished the last of the TM 5.1 enhancements/fixes: 1) TestGen4Web ScriptRunner now uses the TG4W htmlunit-interpreter to run tests. This means all of the TG4W recorded steps - including pop- up menu Selects and Windows - are fully supported. 2) I fixed all of the problems with the new Summary Report. The TPS value now shows correctly and the order of the reports is correct. 3) The validation failure for new TestScenarios is fixed. Plus, TestMaker is a little kinder when it reports TestScenario syntax errors. I will package-up Release Candidate 1 tonight and make an announcement. -Frank -- Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 871 0122 TestMaker open-source test automation From fcohen at pushtotest.com Wed Dec 5 19:47:05 2007 From: fcohen at pushtotest.com (Frank Cohen) Date: Wed Dec 5 20:15:51 2007 Subject: [Dev] A small delay on TM 5.1 RC 1 Message-ID: <31D30978-4190-434E-A065-C2488155FCF9@pushtotest.com> Hi TestMaker Developers: I have run into a small delay in posting the TestMaker 5.1 Release Candidate. I found a few minor bugs that need to be fixed in the TestGen4Web script runner and translation utility. Also, some of the engineers are working on additional improvements that I will roll-up into TestMaker. If you want to get TM 5.1 right away, checkout the cvs.pushtotest.com tm5 repository and build a distribution. At my current rate I expect the Release Candidate will be available on Saturday. -Frank -- Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 871 0122 TestMaker open-source test automation From olivier.dony at denali.be Tue Dec 11 08:45:22 2007 From: olivier.dony at denali.be (Olivier Dony) Date: Tue Dec 11 09:15:06 2007 Subject: [Dev] Exception prevents running non-jython test scripts on Apple's Java 6.0 JVM Message-ID: <17F8A0DC-D837-4090-8A1B-DD1D124525C4@denali.be> Dear all, We have been trying to run Groovy test scripts using the latest version of TestMaker (updated from CVS just now) on Mac Os X. It is apparently mandatory to use a java 6 JVM for the jetty-based testnodes, as a lot of JAR dependencies are compiled for 6.0 (e.g. browserjs-engine.jar, groovy-engine.jar, etc.). However when the TestNode is started using the Apple JVM 6.0 (the one and only developer preview release), it fails to execute our groovy script due to the ClassCastException below. Note that the script runs fine within TestMaker when executed locally through the Agent->'Run Script locally...' menu. It also works when we use a jython script, presumably because the TestRunner does something different for jython than for other scripting languages, in methodFromCallScript(). The issue could be a conflict due to duplicate JSR-223 APIs in the classpath, similarly to the issue described on this page : http:// weblogs.java.net/blog/robc/archive/2007/03/using_phobos_wi.html#c27286 (however simply removing the script-api.jar from the webapp libs doesn't work) We are still trying to work around this issue, so any help/thoughts are welcome! java.lang.ClassCastException: com.sun.script.javascript.RhinoScriptEngineFactory cannot be cast to javax.script.ScriptEngineFactory at javax.script.ScriptEngineManager.initEngines (ScriptEngineManager.java:109) at javax.script.ScriptEngineManager.access$000 (ScriptEngineManager.java:37) at javax.script.ScriptEngineManager$1.run(ScriptEngineManager.java:80) at java.security.AccessController.doPrivileged(Native Method) at javax.script.ScriptEngineManager.init(ScriptEngineManager.java:78) at javax.script.ScriptEngineManager.(ScriptEngineManager.java:51) at com.pushtotest.testmaker.XSTest.xml.TestScenario.ScriptRunner.methodFrom CallScript(ScriptRunner.java:325) at com.pushtotest.testmaker.XSTest.xml.TestScenario.ScriptRunner.methodFrom Call(ScriptRunner.java:307) at com.pushtotest.testmaker.XSTest.xml.TestScenario.ScriptRunner.setupMetho dForTest(ScriptRunner.java:251) at com.pushtotest.testmaker.XSTest.xml.TestScenario.ScriptRunner.setMethods (ScriptRunner.java:237) at com.pushtotest.testmaker.XSTest.xml.TestScenario.ScriptRunner. (ScriptRunner.java:226) at com.pushtotest.testmaker.XSTest.xml.TestScenario.TestusecaseRunner.creat eThread(TestusecaseRunner.java:483) at com.pushtotest.testmaker.XSTest.xml.TestScenario.TestusecaseRunner.creat eUsecase(TestusecaseRunner.java:280) at com.pushtotest.testmaker.XSTest.xml.TestScenario.TestscenarioRunner.runU secase(TestscenarioRunner.java:803) at com.pushtotest.testnetwork.Scenario.run(Unknown Source) at com.pushtotest.testnetwork.TestNode.doExecute(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:589) at org.apache.axis.providers.java.RPCProvider.invokeMethod (RPCProvider.java:397) at org.apache.axis.providers.java.RPCProvider.processMessage (RPCProvider.java:186) at org.apache.axis.providers.java.JavaProvider.invoke (JavaProvider.java:323) at org.apache.axis.strategies.InvocationStrategy.visit (InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java: 453) at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281) at org.apache.axis.transport.http.AxisServlet.doPost (AxisServlet.java:699) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.axis.transport.http.AxisServletBase.service (AxisServletBase.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 487) at org.mortbay.jetty.servlet.ServletHandler.handle (ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle (SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle (SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle (ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 405) at org.mortbay.jetty.handler.ContextHandlerCollection.handle (ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle (HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:295) at org.mortbay.jetty.HttpConnection.handleRequest (HttpConnection.java:503) at org.mortbay.jetty.HttpConnection$RequestHandler.content (HttpConnection.java:841) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) at org.mortbay.io.nio.SelectChannelEndPoint.run (SelectChannelEndPoint.java:361) at org.mortbay.thread.BoundedThreadPool$PoolThread.run (BoundedThreadPool.java:442) Thanks! -- Olivier Dony Denali s.a., "Bridging the gap between Business and IT" Rue de Clairvaux 8, B-1348 Louvain-la-Neuve, Belgium Office: +32 10 43 99 51 Fax: +32 10 43 99 52 www.denali.be Legal Notice: This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message by mistake, please advise the sender immediately by return e-mail and delete this message from your system. Thank you for your cooperation. From olivier.dony at denali.be Tue Dec 11 08:57:19 2007 From: olivier.dony at denali.be (Olivier Dony) Date: Tue Dec 11 09:26:48 2007 Subject: [Dev] Re: [ptt-users] Exception prevents running non-jython test scripts on Apple's Java 6.0 JVM In-Reply-To: <17F8A0DC-D837-4090-8A1B-DD1D124525C4@denali.be> References: <17F8A0DC-D837-4090-8A1B-DD1D124525C4@denali.be> Message-ID: <79437644-A559-4610-8159-AA25008EA808@denali.be> On Dec 11, 2007, at 5:45 PM, Olivier Dony wrote: > Dear all, > > We have been trying to run Groovy test scripts using the latest > version of TestMaker (updated from CVS just now) on Mac Os X. > > It is apparently mandatory to use a java 6 JVM for the jetty-based > testnodes, as a lot of JAR dependencies are compiled for 6.0 (e.g. > browserjs-engine.jar, groovy-engine.jar, etc.). > However when the TestNode is started using the Apple JVM 6.0 (the > one and only developer preview release), it fails to execute our > groovy script due to the ClassCastException below. > > Note that the script runs fine within TestMaker when executed > locally through the Agent->'Run Script locally...' menu. > It also works when we use a jython script, presumably because the > TestRunner does something different for jython than for other > scripting languages, in methodFromCallScript(). > > The issue could be a conflict due to duplicate JSR-223 APIs in the > classpath, similarly to the issue described on this page : http:// > weblogs.java.net/blog/robc/archive/2007/03/using_phobos_wi.html#c27286 > (however simply removing the script-api.jar from the webapp libs > doesn't work) > > We are still trying to work around this issue, so any help/thoughts > are welcome! Well, it turns out that jython.jar does contain a "javax/script/ ScriptEngineFactory.class" file that conflicts with the JVM's one in our case. The groovy test seems to run if I remove the "jython.jar" from the web-app's lib dir in jetty, which is ok as long as I don't need to run jython-based tests. Maybe the developers could look into removing the conflicting classes from jython.jar for TM 5.1, if this doesn't break anything else? Cheers, -- Olivier Dony Denali s.a., "Bridging the gap between Business and IT" Rue de Clairvaux 8, B-1348 Louvain-la-Neuve, Belgium Office: +32 10 43 99 51 Fax: +32 10 43 99 52 www.denali.be Legal Notice: This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message by mistake, please advise the sender immediately by return e-mail and delete this message from your system. Thank you for your cooperation. From fcohen at pushtotest.com Wed Dec 12 06:52:56 2007 From: fcohen at pushtotest.com (Frank Cohen) Date: Wed Dec 12 07:23:05 2007 Subject: [Dev] Re: [ptt-users] Exception prevents running non-jython test scripts on Apple's Java 6.0 JVM In-Reply-To: <79437644-A559-4610-8159-AA25008EA808@denali.be> References: <17F8A0DC-D837-4090-8A1B-DD1D124525C4@denali.be> <79437644-A559-4610-8159-AA25008EA808@denali.be> Message-ID: Hi Olivier: This is fascinating. I am in contact with the JSR-223 team members at Sun and will bring the double javax/script/ScriptEngineFactory.class issue up to them. I will let you know what I learn. I am a fellow Mac OS X user. I am still on 10.4.11 (waiting another couple of months to go to 10.5.) I was very disappointed to learn that Leopard shipped without Java 6. See http://www.pushtotest.com/ thecohenblog/apple-ships-leopard-without-java-6. In fact, Apple recently took down the Java 1.6 developer preview from their site. Your Groovy script runs fine when run locally in TestMaker because that function is not using the JSR 223 ScriptEngine. I opened an enhancement ticket for this at http://bugs.pushtotest.com/ticket/200. I am open to your ideas on workarounds. Thank you, Olivier, for your support. I very much appreciate your effort. -Frank On Dec 11, 2007, at 8:57 AM, Olivier Dony wrote: > On Dec 11, 2007, at 5:45 PM, Olivier Dony wrote: > >> Dear all, >> >> We have been trying to run Groovy test scripts using the latest >> version of TestMaker (updated from CVS just now) on Mac Os X. >> >> It is apparently mandatory to use a java 6 JVM for the jetty-based >> testnodes, as a lot of JAR dependencies are compiled for 6.0 (e.g. >> browserjs-engine.jar, groovy-engine.jar, etc.). >> However when the TestNode is started using the Apple JVM 6.0 (the >> one and only developer preview release), it fails to execute our >> groovy script due to the ClassCastException below. >> >> Note that the script runs fine within TestMaker when executed >> locally through the Agent->'Run Script locally...' menu. >> It also works when we use a jython script, presumably because the >> TestRunner does something different for jython than for other >> scripting languages, in methodFromCallScript(). >> >> The issue could be a conflict due to duplicate JSR-223 APIs in the >> classpath, similarly to the issue described on this page : http:// >> weblogs.java.net/blog/robc/archive/2007/03/ >> using_phobos_wi.html#c27286 >> (however simply removing the script-api.jar from the webapp libs >> doesn't work) >> >> We are still trying to work around this issue, so any help/ >> thoughts are welcome! > > > Well, it turns out that jython.jar does contain a "javax/script/ > ScriptEngineFactory.class" file that conflicts with the JVM's one > in our case. > The groovy test seems to run if I remove the "jython.jar" from the > web-app's lib dir in jetty, which is ok as long as I don't need to > run jython-based tests. > > Maybe the developers could look into removing the conflicting > classes from jython.jar for TM 5.1, if this doesn't break anything > else? > > > Cheers, > > > -- > Olivier Dony > > Denali s.a., "Bridging the gap between Business and IT" > Rue de Clairvaux 8, B-1348 Louvain-la-Neuve, Belgium > Office: +32 10 43 99 51 Fax: +32 10 43 99 52 > www.denali.be > > Legal Notice: This message may contain confidential and/or > privileged information. If you are not the addressee or authorized > to receive this for the addressee, you must not use, copy, disclose > or take any action based on this message or any information herein. > If you have received this message by mistake, please advise the > sender immediately by return e-mail and delete this message from > your system. Thank you for your cooperation. > > _______________________________________________ > Users mailing list > Users@lists.pushtotest.com > http://lists.pushtotest.com/mailman/listinfo/users > -- Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 871 0122 TestMaker open-source test automation From fcohen at pushtotest.com Tue Dec 18 16:47:31 2007 From: fcohen at pushtotest.com (Frank Cohen) Date: Tue Dec 18 19:58:12 2007 Subject: [Dev] Update on new Results Analysis Engine Message-ID: <0512BB15-006E-4CD5-9C68-76EC787C041D@pushtotest.com> Hi TestMaker Developers: William, Luis Carlos, Luigi and I had a phone call to review the new design document. Download the design document at: http://downloads.pushtotest.com/tm5/TM_Results_DesignDoc_fc_v2.pdf Here were my questions: Question: Will the Performance Comparison Utility (PCU) continue to function after the new Results Analysis package changes? Answer: Yes, the PCU will continue to function as it does today. Question: Will I be able to point the new results charting to an archived results directory? Answer: Frank will develop a new user interface to select the source results. Question: Does the new result factory deal with multiple results files? Answer: Yes. Question: How will the new Results Analysis package handle very large test result files? For instance, a test that runs for 24 hours. Answer: William and Luis Carlos are considering a summary index function so the entire log does not reside in memory. Question: What is the schedule for rest of the days in this week? Answer: Luis Carlos started on the changes to the summary schema, design of the classes, will start with summary class and tally class. Our next phone call status update meeting is on Thursday December 20 at 11 am Pacific time. Please let me know if you would like to participate. -Frank -- Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 871 0122 TestMaker open-source test automation From beattiedb at ldschurch.org Fri Dec 21 11:58:15 2007 From: beattiedb at ldschurch.org (Douglas Beattie) Date: Fri Dec 21 12:30:43 2007 Subject: [Dev] Help with initial building of tm5. Also placing PushToTest into Eclipse. Message-ID: <476BB86C.2237.008F.0@ldschurch.org> I would like to set up to build (contribute to as well) PushToTest in the Eclipse (Europa) environment. If anyone has put together an environment to import into Eclipse I would love to get it from you as I am having problems getting everything properly in place. (I'm down to a couple of errors dealing with com.pushtotest.testmaker.XSTest.xml.TestScenario TestT not having a getWhile() method and CallT not finding a getInstance() method. In the mean time I tried to build the vanilla tm5 using ant build_distribution. I get the following: beattiedb:~/Desktop/PushToTest/Src/tm5> ant build_distribution Buildfile: build.xml [echo] ============================================================== [echo] PushToTest(tm) TestMaker Distribution Generator [echo] PushToTest TestMaker is the open-source SOA governance and [echo] test automation platform. Details at http://www.pushtotest.com [echo] ============================================================== clean: [echo] Removing any previous distribution. compile_modules: [echo] ============================================== [echo] Compile All Modules [echo] Monitors: WinMonitor jar: [mkdir] Created dir: /home/default/Desktop/PushToTest/Src/tm5/TestMaker/PTTMonitor/build [javac] Compiling 3 source files to /home/default/Desktop/PushToTest/Src/tm5/TestMaker/PTTMonitor/build [jar] Building jar: /home/default/Desktop/PushToTest/Src/tm5/TestMaker/PTTMonitor/PTTMonitor.jar [jar] Building jar: /home/default/Desktop/PushToTest/Src/tm5/TestMaker/PTTMonitor/PTTMonitorClient.jar [copy] Copying 1 file to /home/default/Desktop/PushToTest/Src/tm5/TestMaker/lib [echo] Monitors: UnixMonitor -pre-init: -init-private: -init-user: -init-project: -init-macrodef-property: -do-init: -post-init: -init-check: -init-macrodef-javac: -init-macrodef-junit: -init-macrodef-nbjpda: -init-macrodef-debug: -init-macrodef-java: -init-presetdef-jar: init: deps-jar: -pre-pre-compile: [mkdir] Created dir: /home/default/Desktop/PushToTest/Src/tm5/TestMaker/PTTMonitor/UnixMonitor/build/classes -pre-compile: -do-compile: [javac] Compiling 5 source files to /home/default/Desktop/PushToTest/Src/tm5/TestMaker/PTTMonitor/UnixMonitor/build/classes -post-compile: compile: -pre-jar: -pre-pre-jar: -do-jar-with-manifest: -do-jar-without-manifest: -do-jar-with-mainclass: [j2seproject1:jar] Building jar: /home/default/Desktop/PushToTest/Src/tm5/TestMaker/PTTMonitor/UnixMonitor/dist/UnixMonitor.jar [echo] To run this application from the command line without Ant, try: BUILD FAILED /home/default/Desktop/PushToTest/Src/tm5/build.xml:86: The following error occurred while executing this line: /home/default/Desktop/PushToTest/Src/tm5/TestMaker/PTTMonitor/UnixMonitor/nbproject/build-impl.xml:300: You must specify at least one of targetOS, dirSep, or pathSep Total time: 2 seconds Any thoughts on this problem. I am not familiar with building using ant. (Sorry) Any help you may be able to provide would be greatly appreciated as I would like to be able to dig into PushToTest with a good debugger to better understand the product before I look at ways to help improve it. Doug ---------------------------------------------------------------------- NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. From fcohen at pushtotest.com Sun Dec 30 12:14:05 2007 From: fcohen at pushtotest.com (Frank Cohen) Date: Sun Dec 30 12:48:40 2007 Subject: [Dev] TestMaker 5.1 tagged and available for download Message-ID: <063D4417-D62E-46F8-98B8-DC400584DFDB@pushtotest.com> Dear TestMaker Developers: I am happy to report that TestMaker 5.1 is checked-into cvs.pushtotest.com and available for immediate download at http:// www.pushtotest.com. I tagged the version 5.1 source code with tm51_rc1 in the tm5 repository. I anticipate we will have 3 release candidates to solve bugs and make additional improvements. I look forward to your comments on TestMaker 5.1. Thank you to everyone that participated in this release! -Frank -- TestMaker 5.1 Changes * TestMaker 5.0 ships with TestGen4Web 0.49 that fails to install on Firefox 2.0.0.7 or later. TestMaker now ships with TestGen4Web 0.50.2-PTT to be fully compatible with Firefox 2.0.0.7 and later. * TestMaker 5.1 changes the way TestGen4Web scripts are run in the TestNode environment. The new script runner uses TestGen4Web's htmlunit-interpreter package. This improves TestMaker's ability to natively run TestGen4Web recorded unit tests. * TestMaker 5.1 offers many minor improvements and bug fixes to the results and reporting capabilities. The charts for a load test now include a legend of concurrent user (CR) levels. We fixed an issue where load tests greater than 12 hours show negative horizontal axis values in the resource distribution charts. We removed the load test summary report from the output panel. We added new options to the TestScenario definition for a load test to automatically save all charts to the results directory and create an HTML-based summary report. * We fixed many problems with installing and running TestMaker on Mac OS X, including an installation problem that prevented the Resource Monitor (PTTMonitor) from running. * We updated the documention by correcting many spelling and grammer problems and including new sections for QA Testers and IT management. Additionally, we added new documentation to show the options to log results data directly to a Relational Database Management System (RDBMS)and added documentation to show how to set TestMaker and TestNode memory settings. * We did an overhaul of the TestMaker classpath and supporting Java Archive Resource (JAR) files. * TestMaker runs on Windows XP, Windows 2003 Server, and Windows Vista. TestMaker 5.1 and later is no longer compatible with the old Windows 2000 and NT operating environments because of a bug in Windows that limits the size of a classpath. * TestMaker 5.0 shipped with a typo in the element in a TestScenario. The element was incorrectly named (notice the extra 's'.) TestMaker 5.1 accepts the correct and incorrect versions. * Added the File menu -> Open Scenario command to open TestScenarios. * Added new capability to TestScenarios to control timeout values for usecases (unit tests) that take too long to operate. * Added an option for the transaction distribution charts to use a moving data average instead of inserting every data point. A complete list of changes and their associated bug reports is found at: http://www.pushtotest.com/Docs/vreleasenotes -- Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 871 0122 TestMaker open-source test automation From gflaifel at ca.ibm.com Sun Dec 30 13:17:42 2007 From: gflaifel at ca.ibm.com (George Flaifel) Date: Sun Dec 30 13:52:20 2007 Subject: [Dev] George Flaifel/Markham/IBM Message-ID: I will be out of the office starting 12/14/2007 and will not return until 01/01/2008. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://cake.pushtotest.com/pipermail/dev/attachments/20071230/38c2d8d4/attachment.htm