<img height="1" width="1" src="https://www.facebook.com/tr?id=&amp;ev=PageView &amp;noscript=1">

Posted by Vicky Walker
Thu, Mar 9, 2017

 

Here at LoansWithNoCreditCheck we are on the lookout for a talented Senior Automation Tester to join our Stockport based office. 

Posted by Adam Grzegorzewski
Wed, Mar 1, 2017

Parameters can be passed to a simulation from the command line or from the launch script gatling.sh

Posted by Adam Grzegorzewski
Tue, Feb 28, 2017


Gatling is an open-source load testing tool based on Scala. It is aimed to be easy to use, supports HTTP, WebSockets, JMS, and utilises a DSL when coding scenarios and simulations.

Posted by Jan Machacek
Mon, Nov 28, 2016

Posted by Mark Harrison
Fri, Sep 2, 2016


Simply put: Chaos testing (excellently explained by  & ) is the discipline of proving the reliability of a distributed system by causing “chaos”.

Posted by Tudor Zgureanu
Wed, Aug 31, 2016

ScalaTest 3.0.0 was recently released. Being a major release it brings lots of features, changes (some of them potentially breaking) and new deprecations.
In this post I will focus more on the main additions and enhancements, followed by some code examples.

Posted by Jan Machacek
Sun, Jul 3, 2016

Posted by Michal Janousek
Mon, Mar 21, 2016


 

I have been using / on a project and it makes sense to leverage the typesafety of using the  library which is as they say, "Reactive type-safe Scala DSL for Cassandra". A couple of months ago version v1.19.0 was released which has deprecated the testkit. After updating to new version it has broken all the existing tests in our project. Phantom has good documentation on the wiki pages so I don't think that it is necessary to describe how to use it. But the documentation hasn't been updated recently. So I think it is a good opportunity to describe how to write the tests, as well as showing how to run the test using embedded cassandra.

Posted by Eslam ElHusseiny
Wed, Jan 27, 2016

Posted by Samuel Durand
Thu, Aug 20, 2015

Welcome to the second article of this series about improving the clarity, quality and reliability of tests in general, and unit tests in particular. In the first article last week we talked about the DRY and DAMP principles. Today we are going to discuss testing a piece of code depending on the configuration and about writing asserts and scenario-style tests. 

Recent Posts

Posts by Topic

see all

Subscribe to Email Updates