Getting Started - Serenity BDD
Follow this guide for a basic example of running your Serenity BDD tests on the Testable platform. Our example project will open https://www.google.com, run various searches, and capture any screenshots.
Start by signing up and creating a new test case using the Create Test button on the dashboard.
Enter the test case name (e.g. Serenity Demo) and press Next.
Select Selenium as the scenario type.
Let’s use the following settings:
- Bindings: Selenium Java
- Framework: Serenity
- Source: Build Project from Version Control. See the detailed documentation for all the options to get our code onto Testable.
We will use the serenity-example project as our source.
This project contains 3 tests that open Google and perform a search. By default Serenity will also capture screenshots after each step. See the serenity-example code for more details.
And that’s it, we’ve now defined our scenario! To try it out before configuring a load test click the Smoke Test button in the upper right and watch Testable execute the scenario 1 time as 1 user. You should see all results including logging, assertions, screenshots, network traces, etc appear once the smoke test completes.
Next, click on the Configuration tab or press the Next button at the bottom to move to the next step.
Now that we have the scenario for our test case we need to define a few parameters before we can execute our test:
- Total Virtual Users: Number of users that will execute in parallel. Each user will execute your Serenity test.
- Test Length: Select Iterations to have each client execute the scenario a set number of times regardless of how long it takes. Choose Duration if you want each client to continue executing the scenario for a set amount of time (in minutes).
- Location(s): Choose the location in which to run your test and the test runner source that indicates which test runners to use in that location to run the load test (e.g. on the public shared grid).
And that’s it! Press Start Test and watch the results start to flow in. See the new configuration guide for full details of all configuration options.
For the sake of this example, let’s use the following parameters:
Once the test starts executing, Testable will distribute the work out to the selected test runners (e.g. Public Shared Grid in
AWS N. Virginia).
In each region, the test runners execute your project’s tests in 3 separate processes concurrently for 1 minute or until it completes if it takes longer than a minute.
The results will include screenshots, assertions, traces, performance metrics, logging, breakdown by URL, analysis, comparison against previous test runs, and more.
Check out the Serenity guide for more details on running your Serenity code on the Testable platform.
We also offer integration (Org Management -> Integration) with third party tools like New Relic. If you enable integration you can do more in depth analytics on your results there as well.
That’s it! Go ahead and try these same steps with your own scripts and feel free to contact us with any questions.