1. INTRODUCTION
2. Testing Grid API
3. Wiki report
3. Installation Instructions
3. Advanced
What is Testing Grid?
- Testing Grid developed on top of GigaSpaces XAP platform.
- Testing Grid in short name called "TGris"
- TGris provides distributed execution of regression test suites from different types of tests (Java, .NET tests, functional tests)
- Reduces time-execution of test-suites due to its distribution and system-provisioning capabilities
- TGris works with full automation cycle 24 hours a day and without human involvement
- Integrated with ["QuickBuild" ] - continuous build-server
- Provides comprehensive reporting ( Wiki, Console, File, Custom Reporter API )
Distributed Testing Grid Architecture
Whenever more Agents connected to the TGrid the execution suite time reduce dramatically.
 |
If you wish to contribute your computer/laptop resources(CPU/Memory/HD) to the TestingGrid, install on your laptop TGrid-Agent and setup ScreenServer to launch TGrid-Agent. It means that when your computer become idle for example after 10 minutes, the ScreenSaver will start Agent and suite-tests will run on your computer.
By this way you:
- contribute your computer to be part of TGrid and help to reduce time of running test-suite.
- gain full utilization of your computer.
|
TestingGrid Lifecycle
Getting Starting with distributed JUnits
1. Download & Unzip TestGrid_1_6.0.zip
2. Go to TestingGrid/bin
3. Start ./startTGrid.sh
4. Start ./agent.sh
5. Open eclipse project and setup build classpath
6. Write a simple JUnit 4.0 test. (The current version supports only JUnit 4.0, @Test annotation should be defined on top of every test method)
6.1 Define @RunWith(TGridRunner.class) to run in TGris environment
6.2 If you wish to route your test to specific Platform, define annotation @TargetPlatformCapability Test PlatformCapability routing
7. Open run test dialog and define TGris server name by -Dtgris.server=your-tgris-server
NOTE: No needs to setup this system-property if TGris runs locally on your computer.
8. All JUnit results you can see in JUnit tab of eclipse
9. Congratulation - you successfully ran distributed JUnit.
NOTE: You don't need to setup Test classpath environment on side of Agent, TGris does it for you. When you run your JUnit test, TGris transparently scans all Test classpath environment and keeps all classpath jars in the space! The TGris server(space) become reliable classpath codebase for all Agents with jar version support. Next time when you run the same test, all Test classpath and environment will be setup from the space. If any other enduser runs any Test that require the same jars that locates in the space, all classpath will be setup from the space as well.
Wiki report
WikiReporter provides online information of executed test suite. The report created automatically right away the test-suite finished to run.
The following snapshot provides :
- Summary table of all test-suites belongs to appropriate Build version.
- Regression histogram which shows accumulated statistic information.
| This summary the client receives by email when regression finished to run.
To subscribe to get wiki notification press  icon. Add this page to the favorite list press  icon. |
Wiki mail notification
When TestSuite finished to run, ?ll subscribed clients will receive email with summary report of executed suite.
The summary table contains the following:
- Link to the regression report
- Suite status
- total test
- total defects
- success rate
- Summary of suite breakdown report
- total running tests
- total skipped tests
- total suite tests
- Build date
- The JVM type this suite executed with.
- link to the XAP installation this suite run with.
Installation Instructions
Usage Instructions
- TGris provides CLI scripts which locates under "bin" directory. All scripts for Unix and Windows
- There are 3 main scripts to start working with TGris
- startTGrid.sh - Start TGris Server
- agent.sh - Start agent
- startSubmitter.sh - Start submitter which receives as argument test-sute.jar
CLI
- To start the agents on multiple machines it's not a simple task, especially when you have more than 10 or 50 computers
- TGris comes with distributed dagent.sh script which provides launching of Agents on desired remote computers
dagent.sh provides the following facilities:
1. User friendly Wizard steps
2. Control "Agents" remotely on desired machines with desired JVM version & vendor
3. Start/Kill/Total Running
4. Silent mode - requires all arguments to disable the Wizard
NOTE: dagent requires [pdsh|www.sourceforge.net/projects/pdsh] installation and available only on UNIX.
