Displaying 1 to 12 from 12 results

FluentLenium - FluentLenium is a website automation framework which extends Selenium to write reliable and resilient UI functional tests

  •    Java

FluentLenium makes the writing of acceptance testing more easy and in a fluent way using the power of css selectors. Build upon Selenium WebDriver. goTo("http://www.bing.com"); $("#sb_form_q").fill().with("FluentLenium"); $("#sb_form_go").submit(); assertThat(title()).contains("FluentLenium");

Spock - Another Haskell web framework for rapid development

  •    Haskell

Since version 0.11.0.0 Spock drops simple routing in favor of typesafe routing and drops safe actions in favor of the "usual" way of csrf protection with a token. Since version 0.7.0.0 Spock supports typesafe routing. If you wish to continue using the untyped version of Spock you can Use Web.Spock.Simple. The implementation of the routing is implemented in a separate haskell package called reroute.

spock-spring-boot-example - An example of testing Spring Boot application with Spock framework

  •    Groovy

This is an example of Spring Boot app tested with Spock framework. These are component tests using the constructor mock injection.

funblog - A simple blog software written in Haskell

  •    Haskell

This repository also provided the material for my talk at BobKonf 2015 Berlin (German). Please note that this software is NOT intendet to be used in production (yet?).




gathering - A self hosted website for announcing group events. Currently powers:

  •    Haskell

Gathering is a self hosted website for announcing group events. This project is also an excuse for me to learn about web development.

allure-java - Allure integrations for java test frameworks

  •    Java

The repository contains new versions of adaptors for JVM-based test frameworks. All the artifacts are deployed to https://dl.bintray.com/qameta/maven.

testcontainers-spock - Spock extension for using Docker containers in Spock tests

  •    Groovy

Spock extension for TestContainers library, which allows to use Docker containers inside of Spock tests. Specifying the @Testcontainers annotation will instruct Spock to start and stop all testcontainers accordingly. This annotation can be mixed with Spock's @Shared annotation to indicate, that containers shouldn't be restarted between tests.

Unroll - A helper tool to easily run the same tests against multiple data with verbose output.

  •    Javascript

A helper tool (for browser and node tests) to easily iterate through test data against a single test method with output about each test iteration and its parameters. Or in other words a helper method to parameterize your tests. It is an attempt to provide similar behaviour to the [Unroll annotation] (https://spockframework.github.io/spock/docs/1.0/data_driven_testing.html#_method_unrolling) from Spock.


job-dsl-sample - Jenkins Job DSL Sample Project

  •    Groovy

Sample project for a Jenkins Job DSL setup with Gradle. This starts up Jenkins using Jenkins Test Harness and runs the Job DSL scripts in the jobs directory. A very simple Spock test checks that no exception is thrown. Real world setup might want to use some more advanced tests, but this gives you a starting point for an initial setup. Additionally, the generated job config files are saved to the directory build/xml.

prosper - A Spock-based integration testing library for prosperous AEM development.

  •    Groovy

A Spock-based integration testing library for Adobe Experience Manager.

babel-plugin-gwt - Data Driven Testing babel plugin inspired by Groovy's Spock framework 🖖

  •    Javascript

Writing clean descriptive tests can sometimes be difficult and cumbersome. This plugin provides syntactic sugar to make writing well documented data driven tests easy and enjoyable.

cjp-examples - Examples from the Checking Java Programs book and videos

  •    Java

I’ve been an advocate of advanced techniques and strong testing for most of my life as a software developer. This repository was first set up in 2007 (in CVS; moved to GitHub in 2015). It was originally built with Ant but has mostly been moved to Maven to simplify classpath. Classpath is also the reason I chose to split this repo into multiple projects, each an Eclipse project and a Maven-buildable project. Otherwise the classpath (and the Maven pom file) would become overly large. Not everything builds or runs at the moment: patches welcome; complaints, not so much. A few parts of this will indeed likely stay on Ant because one or two of the tools are only available as Ant plugins. While I do know about the maven-ant-plugin, it’s still just easier this way.