Systems | Development | Analytics | API | Testing

Hello to the Testhouse family! This is my second blog in a series of posts aimed at sharing insights into things I have learned or experienced in my career in testing to date. If you find anything that sparks your interest or have follow up questions, then please do let me know. In my last blog, I touched on mentorship, conferences, and the value of networking. This blog continues the mentoring theme and focuses on the benefits of having a mentor, and how you can go about finding one.

Test-driven development, or TDD, is a testing method where you first convert the feature requirements to tests and then write code to make the tests pass. In this article, we take an objective look at test-driven development, its benefits, downsides, and best use cases.

The mobile market is changing rapidly, from the explosive growth of apps and devices to the evolving complexity of software errors. The digital experience is now primary to our everyday lives.

We recently talked with one of our clients and asked him about some recommendations to get introduced in practicing Test Automation. He advised us that he always requires an acceptable application under test whenever he needs to undertake some test automation-related exercise or proof of concept. There are a hundred various sample apps available, and it might be difficult to find a nice app while not wasting too much time on it.

We’re pleased to announce that we are delivering the following Tricentis product updates across our entire portfolio. Updates have already begun rolling out and will be complete by June 10th.

Companies acquire enterprise SaaS applications (such as Microsoft Dynamics, Salesforce, ServiceNow or Workday) to accelerate business capabilities. However, the complexity increases as businesses begin to customise and integrate solutions to suit their business requirements. So, the cost of overlooking testing the application can be catastrophic in the form of monetary and reputational damage.