{"id":2652,"date":"2016-03-29T11:08:12","date_gmt":"2016-03-29T11:08:12","guid":{"rendered":"http:\/\/www.gallop.net\/blog\/?p=1169"},"modified":"2023-09-05T12:00:45","modified_gmt":"2023-09-05T06:30:45","slug":"agile-test-automation-and-agile-quadrants","status":"publish","type":"post","link":"https:\/\/www.cigniti.com\/blog\/agile-test-automation-and-agile-quadrants\/","title":{"rendered":"Different Types of Testing Automation & Agile Test Quadrants Recommended in Agile"},"content":{"rendered":"
This blog briefly discusses the relationship between Test automation and Agile Test Quadrants.<\/p>\n
Test automation is generally defined as \u201cthe use of special software (separate from the software being tested) to control the execution of tests and the comparison of actual outcomes with predicted outcomes.\u201d<\/p>\n
Agile Test Quadrants (introduced by Brian Marick and further worked upon by Lisa Crispin) try to understand the relationship between the various forms of tests using four different quadrants:<\/p>\n
<\/p>\n
Using the Agile Testing Quadrants helps you accomplish goals related to supporting the team, critiquing the product, and meeting the business and technological needs.<\/p>\n
Following are some details on what each quadrant is made up of, what tools might be used in each, and the purpose of each.<\/p>\n
Q1 is associated with Automated testing and covers tests such as Unit tests, API tests, Web Services testing, and Component Tests. The main benefit of this quadrant is that these tests help improve the design without adversely affecting the functionality. The main objective is to improve the product’s quality through proper source code management and a seamlessly integrated development environment. A few tools used are TeamCity, Eclipse, xUnit, IntelliJ Idea, etc.<\/p>\n
This is a critical agile testing quadrant as it helps teams get together to identify the pain points. If you cannot cope with the activities of this quadrant, managing the other quadrants will prove to be even more difficult.<\/p>\n
Q2 is associated with Automated and manual testing and covers tests such as Functional Testing, Story Tests, Prototypes, and Simulations. Q2 helps formulate the correct set of questions and thus drives tests correctly aligned with the business. Q2 thrives in an iterative environment where skilled testers collaborate with clients and understand the responsibility of delivering a quality product. Q2 involves a lot of brainstorming sessions; thus, MindMap may be used as a regular tool along with Visio for flow diagrams.<\/p>\n
Behavior-driven development tools and frameworks such as Cucumber and easyB, and UI testing tools\/libraries\/frameworks such as Selenium, QTP, Robot Framework, etc., also serve as good tools of use.<\/p>\n
Q3 is associated with Manual testing and covers tests such as Exploratory Testing<\/a>, Scenario-based Testing, Usability Testing, User Acceptance Testing, and Alpha\/Beta testing. Q3 is about evaluating the Product and its use using demos, feedback, checking the actual user experience, etc. Q3 involves critical thinking and in-depth observation of multiple scenarios (usability, API, Web).<\/p>\n