Open Source Windows Software Testing Tools - Page 46

Simple test runner for QTestLib tests. Allows to run multiple different tests, provides interface similar to some XUnit applications, can be used with TDD (sort of). Consists of two different applications: GUI and console test runners.

This is yet another unit testing framework for C++. However, QUnit feels like 50 lines of code, integrates nicely into your development environment, and contains no bells and whistles. QUnit is more like an idiom, just implement when you need it.

Testing complex systems calls for clear task management and control covering everything from defining test plans to writing test cases and recording results. QATraq provides the framework for task management and control, across the whole test process.

Simplifies usage of Google C++ Testing Framework in Qt Creator IDE. Source code can be found here: https://github.com/OneMoreGres/qtc-gtest IMPORTANT: plugin's version must match Qt Creator's version (difference in last digit is acceptable) Then plugin must be enabled in Help->Modules menu.

Define test strategies, design test plans, execute plan-based and exploratory tests, create test protocols and manage found issues in a lightweight manner. It's for those that are looking for a lightweight, productive and structured testing process. Note: this is a community edition from 2015 (with source code) and is not maintained anymore. The latest version can be found at www.qualityspy.net

The goal of quality-check is to provide a small Java library for basic runtime code quality checks. It provides similar features to org.springframework.util.Assert or com.google.common.base.Preconditions without the need to include big libraries or frameworks such as Spring or Guava. The package quality-check tries to replace these libraries and provide all the basic code quality checks you need. The checks provided here are typically used to validate method parameters and detect errors during runtime. To detect errors before runtime we use JSR-305 Annotations. With these annotations you are able to detect possible bugs earlier. For more informations look at FindBugs™ JSR-305 support. We noticed that many projects just copy org.springframework.util.Assert or com.google.common.base.Preconditions to get access to these quality checks. Therefore we provide these features and small library that can be included in any application without big overhead.

Quantum replicates the functionalities of QC. Quantum will have the requirements, test cases, test runs, defects, RTM, TCM just as QC and will also implement custom fields. It is being developed on *AMP platform and is platform independent

QC4J is an automated, specification-based testing framework, based on QuickCheck for Haskell. It makes it easy to test referentially transparent code, by creating test data automatically through user-defined generators.

QuickMock is a library for testing C++ code using simple hand-writing mock objects.

A simple C++ unit testing framework contained within a single header file. Minimal code is required for each new test.

R Unit test framework R functions implementing a standard Unit Testing framework, with additional code inspection and report generation tools

RCPUnit is an unit testing framework, an automatic GUI testing framework, and a plugin for Eclipse RCP. It runs with PDE JUnit or other unit testing frameworks. It brings you the ability to do unit testing easily in RCP applications, and SWT application.

A robust C unit testing framework

.Net wrapper for MS Terminal Services control. Part of TAF Core distributed test automation framework (https://sourceforge.net/projects/tafcore/)

Generate a lot of random junk. Create: • huge files • random character stream • specific character sequence Example uses - generate: • specific number of characters for testing web forms • restricted range character stream • control characters, 'high characters', emojis for fuzzing application input • specific byte sequence • Unicode character range • file overwrites to the exact byte count • custom text strings as content filler • long password strings • specific file size (e.g. 777 bytes, 10 MB, 2 GB) • huge files (x64 version: 4GB+ files) • fast generation rates on x64 version: ~8GB/sec streams with i3 CPUs on Linux • files for zipping / hashing / integrity / transfer / speed tests. RND.zip contains the source code and the x86/x64 executables for Linux, Windows, Raspberry Pi.

RSpec Rails brings the RSpec testing framework to Ruby on Rails as a drop-in alternative to its default testing framework, Minitest. In RSpec, tests are not just scripts that verify your application code. They’re also specifications (or specs, for short): detailed explanations of how the application is supposed to behave, expressed in plain English. RSpec follows semantic versioning, which means that “major version” upgrades (e.g., 2.x → 3.x) come with breaking changes. If you’re upgrading from version 2.x or below, read the rspec-rails upgrade notes to find out what to watch out for. In RSpec, assertions are called expectations, and every expectation is built around a matcher. When you expect(a).to eq(b), you’re using the eq matcher. RSpec Rails defines ten different types of specs for testing different parts of a typical Rails application. Each one inherits from one of Rails’ built-in TestCase classes, meaning the helper methods provided by default in Rails tests are available.

For further information regarding RTH visit our blog at http://requirementsandtestinghub.wordpress.com/. You can learn more about the history of RTH, the current status and our Demo (Live) system for testing of RTH.

"Ra" is a testing utility wich provides numerous abilities for testers such as report generation (in different formats), statistics gathering and flexible tests running scripts and others.

Generate random values and insert them in the database. Great to test a new software or to generate meaningful dummy data. Written in PHP and uses MySQL as a DBMS.

A testing framework, based on JUnit, that allows the easy creation of randomized tests, based on Design-by-Contract principles. The programmer defines simple actions on parameters (injected by the framework), and the resulting ecosystems are verified.

Randoop is an automatic unit test generator for Java. It automatically creates unit tests for your classes, in JUnit format. 1) Randoop generates unit tests using feedback-directed random test generation. In a nutshell, this technique randomly, but smartly, generates sequences of methods and constructor invocations for the classes under test, and uses the sequences to create tests. Randoop executes the sequences it creates, using the results of the execution to create assertions that capture the behavior or your program and that catch bugs. 2) Randoop has created tests that find previously unkwon errors even in widely-used libraries including Sun and IBM's JDKs. Randoop's combination of randomized test generation and test execution results in a highly effective test generation technique. Source is stored in Bitbucket: https://bitbucket.org/javydreamercsw/randoop-netbeans-plugin

PyRAFT is a general purpose object-oriented framework meant for testers. It aims to provide an easy platform on top of which testers can build tests as per their project requirements, for testing functionality, performance and security of software.

Це віртуальна машина QEMU із зібраною операційною системою Raspbian для емуляції Raspberry Pi на Windows 7, 8, 10. Використовується для занять з робототехніки в Київському національному університеті будівництва і архітектури. pi/raspberry

Handle every connection on different windows really simple, like chatting! Whit this too you can start a server, what listens on a specific port and/or connect to a specific host name with a specific port. The incomming/outgoing connections are appearing in popup windows. Written in Lazarus

A dead simple library to screenshot test React components. Under the hood, we start a local server that renders components server-side. Each component is given its own dedicated page (e.g. /render/my-component). Then we use Puppeteer to take a screenshot of that page. If you work on a team where developers use a different OS (e.g. Mac OS and Linux), or if you develop on Mac OS but use Linux for continuous integration, you would quickly run into issues where screenshots are inconsistent across platforms. This is, for better or worse, expected behavior. In order to work around this issue, react-screenshot-test will default to running Puppeteer (i.e. Chrome) inside Docker to take screenshots of your components. This ensures that generated screenshots are consistent regardless of which platform you run your tests on.