TestingBot provides a cloud of browsers and devices, ready to run your Automated, Live and Visual tests.
One of the advantages of running your Selenium tests on the TestingBot grid is that we scale depending on your needs. If you need to run 100 Selenium tests, it might take some time for them to finish if you run them one after another.
We're happy to release our first TestingBot plugin for Jenkins. Jenkins is a CI (continuous integration) system which runs your tests, with lots of options and features.
In this post you'll find a small tutorial on how to use Cucumber and Capybara to run Selenium tests on our Selenium grid.
Cucumber is Aslak Hellesøy’s rewrite of RSpec’s "Story runner". It uses plain text DSL (Gherkin), which we mentioned in a previous post (Behat and Mink), meaning you can write tests as stories.
If you haven't heard of Behat yet, it's a BDD framework which runs on PHP written by Konstantin Kudryashov. Behat is similar to Cucumber for Ruby, Lettuce for Python and SpecFlow for .NET.
You'll use Behat for functional testing, data-driven testing and API testing.
Jenkins (formerly known as Hudson) is an open-sourced continuous integration (CI) system built in Java. With Jenkins you are able to run your Selenium tests after each xx commits to your version control system, or run at a specific interval.
This week we've reached the 35,000 tests milestone so we thought it might be interesting to do some research in the statistics we've gathered during the browsers tests. We at TestingBot run Selenium tests for our customers during which we gather technical statistics about the browsers running the tests. Time per test, number of crashes, CPU/Ram usage per browser and a lot more statistics are gathered in our datastore.
When a Selenium test fails, you usually get a clear error message or trace to indicate where the problem is located. A video of your Selenium test will offer even more help in finding out just why your Selenium test failed. By video-recording your Selenium test, you can track down when and where a problem occurs.
Today we've added Android to our Selenium grid, which means you can now use our grid for mobile testing as well. We've hooked up an Android Ice Cream Sandwich emulator to the grid, which speaks Webdriver protocol.
Today we've added SMS support to our alert options. If a test fails, we can now alert you via e-mail, push notification and SMS.
In this blog post we'll highlight how easy it is to start testing websites with .NET framework 4 or .NET framework 3 and C#. NUnit is built for all .NET languages and is basically a unit testing framework. It's written in C# and integrates nicely with .NET and its features/syntax.