Behat — BDD for PHP NUnit - Home collectiveidea/json_spec Publisher: RSpec - Relish RSpec is a Behaviour-Driven Development tool for Ruby programmers. BDD is an approach to software development that combines Test-Driven Development, Domain Driven Design, and Acceptance Test-Driven Planning. RSpec helps you do the TDD part of that equation, focusing on the documentation and design aspects of TDD. Documentation This is the official documentation site for RSpec. Much of the documentation you see here is written with Cucumber, which, like RSpec, provides executable documentation. You can also find full API documentation for each sub-project at: Mailing list rspec google group Upgrading from RSpec 2.x We've put a lot of effort into making the upgrade process from RSpec 2.x to 3.x as smooth as possible, in spite of the fact that it's our first chance in over 3 years to intentionally make backwards-incompatible changes. Help make this documentation better! Please submit feedback (and patches!)
bmabey/database_cleaner etorreborre/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
Gauge | ThoughtWorks protractor/docs/getting-started.md at master · angular/protractor Documentation·Cucumber Cucumber supports over a dozen different software platforms. Every Cucumber implementation provides the same overall functionality, but they also have their own installation procedure and platform-specific functionality. The features that are common to all Cucumber implementations are documented in the reference manual. If you're looking for a reference implementation of "cucumber" using the latest "gherkin"-parser, have a look at microcuke. It's a tiny reference implementation in about 500 SLOC that can be ported to a new language in a day or two. Use the table below to find the Cucumber implementation that works for you. Here you will find platform-specific installation instructions and documentation.
GXUnit GXUnit Es un intento de crear una herramienta con funcionalidad similar a Nunit o Junit, adaptada a la realidad de Genexus. Por ahora podria utilizarse para crear TEST de objetos Procedure. El la version YI, podriamos testear Transacciones. WEBPanels sin campos de entrada, podrian testearse con el webwrapper. Workpanels, serian complicados de testear, pues mezclan mucho la interfaz con la logica. La primera etapa seria, hacer un framework de pruebas, para procedimientos La segunda, seria ayudar a generar los programas de test, con Patterns (Simple Test Pattern) La tercera, para la que hay que esperar a la Version YI, de Genexus, seria probar las transacciones. Para lograr mejores resultados y no tener que programar en codigo nativo con genexus, seria bueno contar con comandos del tipo dentro de los disponibles con Genexus. Algo mas de info, aqui Comentarios GXUnit es una herramienta super necesaria para adaptar Extreme Programming a GeneXus , muy buena la idea. Proyecto GxUnit 1) Alcance 3.1.
ruby - rails: how to unit test a json controller Fixtures and factories RSpec Testing Framework with Ruby - The testing world is a very big place. There's an entire ecosystem of tools to help solve common problems and pain points. Throughout this chapter I'm going to introduce you to some of the most common tools. After you learn the fundamentals of testing in RSpec, this is the area where you should continue your education and growth. We'll begin by talking about Fixtures and Factories. We've seen how you can create new objects and save them to a database while you're working in RSpec. However, you may find at some point that you're having to populate several tables with data during the set up for an example. When you're test sweep first starts up RSpec will use those fixture files to prepopulate your database tables. Each one is a key value pair with a colon in between. For example, if I have a customers fixture file that has Bob listed in it, then in an orders fixture file I can have an order that belongs to Bob, by specifying customer: bob.