Rational QualityArchitect 
Weblogic EJB Testing Sample Scripts

 

In this directory structure you will find a sample Unit Test, Scenario Test and Stub along with batch files to run these tests.  These assets are exact duplicates of those created during the demo.  These sample tests, however, can be run independent of the demo.  As such, should you get into "demo-trouble" you will always have a way out!  These assets should always work.

You will also find desktop shortcuts which you can use to make your demo life easier.


Running the Sample Tests

Batch File to Execute Description

WebLogic Assets\Sample_StartServer.Bat
This batch file will start the WebLogic 6.1 server
RQA WebLogic Assets\Sample_UnitTest.Bat This batch file will run the unit test in the unittests directory.  This is an exact duplicate of the unit test that is created during the demo.  If you run the test against the EJBs as installed, the test will show failures in the log.  If you deploy the stub component, then the test will show passes in the log.  In either case, the test should run to completion without errors.
RQA WebLogic Assets\Sample_DeployStub.Bat This batch file will deploy a pre-created stub to the server.  The stub willreplace the faulty CustomerHelper EJB from the system.  With the stub deployed, the Unit Test will show pass in the log.
RQA WebLogic Assets\Sample_ResetDemo.Bat This batch file will reset the WebLogic 6.1 server to its original state.  It will prompt you to delete all assets created during the demo and it will remove the stub, replacing it with the original CustomerHelper component.
RQA WebLogic Assets\Sample_ResetDemo.Bat This batch file will run the scenario test in the scenariotests directory.  This is an exact duplicate of the scenario test that is created during the demo.  The test should show pass upon first execution.  The test should run to completion without errors.
 

Make Your Life Easier

You'll find it's easier to create Desktop Shortcuts to the various batch files used in this demo, as opposed to constantly running batch files from Windows Explorer or from the command line.  Users on Windows 2000 can expand the a self extracting zip to create these desktop shortcuts.