This is chapter 4 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 4 - Quality Characteristics for Technical Testing
The document discusses quality characteristics for technical testing, focusing on reliability testing. It provides definitions and explanations of reliability sub-characteristics like maturity, fault tolerance, and recoverability. It describes approaches to measuring software maturity and reliability over time. Types of reliability tests discussed include fault tolerance testing, recoverability (failover and backup/restore) testing, and availability testing. General guidance is provided on planning and specifying reliability tests, noting the need for production-like environments and long test durations to obtain statistically significant results.
The document discusses fundamentals of software testing including definitions of testing, why testing is necessary, seven testing principles, and the test process. It describes the test process as consisting of test planning, monitoring and control, analysis, design, implementation, execution, and completion. It also outlines the typical work products created during each phase of the test process.
This document provides an overview of software testing and the testing process. It discusses:
- The purpose of testing is to find errors and ensure software meets requirements.
- The testing process includes test planning, analysis and design, execution, evaluation and reporting.
- Key methodologies like unit, integration, system and acceptance testing are explained.
- Regression testing is described as important for ensuring changes don't break existing functionality.
- The roles of different teams in the testing process and the goals at each testing level are outlined.
Software Testing Life Cycle refers to 6 phases of the software testing process. Learn about each phase of STLC in-depth in our article. (Source: https://www.goodcore.co.uk/blog/software-testing-life-cycle/)
software testing is necessary to make sure the product or application is defect free, as per customer specifications. Software testing identifies fault whose removal increases the software Quality and Increases the software reliability.Testing effort is directly proportional to the complexity of the program.
*Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses *
This Edureka PPT on "Software Testing Life Cycle" will provide you with in-depth knowledge about software testing and the different phases involved in the process of testing.
Below are the topics covered in this session:
Introduction to Software Testing
Why Testing is Important?
Who does Testing?
Software Testing Life Cycle
Requirement Analysis
Test Planning
Test Case Development
Test Environment Setup
Test Execution
Test Cycle Closure
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Instagram: https://www.instagram.com/edureka_lea...
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
This is chapter 7 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. I hope this ppt will help u to learn about software testing.
The document discusses defect tracking and management. It provides details on defect identification, reporting, tracking, resolution and using defect information to improve processes. A recommended structure is given for defect reports, including title, description, steps to reproduce, actual and expected results. Examples of a defect report and tracking sheet in Excel are also shown. The defect management process involves executing tests, logging discrepancies, reviewing with developers, assigning defects, retesting after fixes, and closing defects when resolved.
This is the chapter 5 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.
The document discusses creating a high-performing QA function through continuous integration, delivery, and testing. It recommends that QA be integrated into development teams, with automated testing, defect tracking, and ensuring features align with business needs. This would reduce defects and costs while improving customer experience through more frequent releases. Key steps outlined are implementing continuous integration and delivery pipelines, test-driven development, quality control gates, and measuring escaping defects to guide improvements.
Now to answer, “What is Testing?” we can go by the famous definition of Myers, which says, “Testing is the process of executing a program with the intent of finding errors”
This is chapter 2 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
Test Management as Chapter 5 of ISTQB Foundation 2018. Topics covered are Test Organization, Test Planning and Estimation, Test Monitoring and Control, Test Execution Schedule, Test Strategy, Risk and Testing, Defect Management
Chapter 4 - Quality Characteristics for Technical TestingNeeraj Kumar Singh
The document discusses quality characteristics for technical testing, focusing on reliability testing. It provides definitions and explanations of reliability sub-characteristics like maturity, fault tolerance, and recoverability. It describes approaches to measuring software maturity and reliability over time. Types of reliability tests discussed include fault tolerance testing, recoverability (failover and backup/restore) testing, and availability testing. General guidance is provided on planning and specifying reliability tests, noting the need for production-like environments and long test durations to obtain statistically significant results.
The document discusses fundamentals of software testing including definitions of testing, why testing is necessary, seven testing principles, and the test process. It describes the test process as consisting of test planning, monitoring and control, analysis, design, implementation, execution, and completion. It also outlines the typical work products created during each phase of the test process.
This document provides an overview of software testing and the testing process. It discusses:
- The purpose of testing is to find errors and ensure software meets requirements.
- The testing process includes test planning, analysis and design, execution, evaluation and reporting.
- Key methodologies like unit, integration, system and acceptance testing are explained.
- Regression testing is described as important for ensuring changes don't break existing functionality.
- The roles of different teams in the testing process and the goals at each testing level are outlined.
Software Testing Life Cycle – A Beginner’s GuideSyed Hassan Raza
Software Testing Life Cycle refers to 6 phases of the software testing process. Learn about each phase of STLC in-depth in our article. (Source: https://www.goodcore.co.uk/blog/software-testing-life-cycle/)
software testing is necessary to make sure the product or application is defect free, as per customer specifications. Software testing identifies fault whose removal increases the software Quality and Increases the software reliability.Testing effort is directly proportional to the complexity of the program.
*Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses *
This Edureka PPT on "Software Testing Life Cycle" will provide you with in-depth knowledge about software testing and the different phases involved in the process of testing.
Below are the topics covered in this session:
Introduction to Software Testing
Why Testing is Important?
Who does Testing?
Software Testing Life Cycle
Requirement Analysis
Test Planning
Test Case Development
Test Environment Setup
Test Execution
Test Cycle Closure
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Instagram: https://www.instagram.com/edureka_lea...
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
This is chapter 7 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. I hope this ppt will help u to learn about software testing.
The document discusses defect tracking and management. It provides details on defect identification, reporting, tracking, resolution and using defect information to improve processes. A recommended structure is given for defect reports, including title, description, steps to reproduce, actual and expected results. Examples of a defect report and tracking sheet in Excel are also shown. The defect management process involves executing tests, logging discrepancies, reviewing with developers, assigning defects, retesting after fixes, and closing defects when resolved.
This is the chapter 5 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.
The document discusses creating a high-performing QA function through continuous integration, delivery, and testing. It recommends that QA be integrated into development teams, with automated testing, defect tracking, and ensuring features align with business needs. This would reduce defects and costs while improving customer experience through more frequent releases. Key steps outlined are implementing continuous integration and delivery pipelines, test-driven development, quality control gates, and measuring escaping defects to guide improvements.
Now to answer, “What is Testing?” we can go by the famous definition of Myers, which says, “Testing is the process of executing a program with the intent of finding errors”
This is chapter 2 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
The document describes the testing life cycle process which includes test plan preparation, test case design, test execution and log preparation, defect tracking, and test report preparation. It then provides details about each step of the testing life cycle process such as how to prepare test plans, design test cases, execute tests and log results, track defects, and prepare test reports.
The document describes the key stages of the software testing life cycle (STLC), including contract signing, requirement analysis, test planning, test development, test execution, defect reporting, and product delivery. It provides details on the processes, documents, and activities involved in each stage. Risk analysis and bug/defect management processes are also summarized. Various test metrics and bug tracking tools that can be used are listed.
This document discusses defect tracking and correction in software development. It defines a defect as any non-conformity to specifications. The defect discovery process involves identifying defects and notifying the development team. The developer then acknowledges, fixes, and verifies the defect. Defects go through a tracking lifecycle of being raised, reported, fixed, and closed. Defects are found through static, dynamic, and operational techniques and categorized by functionality, severity, and priority. The document outlines the contents of a defect report and explains the purpose of defect recording and reporting in the defect management process.
The document discusses software testing concepts and processes. It defines key terms like errors, faults, failures, test cases, test suites and test harnesses. It describes different types of testing like unit testing, integration testing, system testing and acceptance testing. It explains the testing process which involves test planning, designing test cases, and test execution. Defects found during testing are logged and tracked through different states from submission to fixing to verification and closure. Test cases are specified in documents before usage to ensure quality.
Software quality refers to how well a software product or service meets requirements and expectations. It is subjective as it depends on the perspective of the customer. Common aspects of quality include the software being bug-free, delivered on time and on budget, meeting requirements, and being maintainable. True software quality can only be determined by measuring how well the software serves its intended purpose from the viewpoint of all stakeholders.
The document discusses fundamentals of software testing including definitions of testing, why testing is necessary, seven testing principles, and the test process. It describes the test process as consisting of test planning, monitoring and control, analysis, design, implementation, execution, and completion. It also outlines the typical work products created during each phase of the test process.
Static techniques such as reviews can improve both quality and productivity in software development. Static testing examines software work products like requirements and design documents manually or with tools before execution, finding defects early. Dynamic testing executes software with test cases. The two techniques are complementary, as static testing finds defects like missing requirements or design flaws while dynamic testing finds failures from execution. Using static testing from early in the development lifecycle provides advantages like early feedback, low rework costs, increased productivity, and greater awareness of quality issues.
The document provides an overview of software testing methods and concepts. It defines software testing as verifying and validating software to check for errors and ensure it meets requirements. The document discusses different testing methods like static testing (reviews, inspections) and dynamic testing (executing code with test cases). It also defines key terms like verification, validation, defects, bugs, and differences between quality assurance (planning processes) and quality control (product verification).
Software Testing Interview Questions For Experiencedzynofustechnology
The document discusses various topics related to software testing interviews for experienced testers. It covers reliability testing, handling bugs, challenges of thorough testing, testing without complete requirements, differences between retesting and regression testing, challenges of software testing, types of functional testing, and more. Key points made include that it is impossible to thoroughly test a program due to subjective requirements and too many inputs/paths, the importance of regression testing when modules are updated, and differences between bugs, defects, and errors.
Software Quality Assurance involves planned actions to provide confidence that software products and processes meet requirements. It includes various testing activities at both the unit and system level. While testing cannot ensure perfect quality, it provides information to improve the software. There are several factors to consider when prioritizing which defects to address, as it is typically not feasible to fix all defects. Testers should provide severity data to help inform prioritization decisions made by other stakeholders.
Micro understand without Micro managing: E.g., one can identify that a
specific tester is unable to execute a test case for 2 days due to a defect unresolved by developer
Micro understand without Micro managing: E.g., one can identify that a specific tester is unable to execute a test case for 2 days due to a defect unresolved by developer.
Software testing is an important phase of the software development process that evaluates the functionality and quality of a software application. It involves executing a program or system with the intent of finding errors. Some key points:
- Software testing is needed to identify defects, ensure customer satisfaction, and deliver high quality products with lower maintenance costs.
- It is important for different stakeholders like developers, testers, managers, and end users to work together throughout the testing process.
- There are various types of testing like unit testing, integration testing, system testing, and different methodologies like manual and automated testing. Proper documentation is also important.
- Testing helps improve the overall quality of software but can never prove that there
The document discusses various topics related to software testing including types of testing (manual vs automation), testing methods (black box, white box, grey box), testing levels (unit, integration, system), and common myths around testing. It provides definitions and examples of different testing techniques and clarifies misunderstandings around responsibilities and goals of testing. Videos are embedded to further explain key testing concepts like unit testing, integration testing, and differences between testing approaches.
Failure mode and effects analysis (FMEA) is a method to identify potential failures, determine their causes and effects, prioritize risks, and identify actions to address high-priority risks. An FMEA involves assembling a cross-functional team to analyze a process, product or service by identifying functions, potential failure modes and effects, causes, controls, severity, occurrence, detection ratings and risk priority numbers to prioritize improvement actions. FMEAs are used throughout a product or service lifecycle to prevent and reduce failures and risks.
This document provides an overview of software testing fundamentals. It defines testing as executing software to find bugs and discusses why testing is necessary to ensure quality. It also covers causes of defects, different levels of testing from unit to acceptance, testing principles, and sample entry and exit criteria for different test stages. The goal of testing is to validate software meets requirements and works as expected while improving quality through the identification and fixing of defects.
Manual testing is the oldest and most rigorous type of software testing that requires a tester to perform manual test operations without automation help. It is a laborious process requiring patience and other qualities from testers. A manual tester would typically understand functionality, prepare a test environment, execute test cases manually, verify results, record pass/fail, summarize results in a report, publish the report, and record any new defects found. While manual testing is thorough, test automation has become necessary due to shorter deadlines, but manual testing remains crucial and cannot be completely substituted.
Tool Support For Testing (Tool Support For Management Of Testing And Tests)sarahrambe
Test management tools provide support for managing tests and the testing process throughout the software development lifecycle. They allow for tracking tests planned, written, run, and results as well as scheduling tests and monitoring testing activities and progress. Requirements management tools also assist testing by facilitating requirements-based testing and requirements-tests traceability. Incident management tools track failures, defects, and other issues by recording attributes, prioritizing them, and reporting on resolution progress and metrics. Configuration management tools help ensure the correct versions of software, tests, and other items are used during testing.
Black-box testing views the program as a black box without seeing code. White-box testing examines internal structure. Gray-box combines black-box and knowledge of database validation. Test scripts are sets of automated instructions. Test suites are collections of test cases or scripts. Stress testing subjects a system to unreasonable loads to find breaking points while load testing uses representative loads.
This document provides an overview of software testing concepts. It discusses the meaning of software testing, the software testing lifecycle, and principles and techniques of software testing. The principles section explains 7 key principles such as that exhaustive testing is impossible and defects cluster in some modules. The techniques section describes manual testing approaches like walkthroughs and inspections, as well as automated testing types including correctness, performance, reliability, and security testing. The overall purpose is to introduce students to fundamental software testing concepts.
The document discusses software testing concepts including the importance of testing, the testing life cycle, types of testing, quality assurance and control, and bug reporting. It provides definitions and descriptions of key testing terms like errors, bugs, faults, failures, test plans, test cases, unit testing, integration testing, system testing, and regression testing. Testing roles like testers, QA leads, and test analysts are also outlined.
This chapter describes static test techniques, including reviews, and provides an overviewof how they are conducted. The fundamental objective of static testing is to improve the quality of softwarework products by assisting engineers to recognize and fix their own defects early in the softwaredevelopment process. While static testing techniques will not solve all the problems, they areenormously effective. Static techniques can improve both quality and productivity by impressive factors.Static testing is not magic and it should not be considered a replacement for dynamic testing, but allsoftware organizations should consider using reviews in all major aspects of their work includingrequirements, design, implementation, testing, and maintenance. Static analysis tools implementautomated checks, e.g. on code
Tool Support for Testing as Chapter 6 of ISTQB Foundation 2018. Topics covered are Tool Benefits, Test Tool Classification, Benefits of Test Automation and Risk of Test Automation
Test Management as Chapter 5 of ISTQB Foundation. Topics covered are Test Organization, Test Planning and Estimation, Test Monitoring and Control, Test Execution Schedule, Test Strategy, Risk Management, Defect Management
Test Case Design Techniques as chapter 4 of ISTQB Foundation. Topics included are Equivalence Partition, Boundary Value Analysis, State Transition Testing, Decision Table Testing, Use Case Testing, Statement Coverage, Decision Coverage, Error Guessing, Exploratory Testing, Checklist Based Testing
Chapter 3 of ISTQB Foundation 2018 syllabus with sample questions. Answers about what is static testing, what is review, types of review, informal review, walkthrough, technical review, inspection.
The document discusses testing throughout the software development life cycle. It describes different software development models including sequential, incremental, and iterative models. It also covers different test levels from component and integration testing to system and acceptance testing. The document discusses different types of testing including functional and non-functional testing. It also covers topics like maintenance testing and triggers for additional testing when changes are made. Also covers concepts of Agile including DevOps, Shift Left Approach, TDD, BDD, ATDD, Retrospective and Process Improvement
This is chapter 4 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 4 - Mobile Application Platforms, Tools and EnvironmentNeeraj Kumar Singh
This is chapter 4 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 3 - Common Test Types and Test Process for Mobile ApplicationsNeeraj Kumar Singh
This is chapter 3 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 2 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 1 - Mobile World - Business and Technology DriversNeeraj Kumar Singh
This is chapter 1 of ISTQB Specialist Mobile Application Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is a Sample Question Paper of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is the answer to Sample Questions of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
ISTQB Performance Tester Certification Syllabus and Study MaterialNeeraj Kumar Singh
This is Syllabus of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 5 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 4 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Chapter 3 - Performance Testing in the Software LifecycleNeeraj Kumar Singh
The document discusses performance testing activities across different software development lifecycles. It describes how performance testing should be conducted iteratively throughout sequential development models, with testing at each stage from concept to acceptance. For iterative models, performance testing is also iterative and can be part of continuous integration. Specific activities discussed include test planning, monitoring, analysis, design, implementation, execution and completion. Performance risks are also discussed for different architectures.
This is chapter 1 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
This is chapter 2 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
ISTQB Technical Test Analyst Answers to Sample Question PaperNeeraj Kumar Singh
Here are the answers and justification for the sample question paper for ISTQB Advance Technical Test Analyst for certification preparation. This is a standard paper from ISTQB.
This document contains a sample exam for the ISTQB Advanced Level Technical Test Analyst certification. It includes 45 multiple choice questions on topics such as test coverage types, risk analysis, and defect targeting. The questions aim to assess knowledge related to test design, test analysis, and test management. It also provides the exam structure and responsibilities of the exam working group as defined by ISTQB.
Measuring the Impact of Network Latency at TwitterScyllaDB
Widya Salim and Victor Ma will outline the causal impact analysis, framework, and key learnings used to quantify the impact of reducing Twitter's network latency.
Coordinate Systems in FME 101 - Webinar SlidesSafe Software
If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights.
During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to:
- Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value
- Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems
- Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors
- Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported
- Look Ahead: Gain insights into where FME is headed with coordinate systems in the future
Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!
Scaling Connections in PostgreSQL Postgres Bangalore(PGBLR) Meetup-2 - MydbopsMydbops
This presentation, delivered at the Postgres Bangalore (PGBLR) Meetup-2 on June 29th, 2024, dives deep into connection pooling for PostgreSQL databases. Aakash M, a PostgreSQL Tech Lead at Mydbops, explores the challenges of managing numerous connections and explains how connection pooling optimizes performance and resource utilization.
Key Takeaways:
* Understand why connection pooling is essential for high-traffic applications
* Explore various connection poolers available for PostgreSQL, including pgbouncer
* Learn the configuration options and functionalities of pgbouncer
* Discover best practices for monitoring and troubleshooting connection pooling setups
* Gain insights into real-world use cases and considerations for production environments
This presentation is ideal for:
* Database administrators (DBAs)
* Developers working with PostgreSQL
* DevOps engineers
* Anyone interested in optimizing PostgreSQL performance
Contact info@mydbops.com for PostgreSQL Managed, Consulting and Remote DBA Services
Fluttercon 2024: Showing that you care about security - OpenSSF Scorecards fo...Chris Swan
Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge.
You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter.
The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.
Kief Morris rethinks the infrastructure code delivery lifecycle, advocating for a shift towards composable infrastructure systems. We should shift to designing around deployable components rather than code modules, use more useful levels of abstraction, and drive design and deployment from applications rather than bottom-up, monolithic architecture and delivery.
Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data.
The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs.
Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution!
Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.
Advanced Techniques for Cyber Security Analysis and Anomaly DetectionBert Blevins
Cybersecurity is a major concern in today's connected digital world. Threats to organizations are constantly evolving and have the potential to compromise sensitive information, disrupt operations, and lead to significant financial losses. Traditional cybersecurity techniques often fall short against modern attackers. Therefore, advanced techniques for cyber security analysis and anomaly detection are essential for protecting digital assets. This blog explores these cutting-edge methods, providing a comprehensive overview of their application and importance.
論文紹介:A Systematic Survey of Prompt Engineering on Vision-Language Foundation ...Toru Tamaki
Jindong Gu, Zhen Han, Shuo Chen, Ahmad Beirami, Bailan He, Gengyuan Zhang, Ruotong Liao, Yao Qin, Volker Tresp, Philip Torr "A Systematic Survey of Prompt Engineering on Vision-Language Foundation Models" arXiv2023
https://arxiv.org/abs/2307.12980
The DealBook is our annual overview of the Ukrainian tech investment industry. This edition comprehensively covers the full year 2023 and the first deals of 2024.
Best Practices for Effectively Running dbt in Airflow.pdfTatiana Al-Chueyr
As a popular open-source library for analytics engineering, dbt is often used in combination with Airflow. Orchestrating and executing dbt models as DAGs ensures an additional layer of control over tasks, observability, and provides a reliable, scalable environment to run dbt models.
This webinar will cover a step-by-step guide to Cosmos, an open source package from Astronomer that helps you easily run your dbt Core projects as Airflow DAGs and Task Groups, all with just a few lines of code. We’ll walk through:
- Standard ways of running dbt (and when to utilize other methods)
- How Cosmos can be used to run and visualize your dbt projects in Airflow
- Common challenges and how to address them, including performance, dependency conflicts, and more
- How running dbt projects in Airflow helps with cost optimization
Webinar given on 9 July 2024
INDIAN AIR FORCE FIGHTER PLANES LIST.pdfjackson110191
These fighter aircraft have uses outside of traditional combat situations. They are essential in defending India's territorial integrity, averting dangers, and delivering aid to those in need during natural calamities. Additionally, the IAF improves its interoperability and fortifies international military alliances by working together and conducting joint exercises with other air forces.
Best Programming Language for Civil EngineersAwais Yaseen
The integration of programming into civil engineering is transforming the industry. We can design complex infrastructure projects and analyse large datasets. Imagine revolutionizing the way we build our cities and infrastructure, all by the power of coding. Programming skills are no longer just a bonus—they’re a game changer in this era.
Technology is revolutionizing civil engineering by integrating advanced tools and techniques. Programming allows for the automation of repetitive tasks, enhancing the accuracy of designs, simulations, and analyses. With the advent of artificial intelligence and machine learning, engineers can now predict structural behaviors under various conditions, optimize material usage, and improve project planning.
Comparison Table of DiskWarrior Alternatives.pdfAndrey Yasko
To help you choose the best DiskWarrior alternative, we've compiled a comparison table summarizing the features, pros, cons, and pricing of six alternatives.
Blockchain technology is transforming industries and reshaping the way we conduct business, manage data, and secure transactions. Whether you're new to blockchain or looking to deepen your knowledge, our guidebook, "Blockchain for Dummies", is your ultimate resource.
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
1. Defect Management
1 Testing Process 2 Test Management 3 Reviews
Software Testing - ISTQB Advance
Test Manager Exam Preparation
Chapter 4
Neeraj Kumar Singh
4 Defect Management
5 Improving Process 6 Test Tools 7 People Skills
2. Defect Management
Contents
4.1 Introduction
4.2 The Defect Lifecycle and the Software
Development Lifecycle
4.3 Defect Report Information
4.4 Assessing Process Capability with
Defect Report Information
Neeraj Kumar Singh
3. An organization’s defect management process and the tool used to manage this work are of critical importance not
only to the test team but to all teams involved in the development of software.
Information gathered by the effective management of defects allows the Test Manager and other project
stakeholders to gain insight on the state of a project throughout the development lifecycle, and by collecting and
analyzing data over time, can help locate areas of potential improvement for testing and development processes.
In addition to understanding the overall defect lifecycle and how it is used to monitor and control both the testing
and software development processes, the Test Manager must also be familiar with what data is critical to capture
and must be an advocate of proper usage of both the process and the selected defect management tool.
Neeraj Kumar Singh
Defect Management
Introduction
4. Defect Management
Contents
4.1 Introduction
4.2 The Defect Lifecycle and the Software
Development Lifecycle
4.3 Defect Report Information
4.4 Assessing Process Capability with
Defect Report Information
Neeraj Kumar Singh
5. As explained in the Foundation Level syllabus, defects are introduced when a person makes a mistake during the
creation of a work product. This work product can be a requirements specification, a user story, a technical
document, a test case, the program code, or any other work product produced during a software development or
maintenance process.
Defects may be introduced at any point in the software development lifecycle and in any software related work
product. Therefore, each phase of the software development lifecycle should include activities to detect and
remove potential defects.
The earlier each defect is detected and removed, the lower the overall cost of quality for the system; cost of
quality for a given level of defects is minimized when each defect is removed in the same phase in which it was
introduced.
Furthermore, static testing finds defects directly, rather than finding failures, and thus the cost of removing the
defect is lower because debugging activities are not required to isolate the defect.
During dynamic testing activities such as unit testing, integration testing, and system testing, the presence of a
defect is revealed when it causes a failure, which results in a discrepancy between the actual results and the
expected results of a test.
In some cases, a false-negative result occurs when the tester does not observe the anomaly.
Neeraj Kumar Singh
Defect Management
The Defect Lifecycle and the SDLC
6. Most testing organizations use a tool to manage defect reports through the defect lifecycle. A defect report
typically progresses through a workflow and moves through a sequence of states as it continues through the defect
lifecycle.
In most of these states, a single defect lifecycle participant owns the report and is responsible for carrying out a
task which, when completed, will cause the defect report to be moved to the next state (and assigned to the next
responsible party). In terminal states, such as when the defect report is closed (usually meaning that the
underlying defect is fixed and the fix verified through a confirmation test), cancelled (usually meaning that the
defect report is invalid), irreproducible (usually meaning that the anomaly can no longer be observed), or deferred
(usually meaning that the anomaly relates to a real defect, but that defect will not be fixed during the project),
the report does not have an owner, because no further actions are required.
Neeraj Kumar Singh
Defect Management
Defect Workflow and States
7. For defects discovered by testers during testing, there are three states in particular where the action resides with the test
team:
The initial state
In this state, one or more testers gather the information necessary for the person responsible for resolving the defect
to reproduce the anomaly.
This may also be referred to as the “open” or “new” state.
The returned state
In this state, the receiver of the report has rejected the report or is asking the tester to supply further information.
This state may indicate a shortfall in the initial information gathering process or of the testing itself, and Test
Managers should monitor for excessive rates of return. The tester(s) must provide the additional information, or
confirm that the report indeed should be rejected.
This may also be referred to as the “rejected” or “clarification” state.
The confirmation test state
In this state, the tester will run a confirmation test (often following the steps to reproduce the failure from the defect
report itself) to determine whether the fix has indeed solved the problem. If the confirmation test indicates that the
defect is repaired, the tester should close the report. If the confirmation test indicates that the defect is not repaired,
the tester should re-open the report, causing it to be reassigned to the previous owner, who can then complete the
work necessary to repair the defect.
This may also be referred to as the “resolved” or “verification” state.
Neeraj Kumar Singh
Defect Management
Defect Workflow and States
8. In some cases, an anomaly occurs not as the symptom of a defect, but rather due to a problem with the test
environment, the test data, some other element of the testware, or the tester’s own misunderstanding. If the
tester opens a defect report that subsequently is found not to relate to a defect in the work product under test,
that is a false-positive result. Such reports are typically cancelled or closed as invalid defect reports.
In addition, in some cases a defect can exhibit different symptoms which may appear to the tester(s) as being
entirely unrelated. If two or more defect reports are filed which subsequently are found to relate to the same root
cause, one of the defect reports is typically retained while the others are closed as duplicate defect reports.
While invalid and duplicate defect reports represent a certain level of inefficiency, some amount of such reports is
inevitable and should be accepted as such by the Test Manager. When managers attempt to eliminate all invalid
and duplicate defect reports, the number of false-negatives typically increases, since testers are being
discouraged from filing defect reports. This decreases the testing organization’s defect detection effectiveness,
which is related to a key testing organization objective in most cases.
Neeraj Kumar Singh
Defect Management
Managing Invalid and Duplicate Defect Reports
9. Although the testing organization and Test Manager typically own the overall defect management process and the
defect management tool, a cross-functional team is generally responsible for managing the reported defects for a
given project. In addition to the Test Manager, participants in the defect management (or defect triage) committee
typically include development, project management, product management and other stakeholders who have an
interest in the software under development.
As anomalies are discovered and entered into the defect management tool, the defect management committee
should meet to determine whether each defect report represents a valid defect, and whether it should be fixed or
deferred. This decision requires the defect management committee to consider the benefits, risks and costs
associated with fixing or not fixing the defect.
If the defect is to be fixed, the team should establish the priority of fixing the defect relative to other project
tasks. The Test Manager and test team may be consulted regarding the relative importance of a defect and should
provide available objective information.
A defect tracking tool should not be used as a substitute for good communication nor should defect management
committee meetings be used as a substitute for effective use of a good defect tracking tool. Communication,
adequate tool support, a well-defined defect lifecycle, and an engaged defect management committee are all
necessary for effective and efficient defect management.
Neeraj Kumar Singh
Defect Management
Cross-Functional Defect Management
10. Defect Management
Contents
4.1 Introduction
4.2 The Defect Lifecycle and the Software
Development Lifecycle
4.3 Defect Report Information
4.4 Assessing Process Capability with
Defect Report Information
Neeraj Kumar Singh
11. When a defect is detected (as part of static testing), or a failure is observed (as part of dynamic testing), data
should be gathered by the person(s) involved and included in the defect report.
This information should suffice for three purposes:
Management of the report through the defect lifecycle
Assessment of project status, especially in terms of product quality, and test progress
Assessment of process capability
The data needed for defect report management and project status can vary depending on when the defect is
detected in the lifecycle, typically with less information needed earlier (e.g., requirements reviews and unit test).
However, the core information gathered should be consistent across the lifecycle and ideally across all projects to
allow for meaningful comparison of process defect data throughout the project and across all projects.
Neeraj Kumar Singh
Defect Management
Defect Report Information
12. Defect data to be collected may include the following:
The name of the person who discovered the defect
The role of the person (e.g., end user, business analyst, developer, technical support person)
The type of testing being performed (e.g., usability testing, performance testing, regression testing )
A summary of the problem
A detailed description of the problem
Steps to reproduce the failure (for a defect), along with the actual and expected results (highlighting the
anomaly), including screen shots, database dumps, and logs where applicable
The lifecycle phase of introduction, detection, and removal for the defect, including the test level if
applicable
The work product in which the defect was introduced
The severity of the impact on the system and/or the product stakeholders (usually determined by the
technical behavior of the system)
The priority to fix the problem (usually determined by the business impact of the failure) The subsystem or
component in which the defect lies (for defect cluster analysis)
Neeraj Kumar Singh
Defect Management
Defect Report Information
13. Defect data to be collected may include the following:
The project activity occurring when the problem was detected
The identification method which revealed the problem (e.g., review, static analysis, dynamic testing,
production use)
The type of defect (usually corresponding to a defect taxonomy where used)
The quality characteristic affected by the defect
The test environment in which the defect was observed (for dynamic testing)
The project and product in which the problem exists
The current owner; i.e., the person currently assigned to work on the problem, assuming the report is not in a
final state
The current state of the report (usually managed by the defect tracking tool as part of the lifecycle)
The specific work products (e.g., test items and their release numbers) in which the problem was observed,
along with the specific work products in which the problem was ultimately resolved
Neeraj Kumar Singh
Defect Management
Defect Report Information
14. Defect data to be collected may include the following:
The impact on project and product stakeholders’ interests
Conclusions, recommendations and approvals for the action taken or not taken to resolve the problem
Risks, costs, opportunities, and benefits associated with fixing or not fixing the defect
The dates on which various defect lifecycle transitions occurred, the owners of the report based on each
transition, and the actions taken by project team members to isolate, repair, and verify the defect fix
A description of how the defect was ultimately resolved and recommendations for testing the fix (if the defect
was resolved by a change to the software)
Other references, such as the test that revealed the defect and the risk, requirement, or other test basis
element related to the defect (for dynamic testing)
Neeraj Kumar Singh
Defect Management
Defect Report Information
15. Defect Management
Contents
4.1 Introduction
4.2 The Defect Lifecycle and the Software
Development Lifecycle
4.3 Defect Report Information
4.4 Assessing Process Capability with
Defect Report Information
Neeraj Kumar Singh
16. As discussed earlier, defect reports can be useful for project status monitoring and reporting. While the process
implications of metrics are primarily addressed in the Expert Test Management, at the Advanced Level, Test
Managers should be aware of what defect reports mean in terms of assessing the capability of the testing and
software development processes.
In addition to the test progress monitoring information, defect information needs to support process improvement
initiatives. Examples include:
Using the phase of introduction, detection, and removal information, on a phase-by-phase basis, to assess
phase containment and suggest ways to improve defect detection effectiveness in each phase
Using the phase of introduction information for Pareto analysis of the phases in which the largest number of
defects are introduced, to enable targeted improvements to reduce the total number of defects
Using the defect root cause information to determine the underlying reasons for defect introduction, to enable
process improvements that reduce the total number of defects
Using the phase of introduction, detection, and removal information to perform cost of quality analysis, to
minimize the cost associated with defects
Using defect component information to perform defect cluster analysis, to better understand technical risks
(for risk-based testing) and to enable re-engineering of troublesome components
Neeraj Kumar Singh
Defect Management
Assessing Process Capability with Defect Report
17. In some cases, teams may elect not to track defects found during some or all of the software development
lifecycle.
While this is often done in the name of efficiency and for the sake of reducing process overhead, in reality it
greatly reduces visibility into the process capabilities of testing and software development.
This makes the improvements suggested above difficult to carry out due to a lack of reliable data.
Neeraj Kumar Singh
Defect Management
Assessing Process Capability with Defect Report
18. Defect Management
1 Testing Process 2 Test Management 3 Reviews
Software Testing - ISTQB Advance
Test Manager Exam Preparation
Chapter 4
Neeraj Kumar Singh
4 Defect Management
5 Improving Process 6 Test Tools 7 People Skills
20. 1. The diagram shows an incomplete defect management process,
where three states (states X, Y and Z) have yet to be named
appropriately.
Which of the following would correctly complete the process?
Select ONE option.
Answer Set
a. STATE X – RETESTED STATE Y – NEW STATE Z – BLOCKED
b. STATE X – REOPENED STATE Y – REJECTED STATE Z – DEFERRED
c. STATE X – DUPLICATE STATE Y – UNCONFIRMED STATE Z – TERMINATED
d. STATE X – VERIFIED STATE Y – REVIEW STATE Z – FIXED
Defect Management
Sample Question
21. 2. You are the test manager on a project where system testing is being performed on software being provided by a
third party. You have received a complaint from the third party that the completeness of the defect data from your
system testing is unacceptable.
The following list of information items has been identified as potentially missing from the defect reports being sent
to the third party.
Which items do you think are MOST important to add to the defect reports?
Select TWO options.
Answer Set
a. The project activity occurring when the problem was detected.
b. Steps to reproduce the failure, along with the actual and expected results.
c. The priority to fix the problem.
d. The technical type of the defect.
e. The lifecycle phases of introduction, detection, and removal for the defect
Defect Management
Sample Question
22. 3. It has been decided that the first step to test and development process improvement within your organization
will be to reduce the number of defects introduced during development.
Which of the following defect report statistics will be MOST useful in fulfilling this aim?
Select ONE option.
Answer Set
a. The lifecycle phases of introduction, detection, and removal for the defect.
b. The defect root cause information.
c. The defect component information.
d. The defect removal efficiency information
Defect Management
Sample Question