Open Source Model-Based Testing Tools
Model-based testing is a software testing approach that is based on models of the system under test and its environment to define, manually or automatically, the test cases.
functional testing
Tutorials, articles, tools and resources on how to apply functional testing in software testing
Cross-Browser Testing Tools (Free, Open Source, Paid)
When today’s applications run on various browsers (Chrome, Firefox, Safari, Edge, etc.) on different mobile or desktop devices with specific screen settings. This is why you need to perform cross-browser testing for your automated tests. This article lists the main cross-browser testing tools available today.
Self-Healing Automated Tests
Self-Healing Tests is an approach in which machine learning helps with the maintenance of automated tests. Self-Healing, the automation of test automation, recognizes changes in the “system under test” and automatically adapts the test execution so that the tests remain functional.
Pitfalls and Anti-Patterns of the Test Pyramid
The test pyramid is a concept invented in 2012 by Martin Fowler and defined as “a way of thinking about how different kinds of automated tests should be used to create a balanced portfolio.” The Test Pyramids is a common way to define and structure your test strategy, to organize the different test techniques, tools, and to manage the test automation effort.
Benefits of Test Automation in Salesforce
Salesforce is a major software player in the field of customer relationship management (CRM) and customer service software. This article discusses the specific challenges of automated testing for Salesforce applications and provides best practices for implementing test automation in this domain.
Introducing Cerberus Open Source Test Automation Framework
Cerberus Testing is an open source low-code test automation platform. It supports testing Web, iOS, Android and API (REST, SOAP and Kafka) applications and integrates with Selenium, Appium and other testing tools.
Testing Legacy C++ Code with Approval Tests
You have inherited some legacy C++ code: it is valuable, but it doesn’t have tests, and it wasn’t designed to be testable, so you need to start refactoring. But you can’t refactor safely until the code has tests, and you can’t add tests without refactoring! How can you ever break out of this loop?