serenity-js
A next generation, full-stack acceptance testing framework optimised for collaboration, speed and scale!
APACHE-2.0 License
Bot releases are visible (Hide)
Published by jan-molak over 7 years ago
1.0.0 (2017-02-10)
Bug Fixes
- core:
- deps: Pegged Protractor to 5.0.x until backwards compatibility issues intrduced in 5.1 (8c799972)
-
interactions:
Seeis no longer reported by default, as that polluted the report and triggere (3b7efb81) -
serenity-cucumber: The
tagsparameter incucumberOptsis now correctly typed as a list of strin (abdeddad) - serenity-mocha: Pending scenarios with no steps are correctly marked as pending instead of passi (a593a84d)
Features
- integration: Stand-ins enable taking screenshots when there are no Actors on the Stage. (786b3373)
-
screenplay: The actor can now
TakeNotesto assert on their contents later. (ab368276, closes #24) - serenity: SerenityProtractorFramework takes care of executing cucumber and mocha tests. (6cf0197a)
- serenity-mocha:
- serenity-protractor:
Breaking Changes
- JSONReporter is now superseded by a cleaner and more focused implementation -
SerenityBDDReporter, which better handles gathering results from tests executed in parallel.
(0b93ff0d)
- SerenityProtractorPlugin is now removed in favour of the much more flexible SerenityProtractorFramework.
You can use the SerenityProtractorFramework instead of the mocha or the protractor-cucumber-framework modules
as it provides capabilities equivalent to those modules, and also enables an easy integration with Serenity/JS
as well as synchronisation with the WebDriver ControlFlow so that the test reports will show accurate timing.
To enable the framework, add the following configuration to your protractor.conf.js file:
exports.config = {
framework: 'custom',
frameworkPath: require.resolve('serenity-js'),
serenity: {
dialect: 'cucumber' // or 'mocha'
},
specs: [ 'features/**/*.feature' ],
cucumberOpts: { // or 'mochaOpts'
},
Both cucumberOpts and mochaOpts don't need to change as SerenityProtractorFramework can act as a drop-in replacement.
Please see the todomvc-protractor-cucumber and todomvc-protractor-mocha example project for details.
BREAKING CHANGE: The serenity object should be used instead of the Serenity singleton to initialise
the stage and the actors.
Instead of:
import { Serenity } from 'serenity-js';
const stage = Serenity.callToStageFor(cast);
use:
import { serenity } from 'serenity-js';
const stage = serenity.callToStageFor(cast);
Tutorials and more documentation to follow shortly!
(6cf0197a)
Published by jan-molak over 7 years ago
<a name"0.10.2">
0.10.2 (2017-01-22)
Bug Fixes
- serenity-cucumber: Cucumber data table and docstring steps are correctly reported (053955df, closes #14)
Examples:
Data Tables
Cucumber Data Tables are handy for passing a list of values to a step definition:
Scenario: Serenity/JS reports DataTable steps
Given the following accounts:
| name | email | twitter |
| Jan | [email protected] | @JanMolak |
| John | [email protected] | @wakaleo |
and that's what they'll look like in your Serenity Report:
Doc Strings
Doc Strings are handy for passing a larger piece of text to a step definition.
Scenario: Serenity/JS reports DocString steps
Given an example.ts file with the following contents:
"""
export const noop = (_) => _;
export const sum = (a, b) => a + b;
"""
Doc Strings are now reported too:
Show your support, give Serenity/JS a star! ★
Published by jan-molak almost 8 years ago
<a name"0.10.1">
0.10.1 (2017-01-20)
Bug Fixes
- ci:
- coverage: Fix coverage reporting to include files not required from specs (f40a8dc4)
- cucumber: Add support for generators as step definitions (30fd6528, closes #9)
- reporting: JSON report is generated even if we couldn't capture a screenshot (f230239e)
Features
Published by jan-molak almost 8 years ago
0.8.0 (2016-12-29)
Bug Fixes
- interactions: Enter.theValue(v: string | number) (c04c5e68)
Features
- interactions:
Examples
There are two ways you can wait for things to happen in your test scenarios:
PassiveWait
To make your test wait using a PassiveWait (an equivalent of browser.sleep() in Protractor):
actor.attemptsTo(
Wait.for(Duration.ofMillis(500)), // we *assume* that the button will show up during 500ms
Click.on(InboxNavigation.Compose_Button)
)
Please bear in mind that by using a PassiveWait in your test scenario, you're making an assumption that whatever the condition you're waiting for is, it will be met within the specified timeout. If this assumption turns out to be incorrect (because of the network being slow for instance), your test might result in false negatives. Please try to use ActiveWait instead as it's less prone to assumption-related issues ;-)
Why did I introduce PassiveWait then? Because it's useful with things such as CSS3 animations.
ActiveWait
To make your test wait using an ActiveWait (so actively polling the app until the condition is met):
actor.attemptsTo(
Wait.until(InboxNavigation.Compose_Button, Is.clickable()),
Click.on(InboxNavigation.Compose_Button)
)
To specify the maximum timeout:
actor.attemptsTo(
Wait.upTo(Duration.seconds(10)).until(InboxNavigation.Compose_Button, Is.clickable()),
Click.on(InboxNavigation.Compose_Button)
)
You might also want to check out the Is class to see what conditions are already defined and find inspiration to write some of your own.
Hope you find the new features useful!
Jan
Many thanks to @npryce for suggesting to introduce the Duration class ✋
