The document discusses pairwise testing as a technique for reducing the number of test cases needed to cover all combinations of parameters. It shows that using pairwise testing on a problem with 10 parameters, each with multiple values, reduces the number of test cases from over 36 million to just 97 test cases, cutting the estimated testing time from over 2016 man years to just 1 man day. Pairwise testing provides nearly 100% coverage of defects using far fewer tests than exhaustive testing of all combinations.
- The speaker proposes 16 "test axioms" that are intended to provide a framework for testing approaches and represent principles that are context-insensitive and self-evidently true.
- The axioms are grouped into three categories: stakeholders, design, and delivery. The speaker argues the axioms can help testers think critically about testing and identify flaws in arguments.
- It is argued that process improvement models are not effective for improving testing because there is no consensus on best practices and processes must be tailored to context. True improvement requires understanding why current approaches are used given the context.
Git hooks can be used to automate tasks and enforce code quality standards in a repository. Common hooks include prepare-commit-msg to modify commit messages, pre-receive to reject pushes that fail validation checks, and post-receive to automatically link issues to builds, run tests, and update fields after code is received. Git hooks allow automation of best practices using any programming language and help maintain control and organization of code in a repository.
The document discusses a new model for testing that focuses on exploration of knowledge sources to build test models that inform testing. It outlines three patterns of software development (structured, agile, continuous) and argues testing involves exploring knowledge sources and building test models, with all testing being exploratory in nature. A new test process is proposed involving exploration support tools that capture testing plans and activity in real-time. The roles of developers and testers may become blurred in the future under this new model.
The document discusses user stories in user acceptance testing (UAT) time. It covers why changes to user stories during UAT need to be discussed, provides examples of common types of changes like changing a story's size or adding support, and examines what those changes mean for tasks like code, design, and testing updates. It poses the question of whether such changes can be prevented.
This document discusses why checklists are better than test cases for documentation in quality assurance. It argues that test cases become overcrowded and focus too much on documentation rather than core functions. Checklists are more time-saving and easy to update. An example compares a test case to a checklist for login/registration flows. The author's company Hipo uses a test pad and robot framework integrated with checklists to share with clients and team members.
The document provides guidance for managing a team of junior testers. It discusses challenges such as lack of skills and experience in junior testers. It recommends setting clear expectations, providing frequent communication and feedback, ensuring knowledge sharing, and protecting the team to help them succeed. Patience and structure are important, as is repeating key messages, to help junior testers learn and improve. The goal is for the team to work cooperatively toward a common objective.
This document discusses emotional intelligence and emotions-based testing. It introduces emotional intelligence (EQ) and its components: self-awareness, self-regulation, empathy, and social skills. The document provides examples of linking emotions like sadness, discontent, and joy to potential issues in testing approaches, test design, and test execution. It encourages investigating emotions and advocating for "EQ bugs" during testing. Small exercises are suggested to help participants reflect on their feelings and consider how to start with emotions-based testing.
The document discusses pairwise testing as a technique for reducing the number of test cases needed to cover all combinations of parameters. It shows that using pairwise testing on a problem with 10 parameters, each with multiple values, reduces the number of test cases from over 36 million to just 97 test cases, cutting the estimated testing time from over 2016 man years to just 1 man day. Pairwise testing provides nearly 100% coverage of defects using far fewer tests than exhaustive testing of all combinations.
- The speaker proposes 16 "test axioms" that are intended to provide a framework for testing approaches and represent principles that are context-insensitive and self-evidently true.
- The axioms are grouped into three categories: stakeholders, design, and delivery. The speaker argues the axioms can help testers think critically about testing and identify flaws in arguments.
- It is argued that process improvement models are not effective for improving testing because there is no consensus on best practices and processes must be tailored to context. True improvement requires understanding why current approaches are used given the context.
Git hooks can be used to automate tasks and enforce code quality standards in a repository. Common hooks include prepare-commit-msg to modify commit messages, pre-receive to reject pushes that fail validation checks, and post-receive to automatically link issues to builds, run tests, and update fields after code is received. Git hooks allow automation of best practices using any programming language and help maintain control and organization of code in a repository.
The document discusses a new model for testing that focuses on exploration of knowledge sources to build test models that inform testing. It outlines three patterns of software development (structured, agile, continuous) and argues testing involves exploring knowledge sources and building test models, with all testing being exploratory in nature. A new test process is proposed involving exploration support tools that capture testing plans and activity in real-time. The roles of developers and testers may become blurred in the future under this new model.
The document discusses user stories in user acceptance testing (UAT) time. It covers why changes to user stories during UAT need to be discussed, provides examples of common types of changes like changing a story's size or adding support, and examines what those changes mean for tasks like code, design, and testing updates. It poses the question of whether such changes can be prevented.
This document discusses why checklists are better than test cases for documentation in quality assurance. It argues that test cases become overcrowded and focus too much on documentation rather than core functions. Checklists are more time-saving and easy to update. An example compares a test case to a checklist for login/registration flows. The author's company Hipo uses a test pad and robot framework integrated with checklists to share with clients and team members.
The document provides guidance for managing a team of junior testers. It discusses challenges such as lack of skills and experience in junior testers. It recommends setting clear expectations, providing frequent communication and feedback, ensuring knowledge sharing, and protecting the team to help them succeed. Patience and structure are important, as is repeating key messages, to help junior testers learn and improve. The goal is for the team to work cooperatively toward a common objective.
This document discusses emotional intelligence and emotions-based testing. It introduces emotional intelligence (EQ) and its components: self-awareness, self-regulation, empathy, and social skills. The document provides examples of linking emotions like sadness, discontent, and joy to potential issues in testing approaches, test design, and test execution. It encourages investigating emotions and advocating for "EQ bugs" during testing. Small exercises are suggested to help participants reflect on their feelings and consider how to start with emotions-based testing.
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.
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.
Energieeffizienz in der Industrie 2te 2nd Edition Markus Blesltlyccxcujx8326
油
Energieeffizienz in der Industrie 2te 2nd Edition Markus Blesl
Energieeffizienz in der Industrie 2te 2nd Edition Markus Blesl
Energieeffizienz in der Industrie 2te 2nd Edition Markus Blesl