tadedon is a set of utilities that form a foundation for applications written with one of the many Java frameworks, such as GWT, GIN, Guice, Google App Engine, commons-configuration, and many others. It lets you specify the default configuration of your application and upgrade it automatically on each new release. It can redirect all java.util.logging to slf4j and easily configure logback. It can bind application configuration in a Guice module. It supports @PostConstruct and @PreDestroy annotations (JSR 250) in Guice applications. It lets you annotate your methods with @Transactional annotation. It supports Guice injector stage in your Web application. It lets you test your Guice managed servlets and filters without needing a real servlet container. It lets you use Guice Matchers for matching super class, interface, and type literal annotations. It can inject event bus to your GWT applications with the help of GIN.
OWASP Zed Attack Proxy (ZAP) is an easy-to-use integrated penetration testing tool for finding vulnerabilities in Web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing as well as being a useful addition to an experienced pen tester's toolbox. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.
Simple Continuous Integration Tools (scit) is an automated build and or test system consisting of a set of Perl and expect scripts utilizing common tools that are available for most Unix-like operating systems. The intention is to keep it lightweight while still providing a full set of features. The current version has a command-line and an HTML user interface. It should be possible to make it run on very modest hardware; part of the development and testing has been done on a Nokia N900 phone with both master and slave roles running on the same unit.
Flexmock is a mock/stub/spy library for Python. Its API is inspired by a Ruby library of the same name. However, it is not a goal of Python Flexmock to be a clone of the Ruby version. Instead, the focus is on providing full support for testing Python programs and making the creation of fake objects as unobtrusive as possible. Flexmock’s design focuses on simplicity and intuitiveness. This means that the API is as lean as possible, though a few convenient short-hand methods are provided to aid brevity and readability. Flexmock declarations are structured to read more like English sentences than API calls, and it is possible to chain them together in any order to achieve high degree of expressiveness in a single line of code.
CaptureMock provides capture-replay mocking for Python, on the command line and with client-server communication. CaptureMock's approach is a so-called capture-replay approach. This means that when you 'record' your mock, CaptureMock will observe the interaction between your code and the subsystem you are mocking out, and record it in a text file in its own format. When you then run your test in 'replay mode', CaptureMock can play the role of the subsystem in question, and the real subsystem does not need to even be installed. You can then choose, each time you run your tests, whether you wish to have the real subsystems present and verify/recreate the captured mocks, or to rely on the mocks captured by a previous run. If you are running in 'replay mode' and CaptureMock does not receive the same calls as previously, it will fail the test, and suggest that you may want to recreate the mocks in record mode.