Identify Test Environment Hardware and Software

Recommended guidance

The last part ofDocument the test definition concerns thecomplete test environment itself.before Therunning goalscalability isor toperformance followtests. commonlyResults used,are well-known,only useful when the hardware, software, network, data, monitoring, and publishedAIQ bestexecution practices. Hereconfiguration are theknown choicesand for the test environment:repeatable.

Capture these details

• Application servers, databases, caches, queues, load balancers, and external dependencies.

• Server Hardware - the fastest, least expensive server hardware with the best performance. For example, in 2007, this would be a rack-mounted IBM 4-CPU Intel Xeon 2.8 GHz model 873 server with 4 Gbytes ofCPU, memory, dualdisk, Gigabitnetwork, Ethernetoperating adaptors,system, runtime, browser, and runningdriver Windowsversions.

• AIQ 2003version, ServerTest -Node Servicecount, Packnode 2sizing,

browser

Server Load-Generating Consumers - a white-box no-name rack-mounted 2-CPU Intel Xeon 2.1 GHz with 2 Gbytes of memory, dual Gigabit Ethernet adaptors,mode, and runningexecution Windowsgeography.

Data 2003volume, Serveraccount -pool, ServiceDPL/CSV Packsources, 2.and Thesecleanup/reset systemsprocess.Monitoring aretools, referredmetrics, tolog aslocations, TestNodesand dashboard links.

Client-Side Load-Generating Test-Automation Framework - Appvance IQ comes with a commercial software package supported by a large user community. The kit comes as a set of Appvance IQ files, but

Why it should be possible to implement the test scenario using any commercial or commercial performance tools

matters

JAVAEnvironment Virtualchanges Machinecan -explain thedifferent BEAresponse JRockittimes, JVMerror 1.5 to operate the server-side test software, where past performance testing on JRockit showed speedrates, and stability.scalability Additionally,limits. countlessRecord datachanges centersbetween showcalibration, manybaseline, JAVA application servers being run on JRockit

JAVA Specific Optimizations - the consumerstress, and serverfinal systems' memory was expanded to 4 Gigabytes (the PC's full capacity). Setting the –Xms and –Xmx memory settings to the same large number

Execution Setup - logging, debugging, and monitoring components are disabled to reduce overhead and after each scenario, all servers are restarted to clean up resource allocations

At this point, the test is well defined to begin coding the necessary use cases. The definition phase has been completed,runs so building the test environment and installing the test are the next steps. Once this has been done, the server’s maximum capacityresults can be tested.

compared

Using the XSTest-Pattern for Performance Tests

When testing Internet applications for scalability and performance, the sheer number of test cases in the test scenario makes it necessary to use test automation. An approach to test automation is a pattern, called XSTest and it is a feature of Appvance IQ. XSTest takes a test sequence – such as the scenario in The Test Scenario – as input, stages each test case in sequence, and records the transaction results in an XML-based log file. The XSTest implementation in Appvance IQ then tallies the results from the log file into a TPS report. XSTest Sequence Diagram Showing How a Test Scenario is Run illustrates the XSTest pattern as a UML sequence diagram:

XSTest Sequence Diagram Showing How a Test Scenario is Run

fairly.

One of the key advantages of the XSTest pattern is its use of jUnit TestCase objects. These are familiar to most developers and also easily learned. The kit implements the tests as TestCase objects for use in the load test and reuses them as functional tests.