Share on LinkedIn

An API (Application Programming Interface) is an interface between external software applications or between different layers of the same...

In traditional software development environments, test levels like unit, integration, system, end-to-end and UAT tests are commonly used...

There are many challenges in any testing project, and testing in the Agile environment is no different. Let us review some of the most...

Unit tests are the first level of software testing, where individual software units are tested. It is considered “white box” testing. The...

The graphical user interface (GUI) is the primary platform for manipulating software. Due to its importance to the end-user, it must be...

Acceptance Test-Driven Development (ATDD) is a process that ideally involves all roles in the team contributing to the overall testing...

The first quadrant (Q1) is associated with automated testing and covers test types like unit tests, component tests, and API testing....

When an organization implements any change, there must be a preliminary understanding of the side effects that may be on its teams. This...

Brian Marick originally introduced the Agile testing quadrants as terms for different categories of tests used for various purposes. The...

Risk-based testing is a testing approach that uses risk to prioritize, design and execute test scenarios. Risk-based testing helps the...

Exploratory testing is probably one of the most efficient and effective testing methods for Agile teams to use. Exploratory testing...

While there is a separation between development and test teams in traditional testing, Agile testing is based on collaboration and...

Security is a set of measures that protect an application against unforeseen actions that may cause it to stop functioning or be...

Agile development helps organizations deliver fast, but under no circumstances does it say that you can do it with crappy quality. If you...

Automation is a core foundation of almost any successful Agile project. It has a significant impact on testers, as much of their testing...

In theory, an Agile team is expected to produce a potential software increment at the end of each sprint. This looks great on paper, but...

Test-Driven Development (TDD) is an evolutionary approach to conducting a development process that combines test-first development. The...

Most of the testing effort, and in some cases all of it, is strictly the responsibility of the Agile team. They should perform all...

Software risk management (SRM) is a practice that combines a set of tools, processes, and methods for managing risks in the software...

In theory, Agile teams are expected to deliver a working increment of the software ready to be deployed at the end of each sprint. To...