Systems | Development | Analytics | API | Testing

Being a manual tester is a mentally-taxing career. It is basically part of the job to be stressed out by the number of tests and stretched thin by tight deadlines. In the middle of this chaos, have you ever wondered ”Shouldn’t this huge amount of tests be automated?”.

What: Katalon is deprecating its embedded script repository based on uploads of.ZIP files. Why: Katalon wants to encourage QA teams to adopt industry best practices by using generally available version control systems as script repositories. Katalon has integrations available for a number of the most popular Git-based repositories. Who is affected: All users that have imported.ZIP-based repositories into Katalon TestOps and Katalon Studio instead of integrating to version control systems.

With thousands of different web browsers, operating systems, and device combinations available, it’s impossible for software companies to control their users’ environments. All of these choices put the control in the hands of the user: if your web application or website is glitchy or looks bad on the browser they use, then you’ve probably lost that user as a customer.

In the previous article, we walked through an example of how to query and retrieve data from a MySQL database using the native MySQL C API and then compared that to the clean simplicity of using the SourcePro DB API. In this article, we are going to take that a step further and look at input parameter binding. Building off the system we discussed previously that manages the accounts for a credit card system, we are now going to implement a simple application that can add transactions to an account.

When it comes to introducing and scaling automated testing, QA teams can get quickly overwhelmed trying to figure out what processes to automate first, which tests stand to gain the most ROI, and how automation can work with manual testing strategies. Teams often look to general frameworks, like the test automation pyramid, to dive into building their automated testing strategy.

Quality software starts with code review, but quality doesn’t begin and end with code. Documents and artifacts need proper attention to make sure nothing slips through the cracks. To ensure quality software, it's essential to review the software artifacts left behind from the code review process. If code review is the unglamorous task of eating your vegetables, artifact review might as well be getting your 10,000 steps in. Both can be downright boring, but they're good for you.

When you're in the early stages of launching a startup, rapid iteration and determining product-market fit should be your top priorities. Unless you know exactly what you need to build, you should write code quickly only to discard it later. Working on test automation doesn't really fit in at this early stage. However, as you develop your product and gain customers, you will need to expand your testing infrastructure or risk losing customers and acceleration.

In this article, we will cover questions, which can help you prepare well for an interview for software testing jobs.

Our customer is a Central European Bank that is a leader in innovation. Last year alone, they became the best digital bank among 300 registered banks from around the world. To this very day, they have received 130 awards from 30 authorities. In the past, this Bank was the first in the country to offer products and services like credit cards and internet banking, which are taken for granted today.