The CEO asked the test manager 10 questions regarding implementing Agile practices and improving quality while meeting aggressive release goals. Some of the key questions included how Agile will improve quality, what is needed to achieve a goal of 3000 story points per release, how to add features needed late in a sprint, and whether the company really needs automated quality assurance given priorities around time to market over crystal clear quality.
Root Cause Analysis in Testing "Dealing with Problems, Not Symptoms! " SQALab
The document discusses root cause analysis (RCA) techniques for analyzing critical problems. It introduces the 5 whys technique and cause-effect diagramming for performing RCA. A case study example is presented of an RCA meeting with a high-tech company that was experiencing a high return rate of products from customers. The initial belief was that partial test planning and coverage was the root cause, but upon further analysis using the RCA techniques, it was revealed that issues higher up in the development process, such as unclear requirements and incomplete specifications, were likely the underlying root causes.
This document discusses test estimation techniques. It explains that good estimates are accurate, realistic, and actionable. It recommends asking experts, using metrics and industry averages, and negotiating with managers. It also discusses estimating techniques like planning poker, three-point estimates, and understanding dependencies. The document emphasizes using historical data to predict testing time and the number of bugs found.
The CEO asked the test manager 10 questions regarding implementing Agile practices and improving quality while meeting aggressive release goals. Some of the key questions included how Agile will improve quality, what is needed to achieve a goal of 3000 story points per release, how to add features needed late in a sprint, and whether the company really needs automated quality assurance given priorities around time to market over crystal clear quality.
Root Cause Analysis in Testing "Dealing with Problems, Not Symptoms! " SQALab
The document discusses root cause analysis (RCA) techniques for analyzing critical problems. It introduces the 5 whys technique and cause-effect diagramming for performing RCA. A case study example is presented of an RCA meeting with a high-tech company that was experiencing a high return rate of products from customers. The initial belief was that partial test planning and coverage was the root cause, but upon further analysis using the RCA techniques, it was revealed that issues higher up in the development process, such as unclear requirements and incomplete specifications, were likely the underlying root causes.
This document discusses test estimation techniques. It explains that good estimates are accurate, realistic, and actionable. It recommends asking experts, using metrics and industry averages, and negotiating with managers. It also discusses estimating techniques like planning poker, three-point estimates, and understanding dependencies. The document emphasizes using historical data to predict testing time and the number of bugs found.
This document discusses continuous performance testing (CPT) and introduces the Jagger CPT solution. It provides an overview of why performance testing is important, outlines the principles and goals of CPT, and describes the key parts of the Jagger CPT platform including load generation, metrics collection, test data management, and environment management. It also provides an example customer success story where Jagger was used for continuous performance testing of a large ecommerce site.
Мощь переполняет с JDI 2.0 - новая эра UI автоматизацииSQALab
This document provides an overview of the JDI (Java UI test automation framework). It discusses features of JDI including being UI element oriented, providing common UI elements and solutions to common problems. It provides examples of how to write tests using JDI annotations and page object pattern. The document also summarizes benefits of JDI such as reducing test code, improving test clarity, reuse across projects. Finally it outlines new features planned for JDI 2.0 including layout verification, page object generator, integration with Selenium and expanding JDI to other languages like Python.
This document discusses continuous performance testing (CPT) and introduces the Jagger CPT solution. It provides an overview of why performance testing is important, outlines the principles and goals of CPT, and describes the key parts of the Jagger CPT platform including load generation, metrics collection, test data management, and environment management. It also provides an example customer success story where Jagger was used for continuous performance testing of a large ecommerce site.
Мощь переполняет с JDI 2.0 - новая эра UI автоматизацииSQALab
This document provides an overview of the JDI (Java UI test automation framework). It discusses features of JDI including being UI element oriented, providing common UI elements and solutions to common problems. It provides examples of how to write tests using JDI annotations and page object pattern. The document also summarizes benefits of JDI such as reducing test code, improving test clarity, reuse across projects. Finally it outlines new features planned for JDI 2.0 including layout verification, page object generator, integration with Selenium and expanding JDI to other languages like Python.
The document discusses testing of geolocation systems. It provides an overview of geolocation, including definitions and importance. It then outlines the speaker's experience and work testing GIS systems. The rest of the document details approaches to testing geolocation, including simulating calls, checking responses and databases, and verifying accuracy. It also discusses common data formats, projections, tools like PostGIS and QGIS, and potential bugs to watch for like coordinate jumbling. The conclusion emphasizes starting simple, practicing to improve, and for tests to grow with knowledge as geolocation is important for future IT.