Open Source Performance Testing Software

The package 'epyunit' provides extensions for PyUnit and PyDev. * Extensions for PyUnit - Unittests for arbitrary executables. * Extensions for PyDev - Automation of search and load of pydevd.py The extensions are applicable from commandline and/or within Eclipse. Online manuals: - https://pythonhosted.org/epyunit/ PyPi repository: - https://pypi.python.org/pypi/epyunit Current application examples are: - bash-core - http://bash-core.sourceforge.net Nickname - Dromi https://en.wikipedia.org/wiki/Dromi

In order to assure software performance, software needs to be tested accordingly as early as possible - only weaknesses diagnosed early can be assessed quickly and cheaply. ContiPerf enables performance testing already in early development phases and in an easy-to-learn manner: A developer writes a performance test in form of a JUnit 4 test case and adds performance test execution settings as well as performance requirements in form of Java annotations. When JUnit is invoked by an IDE, build script or build server, ContiPerf activates, performs the tests and creates an HTML report. The report provides a detailed overview of execution, requirements and measurements, even providing a latency distribution chart. A large feature set for execution settings and performance requirements is available, e.g. Ramp up, warm up, individual pause timing, concurrent exection of test groups and more.

The software program (SarBox) parses and analyzes SAR data in charts or text formats. SAR is cumulative activity counters in the operating system. It is the most comprehensive command which helps to monitor performance of various Linux / Solaris subsystems (CPU, Memory, I/O, Disk, Network, etc) all in same log. This makes it difficult to analyze since every counter data is dumped into the log file. SarBox helps to analyze this log file and present data in graphical charts or text format. To collect sar statistics from an environment, use below syntax [user@host ~]# sar -A 30 2 > sar_linux.log “30 2” reports for every 30 seconds and total of 2 times, written in sar_linux.log.