| Home >> All |
Page 1 2 3 4 5 6
| • | test.MSGDispatch.* (3) | • | test.RPCDispatch.* (5) | • | test.badWSDL.* (2) |
| • | test.bea.* (12) | • | test.caffeine.* (11) | • | test.chains.* (3) |
| • | test.client.* (3) | • | test.clra.* (30) | • | test.compliance.* (162) |
| • | test.components.* (2) | • | test.concurrency.* (3) | • | test.connextra.* (2) |
| • | test.controller.* (14) | • | test.core.* (13) | • | test.dao.* (3) |
• test: Javadoc index of package test.
Package Samples:
• test.clra.member
• test.clra
• test.clra.rowing.remote
• test.clra.rowing
• test.clra.util
• test.clra.member.remote
• test.clra.web
• test.clra.xml.security
• test.clra.xml
• test.caffeine.jargus.tag
• test.caffeine.jargus
• test.compliance
• test.compliance.loading
• test.compliance.loading.support
• test.compliance.metadata
• test.compliance.metadata.support
• test.compliance.modelmbean
• test.compliance.modelmbean.support
• test.compliance.monitor
• test.compliance.monitor.support
Classes:
• PooledConnectionRegressionTest: Tests a PooledConnection implementation provided by a JDBC driver. Test case provided by Johnny Macchione from bug database record BUG#884. According to the JDBC 2.0 specification: "Each call to PooledConnection.getConnection() must return a newly constructed Connection object that exhibits the default Connection behavior. Only the most recent Connection object produced from a particular PooledConnection is open. An existing Connection object is automatically closed, if the getConnection() method of its associated Pooled-Connection is called again, before it has been explicitly closed by the application. ...
• Test_IMemberXmlRpc: Tests the IMemberXmlRpc SOAP interface. Note: this test is extremely slow. For this reason, it should be run by itself from the command-line; it should not be included in the automated JUnit tests that are run as a part of an ANT build. Here are some durations of the test when the number of members was restricted on the server-side: 10 members 0 min 44 seconds (older code) 20 members 1 min 20 seconds ( " " ) 40 members 1 min 47 seconds ( " " ) 80 members 3 min 28 seconds ( " " ) 160 members 7 min 11 seconds (older code) 405 members 12 min 32 seconds (more recent code) These durations were measured ...
• RunObject: Simplistic runner for XMLObjects. Generates a formatted document. The command line is: RunObject [options] objclass [output] The following options are supported: -dump file - Dump the DOM to the specified file. -instanceof classname - Verify that the object is an instanceof this class. This maybe repeated. -use-factory - Use a simplistic factor to get an instance of this object. -reversetext - Reverse the text in all the text nodes. Use to generate files to use in recompilation testing. SPAN IDs are also preserved. -encoding encoding - XML/HTML encoding. This will be used for output and will be ...
• CreateParticipants: This utility creates Oracle or mySQL INSERT statements to populate the Participant table. The class is meant to run from a command-line and its output may be directed to a file. This utility is meant mainly to generate test data. Participants are generated from the Member table for every entry in the RowingSession table, except for rowing sessions that are marked 'TENATIVE'. Participants are matched by type to rowing sessions: FULL members are placed in REGULAR sessions, and LTR participants are placed in LTR sessions. A member is placed at most once as participant in a rowing session. About 30 ...
• ApplicationException: Every J2EE application needs to specify custom exceptions, that are thrown by business logic. For example when validating a value set on an entity bean, this exception can be thrown. When implementing the Session Facade Pattern, these exceptions can be wrapped in a RemoteException and passed to the client. The client can then act on these in a user-friendly way. For ease-of-use this exception is in the interfaces package. When you have many more application-specific exceptions, put them in a seperate package, it improves reuse and maintainability. For more information on EJB exception handling, ...
• InteropTestDocLit: This test is part of the SOAP Builders round III interoperability testing effort described at http://www.whitemesa.net/r3/plan.html. The test is in group E which requires a service (this class) coding by hand which implements the operations, parameters, and binding style/use described in a WSDL file available from the above web site. The WSDL file is used only as a pseudo-code description of the service. Next WSDL is generated from the service and the WSDL used to create a client which is then used to invoke the service. Other vendors should also be able to use the same, generated WSDL to invoke ...
• InteropTestList: This test is part of the SOAP Builders round III interoperability testing effort described at http://www.whitemesa.net/r3/plan.html. The test is in group E which requires a service (this class) coding by hand which implements the operations, parameters, and binding style/use described in a WSDL file available from the above web site. The WSDL file is used only as a pseudo-code description of the service. Next WSDL is generated from the service and the WSDL used to create a client which is then used to invoke the service. Other vendors should also be able to use the same, generated WSDL to invoke ...
• InteropTestRpcEnc: This test is part of the SOAP Builders round III interoperability testing effort described at http://www.whitemesa.net/r3/plan.html. The test is in group E which requires a service (this class) coding by hand which implements the operations, parameters, and binding style/use described in a WSDL file available from the above web site. The WSDL file is used only as a pseudo-code description of the service. Next WSDL is generated from the service and the WSDL used to create a client which is then used to invoke the service. Other vendors should also be able to use the same, generated WSDL to invoke ...
• BasicTests: Basic test of XMLCContext. Test's creation and output of documents. Performs several tasks based on parameters: doc - Parameter control what document to use: html1name - HTML page #1 by created by class name. html1class - HTML page #1 by created by interface class (default). wml1name - WML page #1 by created by class name. wml1class - WML page #1 by created by interface class. big5name - Big5 HTML page #1 by name. touch - Parameter used to control touching page/class. none - Don't touch files (default). class - Touch class file. source - Touch source file. encoding - Use encoding.
• ComplianceSUITE: Everything under test.compliance is a set of unit tests which should pass as much as possible against the JMX RI Additions to this package are welcome/encouraged - adding a test that fails is a great way to communicate a bug ;-) Anyone contributing to the JBoss JMX impl should seriously consider providing a testcase prior to making code changes in the impl itself - ala XP. The only restriction is that if the tests don't succeed against the RI, the test error message should indicate that the test will fail on the RI (preferred way) or at least comment the testcase stating expected failures. Either ...
• GenericLocalTest: This is a framework class which handles all the basic stuff necessary to set up a local "roundtrip" test to an AxisServer. To use it - extend this class with your own test. Make sure if you override setUp() that you call super.setUp() so that the engine gets initialized correctly. The method deploy() needs to be called to deploy a target service and set up the transport to talk to it - note that this is done by default in the no-argument setUp(). If you don't want this behavior, or want to tweak names/classes, just call super.setUp(false) instead of super.setUp() and the deploy() call won't happen. ...
• TestSrcContent: This TestCase verifies that content of the source files adheres to certain coding practices by matching regular expressions (string patterns): - Verify that Log4J logger is not being used directly ("org.apache.log4j" is not in source files). - Verify that System.out.println is not used except in wsdl to/from java tooling. - Verify that log.info(), log.warn(), log.error(), and log.fatal() use Messages.getMessage() (i18n). - Verify that exceptions are created with Messages.getMessage() (i18n). To add new patterns, search for and append to the private attribute 'avoidPatterns'. Based on code in TestMessages ...
• ReadlineTest: ReadlineTest.java This class shows the usage of the readline wrapper. It will read lines from standard input using the GNU-Readline library. You can use the standard line editing keys. You can also define application specific keys. Put this into your ~/.inputrc (or into whatever file $INPUTRC points to) and see what happens if you press function keys F1 to F3: $if ReadlineTest "\e[11~": "linux is great" "\e[12~": "jikes is cool" "\e[13~": "javac is slow" $endif If one argument is given to ReadlineTest, a private initialization file is read. If a second argument is given, the appropriate library ...
• TestAutoComp: Tests for auto-compilation and class reloading. The command line is: TestAutoComp [options] interfaceName [outfile] The following options are supported: -dump - Dump the DOM to stdout. -sourcefile file - Path to the source file. The root directory of the tree containing the file must be on the classpath. This will will be overwritten. -copyfile file - File to copy over source file to generate an error or change the results. -classloader name Use the specified classloader. One of `enhydra', `multi', `url'. The directory containing
• CreateRowingSessions: This utility creates Oracle or mySQL INSERT statements to populate the RowingSession table. The class is meant to run from a command-line and its output may be directed to a file. This utility is meant mainly to generate test data. It has only one adjustable parameter -- a command-line argument specifying whether Oracle or mySQL is the target database. RowingSessions are generated through December 31 of the current year, starting from September 1 of the preceding year. There are four seasons: winter, spring, summer, and fall. See the Season interface and the Winter, Spring, Summer and Autumn implementations ...
• TimerFilter: Timer filter that logs the request processing time in milliseconds to the console. A filter is an object that performs filtering tasks on either the request to a resource (a servlet or static content), or on the response from a resource, or both. For more information on filters, check the javadoc or read the Filter code with Servlet 2.3 model article at JavaWorld .
• QueueBean: A message-driven bean based on a Queue. A message-driven bean is an EJB that acts as a message consumer in the WebLogic JMS messaging system. As with standard JMS message consumers, message-driven beans receive messages from a JMS Queue or Topic, and perform business logic based on the message contents. More info on message-driven beans can be found here: http://www.onjava.com/pub/a/onjava/excerpt/ejb3_ch13/index.html?page=5#17
• CheckClass: Check the attributes of a class. The command line is: CheckClass [options] classname The following options are supported: -instanceof classname - Verify that the object is an instanceof this class. This maybe repeated. -not-instanceof classname - Verify that the object is not an instanceof this class. This maybe repeated. -method name - Check if method name is defined (check for any method of this name regardless of signature.
• TestFaultHandler: This is a test Handler which interacts with the TestService below in order to test header processing. This one runs before the TestHandler, so when the TestHandler throws an Exception (triggered by a particular header being sent from TestOnFaultHeaders), the onFault() method gets called. In there, we get the response message and add a header to it. This header gets picked up by the client, who checks that it looks right and has successfully propagated from here to the top of the call stack.
• SimpleI18NBeanBeanInfo: BeanInfo class for SimpleI18NBean. Note: The java beans specification does NOT state that a property mutator can NOT exist with out an associated property accessor. Furthermore the implmentation of the sun bdk will look for property mutators by them self. The criteria for determining properties/accessors/mutators are determined by the JavaBeans specification, the implementation of Introspector and the implementation of the bdk not what the author or the framework thinks it "should be".
• SimpleBeanBeanInfo: BeanInfo class for SimpleBean. Note: The java beans specification does NOT state that a property mutator can NOT exist with out an associated property accessor. Furthermore the implmentation of the sun bdk will look for property mutators by them self. The criteria for determining properties/accessors/mutators are determined by the JavaBeans specification, the implementation of Introspector and the implementation of the bdk not what the author or the framework thinks it "should be".
• VerifyTestCase: This class is taken from the generated TestCase. The generated test case is still generated to verify that the generated test case is always compilable. THIS test case exists because I know this is correct. If the generation of the bindings changes, it's likely that the generation of the TestCase will change as well, so we wouldn't know whether they changed for the worse if they all changed the same. This test case should fail to compile if generated stuff changed for the worse.
• BrainFuckInterpreter: an interpreter for the BrainFuck language The Brainfuck programming language consists of eight commands, each of which is represented as a single character. > Increment the pointer. < Decrement the pointer. + Increment the byte at the pointer. - Decrement the byte at the pointer. . Output the byte at the pointer. , Input a byte and store it in the byte at the pointer. [ Jump past the matching ] if the byte at the pointer is zero. ] Jump to the matching [
• SimpleAction: Simple WebWork action. WebWork is a web application framework for J2EE. It is based on a concept called "Pull HMVC" Pull Hierarchical Model View Controller). It supports an arrange of view technologies - XSLT, JSP, Velocity, Applet, Jasper Reports, and more. Actions are central to WebWork (WW) as they are the controllers in your application. For more information, check the WebWork Documentation .
• TimerTestCase: Timer Stress Tests This test works by starting a lot of notifications at the start and checks the concurrency by performing lots of operations. It then waits for the slow notifications to complete allowing any lag due to slower computers to be caught up with. Any concurrency problem or dropped notifications should show up when the test times out and the target notifications are not reached.
| Home | Contact Us | Privacy Policy | Terms of Service |