Systems | Development | Analytics | API | Testing

BDD testing is an Agile approach to software testing where testers write test cases in simple language that even people without technical expertise can understand. The goal of BDD testing is to increase collaboration between the technical side and the business side. The Gherkin language is a unique business-readable language used to describe system behaviors and scenarios. It is structured by 3 primary statements: Given - When - Then, with each statement describing a specific aspect of the system.

Manual testing is a type of software testing where testers evaluate software or application quality manually, without the help of automated testing tools or executing test scripts. Testers interact with the system similar to how an end user would to identify bugs, defects, and issues in the software that create friction in user experience. When a developer manually runs their application and tries out the features they have coded, they are performing manual testing.

TDD (Test Driven Development) and BDD (Behavior Driven Development) are fairly similar development approaches that both emphasize testing and collaboration, yet have major differences in focus and methodology. Simply put, in TDD, developers test first, then use the test results to guide their development, while in BDD, developers express the system behavior they want to create through Gherkin syntax, then code according to those Gherkin expressions.

Accessibility testing is the process of evaluating that a software application, website, or digital content is usable to people with special needs or unique challenges due to physical, sensory, cognitive, or developmental impairments. The goal of accessibility testing is to identify and address barriers or obstacles in the application that can prevent these individuals from effectively using and accessing the digital product.

Cross-browser testing is a type of software testing where testers assess the compatibility and functionality of a website or web application across various web browsers, platforms, and versions. It rose from the inherent differences in popular web browsers (such as Chrome, Firefox, or Safari) in terms of their rendering engines, HTML/CSS support, JavaScript interpretation, and performance characteristics, leading to inconsistencies in user experience.

As the month of May comes to a close, we’re excited to give you an overview of all the new features, improvements, and enhancements we’ve added to the Katalon platform this past month. Let’s dive right into it!

We are thrilled to announce the first of many upcoming GPT-enabled features: manual test generation in Atlassian Jira, powered by Generative AI and Katalon TestOps’ integration. This new feature enables Jira users to generate test steps from a single button click within Jira issues.

End to end and integration testing are both critical in creating comprehensive test automation, yet they offer different focuses and scopes. In this article, we’ll guide you through the fundamentals and key differences of these two types of testing.

In software testing, a test plan is a must-have. A well-defined and comprehensive test plan provides all stakeholders involved with necessary information of the testing roadmap. Through it all members gain a shared vision for the testing approaches, strategies, objectives, resources, and timelines. In this article, we will deep-dive into what a test plan is, why it is so important, and how to create a good test plan that truly improves the overall efficiency of your testing activities.

Synthetic monitoring is a form of application monitoring that uses synthetic automated test scripts to simulate user behavior and interactions with applications and services. Synthetic monitoring involves creating scripts that simulate user actions such as page loads, form submissions, and button clicks. These scripts can then be run continuously or at scheduled intervals to monitor the performance and availability of applications and services.