Open Source Linux QA Automation Software - Page 19

SOURCE CODE MOVED TO https://github.com/kowalpy/Robot-Framework-FTP-Library . NEW RELEASES WILL APPEAR ONLY AT GITHUB AND PYPI. This Python library makes it possible to test or use FTP server using Robot Framework keywords. Together with the library, there are also available project example and keywords documentation created by libdoc. This sourceforge webpage is linked from http://robotframework.org/#test-libraries as external library so it can be considered as the official Robot Framework library.

The library provides functionality of SNMP manager which can be accessed using Robot Framework keywords. In this model, system under test is SNMP agent.

Round Trip Engineering Objects. Reverse object oriented source code (Java, C#, PHP5) into XOL (XML Object Language) DOM repository.Validate syntax using XML Schema. XSLT for code refactoring & code generation. IDE Editors available (Eclipse plugin)

S.T.R.E.S.S.(Stress Testing and Reverse Engineering for System Security) is a framework for functional testing, conventional testing and security assessment about network software and firmware device.

S3 Mockup is an Amazon S3 emulator we develop for one of our projects. It can be easy embedded and used in your test framework or running as an independent service. Using this emulator you can easy setup development and QA environment.

The SE TestManager is a tool to manage manual tests (e.g. behavior of GUI applications) in the software development process. You can create test cases and structure them in a tree. The SE TestManager guides you through the test and generates a PDF report

SHIFT (State-HIerarchy Functional Testing) provides a new way to test your web apps. It extends other web testing frameworks to allow significantly better testing with less effort, and opens up new ways to test which have never been possible before.

SISSy is a platform for problem pattern identification in OO source code written in Java, C++ or Delphi. Problem patterns include the well-known bad smells as well as typical violations of good OO design principles and heuristics.

Swing Java Application manages software requirements and associated functional tests, including results, showing requirements/tests traceability at all time. Requirements and tests are formatted as in text processor; print-ready documents are generated.

SLOCCount is an easy-to-use tool that counts Source Lines of Code (SLOC). It auto-determines the language(s) (inc. C, C++, Ada, Assembly, shell, COBOL, C#, Fortran, Haskell, Java, LISP/Scheme, Perl, PHP, Python, Ruby, SQL). It also estimates cost & time.

Simple Portable Memory Management (SPMM) is a small, easy to integrate memory management library for C++. The library emphasizes simplicity of use and implementation while guaranteeing leak free program execution.

This project is a fork of the good but abandonned RTH (stands for Requirement and Testing Hub). Our aim is to stabilize the project and then, to add extra functionnalities and link it to external softwares (Selenium, JMeter...). We'll release developper previews on a regular basis before entering alpha testing.

STDL (Structured test description language) is a domain-specific testing language that is used to auto-generate unit test code. It supports a myriad of output languages (incl. C#). The project's aim is that of reducing the resources required for testing

STDProject (Simple Tree Driven Project) is a modeling tool for software development projects. It will let you build your project, watch its consistency, generate documentation and reuse work from one project to another.

THE STP CODE HAS MOVED TO GITHUB. THE CODE HERE IS STALE. PLEASE CHECKOUT THE FOLLOWING WEBSITE: http://stp.github.io/

strunts provides tools and helpers for building web applications with struts and eclipse. it allows to validate config files, jsp's, tiles definitions and java code of the struts application.

The SVG Quality Assurance project collects tools that help to improve quality of SVG software and images.

SVN Statistika is a server-side application for generating reports (graphs, trees, tables) from subversion repository. Client-side GUI application is also avaible and is used to control the server-side.

SVNChecker is a framework for Subversion pre-commit hook scripts. See the new project page http://svnchecker.tigris.org/.

SVNFS is a FUSE filesystem for Linux that presents a read-only version of all revisions in a Subversion repository as a native mountpoint, transparent to all other programs.

A tool to automate the usage of SWT based GUI and to allow the user to test the existence of controls and check their characteristics. The users are able to perform the tests from a user interface or from a regression environment.

SWTBot is an automation and testing tool for SWT/RCP applications, with the facility to record and playback scripts. Features will include, text based scripts, ant support for playback of test suites, reporting, and multi threaded playback.

Sanity4J simplifies running multiple code analysis tools on Java projects on an ad-hoc basis. It provides a single entry point to run the tools and produces a consolidated report, which presents all findings in an easily accessible format. Homepage: https://sanity4j.github.io/ Project page: https://github.com/Sanity4J/Sanity4J/

ScaleUp is a monitoring tool, which produces report based on configured text files and keywords (such as exceptions). It is very useful to monitor log in production and testing environments.

Scertify™ Refactoring Assessment is an open source component dedicated to development & QA teams that provides exclusive benchmark data on Software Quality. It automatically detects the portions of an application that can be refactored, gives valuable information on refactoring strategies, and costs. Though IT departments have matured these last 10 years and have now no doubt on the benefits of a continuous control of code quality, three major concerns were still remaining, without any tools able to effectively addressing these needs: * How to understand quality indicators, and how to compare them with the state of the art? * How to measure and manage the gap between the absolute quality level of a software, and a reasonable (reachable) target of quality? * What are the shortest and safe ways to achieve your quality goals?