CucumberStudio is a collaborative testing platform in the cloud that allows the software delivery team to co-design acceptance tests. It provides a real-time environment for designing, executing and refactoring tests. Ultimately CucumberStudio enables to automate tests that become the living specification of your Apps.
CucumberStudio is intended to be used by everyone in a software delivery team: customers, domain experts, product managers, testers and developers.
First of all, we think that tools should not constraint you to adopt a specific process. And in today’s world of continuous deployment, development processes are evolving quickly. So we have designed CucumberStudio to be open and flexible. Adopt the process that is right for you.
Before you begin, here’s a quick run down on all the major terms and concepts used by CucumberStudio:
A sequence of steps that represents one behavior of the application as expected by the user. A scenario may be either manual and/or automated.
A sequence of steps that can be reused across multiple scenarios like a function. It defines the Domain Specific Language (DSL) of the project. It is the common language shared by the team and used as building blocks to create scenarios.
For a scenario with parameters, it is possible to define several sets of values, that is, a datatable. A test will be generated for each set of values.
If a scenario has no datatable, it will generate one test. If a scenario has a datatable with N sets of values, it will generate N tests. So basically, the scenario is a higher level desciption of the behavior of the application. It generates one or more test instances that will be executed.
A test run is a collection of tests you want to execute. For each test of a test run, you can add one or more test results to keep track of your test execution progress.
An open source application that generates scripts for various test automation frameworks like RSpec, JUnit, TestNG, Robot Framework, Cucumber, and so on.