FitNesse

specs2 @ GitHub Specify your software using both text and Scala code class HelloWorldSpec extends Specification { def is = s2""" This is a specification for the 'Hello world' string The 'Hello world' string should contain 11 characters $e1 start with 'Hello' $e2 end with 'world' $e3 """ def e1 = "Hello world" must haveSize(11) def e2 = "Hello world" must startWith("Hello") def e3 = "Hello world" must endWith("world") } Use different styles of specifications /** This is the "Unit" style for specifications */class HelloWorldSpec extends Specification { "This is a specification for the 'Hello world' string".txt "The 'Hello world' string should" >> { "contain 11 characters" >> { "Hello world" must haveSize(11) } "start with 'Hello'" >> { "Hello world" must startWith("Hello") } "end with 'world'" >> { "Hello world" must endWith("world") } }} Document your APIs with compiler-checked examples Manage contexts for integration testing

You Test It ! Watir.com | Web Application Testing in Ruby Maven - Welcome to Apache Maven Unit testing In computer programming, unit testing is a method by which individual units of source code, sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures are tested to determine if they are fit for use.[1] Intuitively, one can view a unit as the smallest testable part of an application. In procedural programming, a unit could be an entire module, but it is more commonly an individual function or procedure. In object-oriented programming, a unit is often an entire interface, such as a class, but could be an individual method.[2] Unit tests are short code fragments[3] created by programmers or occasionally by white box testers during the development process. Ideally, each test case is independent from the others. Benefits[edit] The goal of unit testing is to isolate each part of the program and show that the individual parts are correct.[1] A unit test provides a strict, written contract that the piece of code must satisfy.

Selenium - Web Browser Automation Support Older Manuals Older releases are available from the Sourceforge files section. Professional Support A lot of companies also offer professional support. WANdisco has a support forum for TortoiseSVN, which you can find here. Project Status Have a look at our project status page to see what we are working on at the moment, and to check the release history. TortoiseSVN book The TortoiseSVN 1.7 Beginner's Guide is a well written book, as its title says for beginners. Subversion book Read the official Subversion book Version Control with Subversion to find out what it's all about. A list of common problems and their solutions can be found in the FAQ. Mailing list Test-driven development Method of writing code Test-driven development (TDD) is a way of writing code that involves writing an automated unit-level test case that fails, then writing just enough code to make the test pass, then refactoring both the test code and the production code, then repeating with another new test case. Alternative approaches to writing automated tests is to write all of the production code before starting on the test code or to write all of the test code before starting on the production code. With TDD, both are written together, therefore shortening debugging time necessities.[1] TDD is related to the test-first programming concepts of extreme programming, begun in 1999,[2] but more recently has created more general interest in its own right.[3] Programmers also apply the concept to improving and debugging legacy code developed with older techniques.[4] The original description of TDD was in an ancient book about programming. 1. List the expected variants in the new behavior. 2. 3. 4. 5.

Selenium WebDriver The biggest change in Selenium recently has been the inclusion of the WebDriver API. Driving a browser natively as a user would either locally or on a remote machine using the Selenium Server it marks a leap forward in terms of browser automation. Selenium WebDriver fits in the same role as RC did, and has incorporated the original 1.x bindings. It refers to both the language bindings and the implementations of the individual browser controlling code. This is commonly referred to as just "WebDriver" or sometimes as Selenium 2. WebDriver is the name of the key interface against which tests should be written in Java, the implementing classes one should use are listed as below: AndroidDriver, ChromeDriver, EventFiringWebDriver, FirefoxDriver, HtmlUnitDriver, InternetExplorerDriver, PhantomJSDriver, RemoteWebDriver, SafariDriver For More information on Selenium WebDriver, please see the documentation and Remote Control to WebDriver Migration Notes.

www.cs.princeton.edu/courses/archive/spr05/cos126/cmd-prompt.html There are only a few Command Prompt commands that you will need to master to make it through COS 126. The following is a brief tutorial covering the most important ones. The Command Prompt program allows you to work in an environment that looks more like a traditional operating system as opposed to the icon based Windows environment. In Command Prompt, you will use your keyboard. You won't use your mouse at all. You will need the command prompt in COS 126 to compile and execute your Java programs. To launch Command Prompt select Start -> Run and type cmd in the box. The Command Prompt shows up as a black terminal window. This is where you type commands. javac: To compile a Java program, use the javac command. You can also use Command Prompt commands to organize files into a directory hierarchy. dir: To view the contents of a directory, type dir. Two important abstractions in Command Prompt are standard input and standard output. Redirecting standard input.

Cuke4Ninja: The Secret Ninja Cucumber Scrolls | Cucumber | Gherkin | Agile Acceptance Testing | Behaviour Driven Development Test Plan Sample Table of Contents 1. Introduction Description of this Document Related Documents Schedule and Milestones 2. 3. New Features Testing Regression Testing 4. 5. 6. 7. 1. Description of this Document This document is a Test Plan for the -Project name-, produced by Quality Assurance. The focus of the -Project name- is to support those new features that will allow easier development, deployment and maintenance of solutions built upon the -Project name-. [List of the features] This release of the -Project name- will also include legacy bug fixing, and redesigning or including missing functionality from previous release The following implementations were made: [List and description of implementations made] Related Documents [List of related documents such as: Functional Specifications, Design Specifications] Schedule and Milestones [Schedule information QA testing estimates] 2. Hardware [List of hardware requirements] Software [List of software requirements: primary and secondary OS] Staffing 3. 4. 5. 6. Risks