Working with legacy integration test frameworks can lead to bloated, slow and flaky automated frameworks. here, we'll examine how to address the issues and some possible solutions.
read more →

This series will cover a couple of obstacles or complications you might run into when writing UI tests for iOS and will give advice on how to write cleaner tests. The third and last part will show how you can use page objects to structure your tests in a sustainable way.
read more →

This series will cover a couple of obstacles or complications you might run into when writing UI tests for iOS and will give advice on how to write cleaner tests. The second part will explain how to correctly access views in tests.
read more →

This series will cover a couple of obstacles or complications you might run into when writing UI tests for iOS and will give advice on how to write cleaner tests. In the first part we will look into possible issues with testing custom views.
read more →

Welcome to another Novoda ‘2-minute Q&A’. This series gives you insights into some of the challenging scenario's and ideas that we deal with day to day in the world of Novoda's Engineering, Product and agile Software Crafting. Today we have JT our Head of Quality Assurance, having managed
read more →

With a new year comes a new start. At Novoda we are always learning but the new year is a great milestone for starting a new project. What are some of our engineers up to in 2018? 2017 was an amazing year, we spoke publicly about our Novoda Craft University
read more →

Alright, you’re a mobile software test engineer and you want to get some test devices in house. But your boss has the purse strings pretty tight, as they do sometimes. That’s fine. It’s up to you to convince the powers that be that you need them. Let’
read more →

Mobile applications are complex software systems. Automated tests can help to ensure reliability, which leads to satisfied customers - an essential ingredient for any successful product. What if you could write tests that document requirements and features in a way that everyone involved in a project could understand? If tests
read more →

In the previous post, we wrote the acceptance test as a first step and started creating the most external classes of our implementation. In this post, we will finish implementing the system, and will summarize what we have learnt during the process. To finish the BankAccount class, we need to
read more →