Category: QA

At Caplin, dev days offer an opportunity for engineers to take a break from their routine tasks, to delve into a side project or experiment with a new technology. During my recent dev day, ...Read More

Here at Caplin, we loosely adhere to the principles of the testing pyramid. That is, we limit the number of tests that are typically time consuming (to write, run and maintain) and ...Read More

This month, Caplin held its biannual hackday event. Developers got into teams of up to 3 and had 24 hours to produce something befitting this year's theme: Speed. Along with my colleague Andrew Voneshen we formed the team “Driving Miss ...Read More

Coverage identifies the parts of the codebase that do not have tests. Five questions often arise in software development and test automation: Can I refactor my code quickly and safely? Is my application robust? Will it break under certain conditions? ...Read More

QAFFL is nothing to do with Harry Potter, despite the name and possible Quidditch connection. In fact, it is a one day conference focusing on QA in Finance: a series of talks ...Read More

On 6th April 2018 the first AppiumConf was held. This was the first conference specifically about Appium, the mobile testing tool based on Selenium. Fittingly, the keynote was from two founders of the Appium project. They took us through the brief history of Appium, and ...Read More

The Caplin Integration Team has recently started creating our latest set of adapters used for internal testing and demos. For this version of our mock adapters we opted to go with Kotlin as our primary language. This has ...Read More

This blog is based on the talk presented by Antony Marcano on Screenplay pattern, in Selenium conference 2016. I have also looked into some tutorials online (listed at the end), which also contributes to some contents below and my better ...Read More

On November15-16th, several members of Caplin’s QA team attended the Selenium Conference, an annual conference about Selenium Testing tool and best practices. As someone who is relatively new to Selenium but has been Dev-ing for about 3 ...Read More

"org.openqa.selenium.WebDriverException: Element is not clickable at point (411, 675). Other element would receive the click: ..." The above-mentioned error message is well known by most QA and developers, who work with Selenium. Sometimes it makes perfect sense, ...Read More