Serenity (previously known as 'Thucydides') is a library designed to make writing automated acceptance tests easier, and more fun.
Serenity helps structure your automated acceptance tests in order to make them easier to understand and maintain, and provides great reporting capabilties on top of tools like JBehave, Cucumber or JUnit. It also provides tight integration with WebDriver, to make automated web testing easier and more efficient.
Serenity works in two ways:
- It instruments your test code and reports on the steps that your tests execute to achieve their goals, and stores the test results in a standardized format;
- It aggregates these test results into clear and meaningful reports, that reflect not only the outcomes of your tests, but also the status of your project. For example, you can get Serenity to report on what requirements, features or stories you have implemented, and how well (or not) they were tested.
Serenity was originally called Thucydides, and the package structure still reflects this history. Thucydides is discussed at length in the BDD in Action under the name Thucydides - everything discussed in "BDD in Action" is directly applicable for Serenity except for the artifact names.
Thucydides was renamed Serenity in November 2014, and moving forward, all new work will be done on Serenity. The artifact names reflect this change, e.g.
- net.thucydides:thucydides-code becomes net.serenity:core
- net.thucydides:thucydides-junit becomes net.serenity:serenity-junit
- net.thucydides:thucydides-jbehave becomes net.serenity:serenity-jbehave
- net.thucydides:thucydides-cucumber becomes net.serenity:serenity-cucumber
and so on.
Serenity uses a three-digit version number notation, with the following meaning:
<major>.<minor>.<build>
The first and second digits are for more significant updates, including new features or important bug fixes. The third is updated automatically for every new release, and is generated by the build process.
Commit messages are used to generate the release notes for each release. To do this, we loosely follow the AngularJS commit conventions: for commit messages to appear in the release notes, the title line needs to respect the following format:
<type>: <message>
where is one of the following:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug or adds a feature
- perf: A code change that improves performance
- test: Adding missing tests
- chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
Also commits can consists of several lines - to include some additional information in relase notes. For example:
feat: A new feature to make something better
now it will be available to call api.function() with additional parameters like api.function(Integer)
it will be included in release notes as:
-
feat: A new feature to make something better
now it will be available to call api.function() with additional parameters like api.function(Integer)
Please take a look at release notes to find some more examples of mutiline commits.
For more information, read the Contributing guide for this repo.
Starting from version 1.1.26, any commits without one of these prefixes will not appear in the release notes.
This distribution, as a whole, is licensed under the terms of the Apache License, Version 2.0
If you have found a defect, we are keen to hear about it! But there are a few things you can do to help us provide a fix sooner:
Simply saying "The reports don't get generated" will not help us very much. Give as much context as possible, including:
- Serenity version (serenity-core and the other serenity libraries, such as serenity-cucummber and serenity-jbehave)
- If you are using Firefox, firefox and geckodriver version
- If you are using Chrome, chrome and chromedriver version
- What Operating System are you using
Also, make sure you try with the latest version of Serenity - your bug may already be fixed, and in any case error messages from the latest version will be more relevant when we try to track down the source of the problem.
It is easier for us to fix something we can see breaking. If someone has to volunteer an hour of there time to reproduce a defect, Start of with one of the Serenity started projects (like this one and add a scenario or test case that both illustrates and describes your issue. If possible, write the test to describe the behaviour you expect, so that it fails when the defect is present, and that it will pass when the defect is fixed.
The fastest way to fix a defect is often to dig into the code and to submit a pull request.
If you are using Serenity for your company projects, and need faster or more in-depth support, why not ask your company to get some commercial support? We provide a range of support options including prioritied tickets, custom Serenity work, and remote mentoring/pair programming sessions, depending on your needs.
Take a look at this article for more information.