A test strategy is the set of ideas that guides your test design. It's what explains why you test this instead of that, and why you test this way instead of that way. Strategic thinking matters because testers must make quick decisions about what needs testing right now and what can be left alone. You must be able to work through major threads without being overwhelmed by tiny details. James Bach describes how test strategy is organized around risk but is not defined before testing begins. Rather, it evolves alongside testing as we learn more about the product. We start with a vague idea of our strategy, organize it quickly, and document as needed in a concise way. In the end, the strategy can be as formal and detailed as you want it to be. In the beginning, though, we start small. If you want to focus on testing and not paperwork, this approach is for you.
Shift Left & Shift Right Approach in TestingRiswan
Shift Left Testing Approach uses information from the business requirements to start the testing process. This includes using the list of requested features to create test cases, expected transaction volume as targets for performance testing, and business priority to prioritize test case execution.
Shift Right Testing Approach uses operational information to start the testing process. This includes using complaint data to enrich regression test cases with the most complained about features and existing revenue data to prioritize test execution.
Both Shift Left and Shift Right approaches are used together in testing to improve test quality by starting with different types of early input information.
This is the Testing Capability document prepared by a Test Manager for work done with present client and used to sell the testing services to other clients.
Shift left - find defects earlier through automated test and deploymentClaudia Ring
Do you know how much time it takes or how that translates into dollars lost every time you fix a defect in development, QA, or Production? The cost of application failures or errors increases exponentially the further into the delivery pipeline they are when found. If application defects are discovered by end users in Production, or errors cause a Production outage, the cost can be thousands per second, in addition to the intangible loss of reputation.
So how do you begin to identify defects earlier in software development and prevent them from becoming major, costly errors later on? Join Al Wagner, IBM Technical Evangelist, as he discusses how to "shift left" and;
Incorporate service virtualization and automated testing into development for a more thorough and accurate representation of application quality
Integrate deployment automation with continuous testing to remove wait times on application promotion
Adopt best practices that have proven successful for IBM customers who are currently shifting left
Software Testing Process, Testing Automation and Software Testing TrendsKMS Technology
This is the slide deck that KMS Technology's experts shared useful information about latest and greatest achievements of software testing field with lecturers of HCMC University of Industry.
The document discusses how the role of testers has evolved over time as business and technology changes accelerated. It describes how testing jobs now require strong programming skills. It also presents a model that positions testing as a team activity that provides empirical evidence across many dimensions to support product quality. The document advocates for testers to think analytically, be curious and critical, and apply their skills broadly to contribute in various roles on a team.
This document provides an overview of exploratory testing techniques. It discusses that exploratory testing involves simultaneous learning, test design, and test execution. Exploratory testing is tester-centric and focuses on problem solving strategies like heuristics rather than scripts. The document dispels some myths about exploratory testing, including that it is unstructured and cannot involve documentation. It provides examples of how documents can be used for reflection, information sharing, and reporting in exploratory testing.
Shift Left & Shift Right Approach in TestingRiswan
Shift Left Testing Approach uses information from the business requirements to start the testing process. This includes using the list of requested features to create test cases, expected transaction volume as targets for performance testing, and business priority to prioritize test case execution.
Shift Right Testing Approach uses operational information to start the testing process. This includes using complaint data to enrich regression test cases with the most complained about features and existing revenue data to prioritize test execution.
Both Shift Left and Shift Right approaches are used together in testing to improve test quality by starting with different types of early input information.
This is the Testing Capability document prepared by a Test Manager for work done with present client and used to sell the testing services to other clients.
Shift left - find defects earlier through automated test and deploymentClaudia Ring
Do you know how much time it takes or how that translates into dollars lost every time you fix a defect in development, QA, or Production? The cost of application failures or errors increases exponentially the further into the delivery pipeline they are when found. If application defects are discovered by end users in Production, or errors cause a Production outage, the cost can be thousands per second, in addition to the intangible loss of reputation.
So how do you begin to identify defects earlier in software development and prevent them from becoming major, costly errors later on? Join Al Wagner, IBM Technical Evangelist, as he discusses how to "shift left" and;
Incorporate service virtualization and automated testing into development for a more thorough and accurate representation of application quality
Integrate deployment automation with continuous testing to remove wait times on application promotion
Adopt best practices that have proven successful for IBM customers who are currently shifting left
Software Testing Process, Testing Automation and Software Testing TrendsKMS Technology
This is the slide deck that KMS Technology's experts shared useful information about latest and greatest achievements of software testing field with lecturers of HCMC University of Industry.
The document discusses how the role of testers has evolved over time as business and technology changes accelerated. It describes how testing jobs now require strong programming skills. It also presents a model that positions testing as a team activity that provides empirical evidence across many dimensions to support product quality. The document advocates for testers to think analytically, be curious and critical, and apply their skills broadly to contribute in various roles on a team.
This document provides an overview of exploratory testing techniques. It discusses that exploratory testing involves simultaneous learning, test design, and test execution. Exploratory testing is tester-centric and focuses on problem solving strategies like heuristics rather than scripts. The document dispels some myths about exploratory testing, including that it is unstructured and cannot involve documentation. It provides examples of how documents can be used for reflection, information sharing, and reporting in exploratory testing.
Agile Testing – embedding testing into agile software development lifecycle Kari Kakkonen
My presentation on Agile Testing, including a tuning concept and a case study of agile testing choices in a project, held 16 of June, 2014 at a customer internal seminar.
Agile testing principles and practices - Anil KaradeIndicThreads
Traditional test processes are not adaptive to extensive changes in software. Agile process emphasizes on ability to adapt to changing business needs, customer collaboration, integrated teams and frequent delivery of business values. Agile is an umbrella term that describes a variety of methods including XP and Scrum.
The talk will discuss pitfalls of the traditional testing process. Traditional testing process happens very late in the SDLC Where as Agile process focuses on test-first approach. The talk will explain benefits of going agile. Principles and practices of agile process will be discussed and agile methodologies Scrum and Extreme Programming will be discussed in detail. Purpose of Scrum, its effectiveness, timings and managing the scrum will be discussed. Some of the practices for XP like Pair Programming, Test Driven Development will be discussed. The Talk will also cover the QA role in agile world. The talk will cover the implementation issues while shifting from traditional to agile process. Talk will also include an interactive game for illustration of concepts.
Enterprise QA and Application Testing ServicesCygnet Infotech
Cygnet’s innovation and insight-driven software testing services have paved way for numerous path-breaking software applications. Our meticulous approach towards application testing eliminates pesky bugs, reduces the time-to-market while optimizing the total-cost-of-ownership.
Let's explore what is agile testing, how agile testing is different than traditional testing. What practices team has to adopt to have parallel testing and how to create your own test automation framework. Test automation frameworks using cucumber, selenium, junit, nunit, rspec, coded UI etc.
This document provides an overview and agenda for a presentation on automation testing using IBM Rational Functional Tester. It discusses what automation testing is, why it is useful, and when it should be implemented. It also addresses common myths about automation testing and provides tips for successful automation. Finally, it covers features of IBM Rational Functional Tester, including how to set up a test environment and record scripts to automate testing.
Developing a Testing Strategy for DevOps SuccessDevOps.com
To achieve rapid time-to-market, businesses have embraced DevOps, which places a premium on speed and efficiency. But speed is not the only measure of DevOps success. To release better software faster, enterprises must optimize testing strategy and embed a culture of quality within their DevOps processes.
In this webinar, you will learn:
How to transform QA from a bottleneck to a speed enabler
How to integrate quality and increase visibility throughout the SDLC
How to help your VPs and Directors gauge the success of their current quality initiatives
Software Testing: History, Trends, Perspectives - a Brief OverviewSoftheme
In this presentation you can learn about different types of software testing, new technologies and methodologies. It contains an overview of software testing perspectives.
QualiTest provides load and performance testing services to determine a system's behavior under normal and peak load conditions. Their testing process identifies maximum operating capacity and elements that cause degradation. They ensure applications can handle predicted traffic volumes. QualiTest uses various load testing tools and methodologies to simulate real-world usage and stress test systems. Their testing delivers reports on defects, tool evaluations, and ongoing support for quality improvement.
Testing is the process of validating and verifying software to ensure it meets specifications and functions as intended. There are different levels of testing including unit, integration, system, and acceptance testing. An important part of testing is having a test plan that outlines the test strategy, cases, and process to be followed. Testing helps find defects so the product can be improved.
This document provides an overview of agile testing. It discusses what agile testing is, common agile testing strategies and stages, principles of agile testing, advantages such as reduced time and money and regular feedback, challenges like compressed testing cycles and minimal time for planning, and concludes that communication between teams is key to agile testing success. The agile testing life cycle involves four stages: iteration 0 for initial setup, construction iterations for ongoing testing, release for deployment, and production for maintenance. Principles include testing moving the project forward, testing as a continuous activity, everyone on the team participating in testing, and reducing feedback loops.
This document discusses adapting testing roles and processes to an agile development methodology. It notes that in agile, testers are full team members who participate in planning and requirements analysis from the start of each sprint. Testing activities occur throughout development rather than just at the end. Challenges in transitioning include changing traditional testing roles and resistance to change, while benefits include more transparent communication and continuous feedback between testers and developers. The document provides examples of agile testing practices and recommendations for improving testing efficiency such as increased test automation and planning.
After doing testing on multiple Agile projects, I have come to realize certain aspects about the process and techniques that are common across projects. Some things I have learned along the way, some, by reflection on the mistakes / sub-optimal things that I did.
I have written and published my thoughts around the "Agile QA Process", more particularly what techniques can be used to test effectively in the Iterations.
The document provides an overview of testing practices and services at Birlasoft focused on the financial services industry. It lists key service areas including application development, validation, verification, and maintenance. It also lists industry experience in areas like mortgages, loans, credit cards, and wealth management. Finally, it outlines various testing types and solutions offered as well as examples of clients.
Manual testing involves manually testing software by playing the role of an end user and using test cases to ensure correct behavior. It is important early in development when automation is not possible and for testing visual elements. A test plan is a document that outlines test objectives, workflows and processes while a test case specifies conditions to determine if a feature works as intended. Both exploratory and black/white box testing have pros and cons for finding bugs. Bugzilla is a bug tracking system that helps developers manage issues.
The Heuristic Test Strategy Model provides a framework for designing effective test strategies. It involves considering four key areas: 1) the project environment including resources, constraints, and other factors; 2) the product elements to be tested; 3) quality criteria such as functionality, usability, and security; and 4) appropriate test techniques to apply. Some common test techniques include functional testing, domain testing, stress testing, flow testing, and scenario testing.
- High-Performance Teams: Core Protocols for Psychological Safety and EIRichard Kasperowski
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help alleviate symptoms of mental illness and boost overall mental well-being.
Estimating in Software Development: No Silver Bullets AllowedTechWell
What do poker, Greek oracles, an Italian mathematician from the Middle Ages, and the path of hurricanes have in common? Given the title of this presentation, chances are it has something to do with estimation, and you'll have to attend this session to get the full connection. Kent McDonald explores the challenges and realities of trying to estimate software-related knowledge work-analysis, testing, development, and the entire project effort. A major challenge is that there are no guaranteed ways to arrive at perfectly accurate estimates, which not surprisingly is why they are called estimates. Kent introduces and gives you a chance to practice quick and practical estimating techniques that will work in different situations-guesstimating, break it down and add it up, and planning poker. Kent has found that these "lite" estimation techniques are almost always just as informative as the ones you just spent six weeks formulating.
In today’s market, global outreach, quick time to release, and a feature rich design are the major factors that determine a product’s success. Organizations are constantly on the lookout for innovative testing techniques to match these driving forces. Crowdsourced testing is a paradigm increasing in popularity because it addresses these factors through its scale, flexibility, cost effectiveness, and fast turnaround. Join Rajini Padmanaban and Mukesh Sharma as they describe what it takes to implement a crowdsourced testing effort including its definition, models, relevance to today’s development world, and challenges and mitigation strategies. Rajini and Mukesh share the facts and myths about crowdsourced testing. They span a range of theory and practice including case studies of real-life experiences and exercises to illustrate the message, and explain what it takes to maximize the benefits of a crowdsourced test implementation.
Agile Testing – embedding testing into agile software development lifecycle Kari Kakkonen
My presentation on Agile Testing, including a tuning concept and a case study of agile testing choices in a project, held 16 of June, 2014 at a customer internal seminar.
Agile testing principles and practices - Anil KaradeIndicThreads
Traditional test processes are not adaptive to extensive changes in software. Agile process emphasizes on ability to adapt to changing business needs, customer collaboration, integrated teams and frequent delivery of business values. Agile is an umbrella term that describes a variety of methods including XP and Scrum.
The talk will discuss pitfalls of the traditional testing process. Traditional testing process happens very late in the SDLC Where as Agile process focuses on test-first approach. The talk will explain benefits of going agile. Principles and practices of agile process will be discussed and agile methodologies Scrum and Extreme Programming will be discussed in detail. Purpose of Scrum, its effectiveness, timings and managing the scrum will be discussed. Some of the practices for XP like Pair Programming, Test Driven Development will be discussed. The Talk will also cover the QA role in agile world. The talk will cover the implementation issues while shifting from traditional to agile process. Talk will also include an interactive game for illustration of concepts.
Enterprise QA and Application Testing ServicesCygnet Infotech
Cygnet’s innovation and insight-driven software testing services have paved way for numerous path-breaking software applications. Our meticulous approach towards application testing eliminates pesky bugs, reduces the time-to-market while optimizing the total-cost-of-ownership.
Let's explore what is agile testing, how agile testing is different than traditional testing. What practices team has to adopt to have parallel testing and how to create your own test automation framework. Test automation frameworks using cucumber, selenium, junit, nunit, rspec, coded UI etc.
This document provides an overview and agenda for a presentation on automation testing using IBM Rational Functional Tester. It discusses what automation testing is, why it is useful, and when it should be implemented. It also addresses common myths about automation testing and provides tips for successful automation. Finally, it covers features of IBM Rational Functional Tester, including how to set up a test environment and record scripts to automate testing.
Developing a Testing Strategy for DevOps SuccessDevOps.com
To achieve rapid time-to-market, businesses have embraced DevOps, which places a premium on speed and efficiency. But speed is not the only measure of DevOps success. To release better software faster, enterprises must optimize testing strategy and embed a culture of quality within their DevOps processes.
In this webinar, you will learn:
How to transform QA from a bottleneck to a speed enabler
How to integrate quality and increase visibility throughout the SDLC
How to help your VPs and Directors gauge the success of their current quality initiatives
Software Testing: History, Trends, Perspectives - a Brief OverviewSoftheme
In this presentation you can learn about different types of software testing, new technologies and methodologies. It contains an overview of software testing perspectives.
QualiTest provides load and performance testing services to determine a system's behavior under normal and peak load conditions. Their testing process identifies maximum operating capacity and elements that cause degradation. They ensure applications can handle predicted traffic volumes. QualiTest uses various load testing tools and methodologies to simulate real-world usage and stress test systems. Their testing delivers reports on defects, tool evaluations, and ongoing support for quality improvement.
Testing is the process of validating and verifying software to ensure it meets specifications and functions as intended. There are different levels of testing including unit, integration, system, and acceptance testing. An important part of testing is having a test plan that outlines the test strategy, cases, and process to be followed. Testing helps find defects so the product can be improved.
This document provides an overview of agile testing. It discusses what agile testing is, common agile testing strategies and stages, principles of agile testing, advantages such as reduced time and money and regular feedback, challenges like compressed testing cycles and minimal time for planning, and concludes that communication between teams is key to agile testing success. The agile testing life cycle involves four stages: iteration 0 for initial setup, construction iterations for ongoing testing, release for deployment, and production for maintenance. Principles include testing moving the project forward, testing as a continuous activity, everyone on the team participating in testing, and reducing feedback loops.
This document discusses adapting testing roles and processes to an agile development methodology. It notes that in agile, testers are full team members who participate in planning and requirements analysis from the start of each sprint. Testing activities occur throughout development rather than just at the end. Challenges in transitioning include changing traditional testing roles and resistance to change, while benefits include more transparent communication and continuous feedback between testers and developers. The document provides examples of agile testing practices and recommendations for improving testing efficiency such as increased test automation and planning.
After doing testing on multiple Agile projects, I have come to realize certain aspects about the process and techniques that are common across projects. Some things I have learned along the way, some, by reflection on the mistakes / sub-optimal things that I did.
I have written and published my thoughts around the "Agile QA Process", more particularly what techniques can be used to test effectively in the Iterations.
The document provides an overview of testing practices and services at Birlasoft focused on the financial services industry. It lists key service areas including application development, validation, verification, and maintenance. It also lists industry experience in areas like mortgages, loans, credit cards, and wealth management. Finally, it outlines various testing types and solutions offered as well as examples of clients.
Manual testing involves manually testing software by playing the role of an end user and using test cases to ensure correct behavior. It is important early in development when automation is not possible and for testing visual elements. A test plan is a document that outlines test objectives, workflows and processes while a test case specifies conditions to determine if a feature works as intended. Both exploratory and black/white box testing have pros and cons for finding bugs. Bugzilla is a bug tracking system that helps developers manage issues.
The Heuristic Test Strategy Model provides a framework for designing effective test strategies. It involves considering four key areas: 1) the project environment including resources, constraints, and other factors; 2) the product elements to be tested; 3) quality criteria such as functionality, usability, and security; and 4) appropriate test techniques to apply. Some common test techniques include functional testing, domain testing, stress testing, flow testing, and scenario testing.
- High-Performance Teams: Core Protocols for Psychological Safety and EIRichard Kasperowski
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help alleviate symptoms of mental illness and boost overall mental well-being.
Estimating in Software Development: No Silver Bullets AllowedTechWell
What do poker, Greek oracles, an Italian mathematician from the Middle Ages, and the path of hurricanes have in common? Given the title of this presentation, chances are it has something to do with estimation, and you'll have to attend this session to get the full connection. Kent McDonald explores the challenges and realities of trying to estimate software-related knowledge work-analysis, testing, development, and the entire project effort. A major challenge is that there are no guaranteed ways to arrive at perfectly accurate estimates, which not surprisingly is why they are called estimates. Kent introduces and gives you a chance to practice quick and practical estimating techniques that will work in different situations-guesstimating, break it down and add it up, and planning poker. Kent has found that these "lite" estimation techniques are almost always just as informative as the ones you just spent six weeks formulating.
In today’s market, global outreach, quick time to release, and a feature rich design are the major factors that determine a product’s success. Organizations are constantly on the lookout for innovative testing techniques to match these driving forces. Crowdsourced testing is a paradigm increasing in popularity because it addresses these factors through its scale, flexibility, cost effectiveness, and fast turnaround. Join Rajini Padmanaban and Mukesh Sharma as they describe what it takes to implement a crowdsourced testing effort including its definition, models, relevance to today’s development world, and challenges and mitigation strategies. Rajini and Mukesh share the facts and myths about crowdsourced testing. They span a range of theory and practice including case studies of real-life experiences and exercises to illustrate the message, and explain what it takes to maximize the benefits of a crowdsourced test implementation.
This document provides an overview of a presentation titled "Managing Multiple Teams at Scale with Scrum and Lean" given by Ken Pugh. It discusses managing complexity and size in applications, lean principles, releasing and coordination across multiple teams, roles at different levels including team, program, and portfolio levels, and using frameworks like Scrum and Kanban at each level. The document contains diagrams and outlines to illustrate concepts like concurrently and dependently developable work, levels of coordination, and roles in scaled frameworks.
An Automation Culture: The Key to Agile SuccessTechWell
Geoff Meyer presented on establishing an automation culture within agile organizations. He discussed challenges that Dell encountered when adopting test automation, such as overemphasis on UI testing and lack of automation skills. Meyer outlined opportunities for automation beyond test cases, including environment setup. He emphasized the importance of identifying focus areas, establishing standards and communities, developing workforce skills, and operationalizing automation. Maintaining the culture requires continuous integration, skills development, and recognizing automation as a shared responsibility.
Danger! Danger! Your Mobile Applications Are Not SecureTechWell
A new breed of mobile devices with sophisticated processors and ample storage has given rise to sophisticated applications that move more and more data and business logic to devices. The result is significant and potentially dangerous security challenges, especially for location-aware mobile applications and those storing sensitive or valuable data on devices. To counter these risks, Johannes Ullrich introduces and demonstrates design strategies you can use to mitigate these risks and make applications safer and less vulnerable. Johannes illustrates design patterns to: co-validate data on both the client and server; authenticate transactions on the server; and store only authenticated and access-controlled data on the client. Learn to apply these solutions without losing access to powerful HTML5 JavaScript APIs such as those required for location-based mobile applications. Johannes shares the source code of a location-based mobile application used to organize the cataloging of historic buildings.
Database Development: The Object-oriented and Test-driven WayTechWell
As developers, we've created heuristics that help us build robust systems and employed test-driven development (TDD) to improve code design and counter instability. Yet object-oriented development principles and TDD have failed to gain traction in the database world. That’s because database development involves an additional driving force-the data. Max Guernsey shows how to treat databases as objects with classes of their own-rather than as containers of objects-and how to drive database designs from tests. He illustrates a way to give these database classes the ability to upgrade old data without introducing undue risk. Max also shares how to apply good object-oriented design principles to database classes and how to enforce semantic connections between databases and clients. Max demonstrates how it all works together, ensuring that your production databases work exactly the same as test databases, minimizing the risk of design changes, and enabling client applications to more easily keep up with database changes.
Better Test Designs to Drive Test Automation ExcellenceTechWell
Test execution automation is often seen as a technical challenge-a matter of applying the right technology, tools, and smart programming talent. However, such efforts and projects often fail to meet expectations with results that are difficult to manage and maintain-especially for large and complex systems. Hans Buwalda describes how the choices you make for designing tests can make-or break-a test automation project. Join Hans to discover why good automated tests are not the same as the automation of good manual tests and how to break down tests into modules-building blocks-in which each has a clear scope and purpose. See how to design test cases within each module to reflect that module's scope and nothing more. Hans explains how to tie modules together with a keyword-based test automation framework that separates the automation details from the test itself to enhance maintainability and improve ROI.
Using Non-Violent Communication Skills for Managing Team ConflictTechWell
“Going agile” has transformed thousands of workplaces into groups of self-directed teams, more engaged and increasingly more productive. Knowledge workers report increased job satisfaction, strong team identity, and camaraderie. One of the secrets of high performing teams is their ability to manage conflict in ways that support team cohesion, deepen trust, and reinforce commitment to team greatness. Agile practices value individuals and interactions over processes and tools. Sounds great on paper! How do you live that? How do you work effectively with “difficult people” whether teammates, your boss, or stakeholders in your project? Pat Arcady identifies what is at the core of disagreement, presents a simple four-step protocol for managing conflict, and introduces three key distinctions to make for converting an argument into a meaningful discussion. Practice applying these concepts to your own work situations. This is an experiential session, focused on practical applications for you at your job.
Information Obfuscation: Protecting Corporate DataTechWell
With corporate data breaches occurring at an ever-alarming rate, all levels of organizations are struggling with ways to protect corporate data assets. Rather than choosing one or two of the many options available, Michael Jay Freer believes that the best approach is a combination of tools and practices to address the specific threats. To get you started, Michael Jay introduces the myriad of information security tools companies are using today: firewalls, virus controls, access and authentication controls, separation of duties, multi-factor authentication, data masking, banning user-developed MS-Access databases, encrypting data (both in-flight and at-rest), encrypting emails and folders, disabling jump drives, limiting web access, and more. Then, he dives deeper into data masking and describes a powerful data-masking language. Explore how to develop standard masking business-rules and the best industry practices for manipulating masked data. You can get started slowly with information obfuscation without attempting to "boil the ocean."
Enterprise Lean-Agile: It’s More Than ScrumTechWell
Introducing agile development into a large enterprise is like creating a bubble of sanity in the midst of bedlam. Unless the sanity spreads, the effort is ultimately frustrating, frustrated—and fails. Jeff Marr describes the web of the enterprise ecosystem and presents strategies to build a common agile and lean vocabulary and set of practices within your organization. The lean/agile tenets must be understandable to and appropriate for executive leaders, non-agile product development teams, hardware development, manufacturing, customer support, sales, regulatory compliance, and other elements of the enterprise. Jeff describes how enterprises typically view agile and ways common misconceptions play to your advantage and disadvantage. Finally, Jeff describes an approach to establishing partnerships of mutual interest across the enterprise. If you are a leader, champion, coach, or team member struggling with or preparing for agile adoption in the enterprise, you’ll take away invaluable tips to help you avoid pitfalls, improve communication, and spread the sanity.
Misconceptions abound about the way requirements fit—or don’t fit—into agile projects. Is “agile requirements” an oxymoron—two contradictory terms joined together? How is it possible for requirements to be agile? Do agile projects even need requirements? In reality, requirements are the basis for planning, analyzing, developing, and delivering agile projects. Paul Reed shares the value of requirements analysis on agile projects, the ways requirements form the basis for agile planning, and explains how effective agile teams collaborate to develop requirements. Drawing on what we know about chaos theory, complex adaptive systems, metrics on software projects, and practical application on numerous agile projects, discover how agile and requirements are congruent. Learn how agile and requirements combine to form a sound and sensible union that drives successful delivery of business value. Leave with a clear understanding of how requirements done right leverage agile practices and how agile projects depend on requirements to deliver business value.
André Dhondt presented on speed grooming requirements with SAFe. He discussed how normal backlog grooming creates pressure due to stories not being ready and dependencies not being identified. The SAFe framework addresses this with a speed grooming schedule that incorporates dedicated grooming sessions weekly to ensure stories are ready for planning. Key aspects of speed grooming include strict separation of defining what is needed versus how it will be implemented, progressive elaboration of stories, and inspecting and adapting the process. The goal is to respect people's time by ensuring stories are properly defined before planning begins.
In the tradition of James Whittaker’s book series How to Break … Software, Jon Hagar applies the testing “attack” concept to the domain of embedded software systems. Jon defines the sub-domain of embedded software and examines the issues of product failure caused by defects in that software. Next, he shares a set of attacks against embedded software based on common modes of failure that testers can direct against their own software. For specific attacks, Jon explains when and how to conduct the attack, as well as why the attack works to find bugs. In addition to learning these testing skills, attendees get to practice the attacks on a device—a robot that Jon will bring to the tutorial—containing embedded software. Specific attack methods considered include data issues, computation and control structures, hardware-software interfaces, and communications.
A test strategy is the set of ideas that guides your test design. It's what explains why you test this instead of that, and why you test this way instead of that way. Strategic thinking matters because testers must make quick decisions about what needs testing right now and what can be left alone. You must be able to work through major threads without being overwhelmed by tiny details. James Bach describes how test strategy is organized around risk but is not defined before testing begins. Rather, it evolves alongside testing as we learn more about the product. We start with a vague idea of our strategy, organize it quickly, and document as needed in a concise way. In the end, the strategy can be as formal and detailed as you want it to be. In the beginning, though, we start small. If you want to focus on testing and not paperwork, this approach is for you.
This document provides an introduction to software testing for startups. It discusses that testing early in the development cycle results in faster development, better software, and enhanced investment appeal. It recommends creating test cases based on functional specifications and menus. The document outlines six principles of testing, including that you cannot test every scenario and defects congregate in particular areas. It recommends testing frequently with both developers and testers working closely together.
Testing is done throughout development to minimize risks. Testers evaluate the product, create test conditions, and identify potential issues to improve quality. Effective testing considers coverage of the product's structure, functions, data, interfaces, platform, and operations through accurate models and test procedures. Testers communicate risks and results so informed decisions can be made.
The correct answer is c. The quality of the information used to develop the tests is a factor that influences the test effort involved in most projects. Factors like requirements documentation, software size, life cycle model used, process maturity, time constraints, availability of skilled resources, and test results all impact the test effort.
Exploratory Testing - A Whitepaper by RapidValueRapidValue
Exploratory testing is a hands-on approach that involves simultaneous test design, execution, and learning. It minimizes planning and maximizes test execution. Exploratory testing is beneficial for situations with time constraints or limited product knowledge, as it reduces test design time by designing and executing tests in parallel. Key advantages include finding important bugs, increasing test coverage, and enhancing understanding of the product being tested.
The document provides an overview of software testing fundamentals including definitions of testing, why testing is necessary, quality versus testing, general testing vocabulary, testing objectives, and general testing principles. It defines software testing as verifying and validating that software meets requirements, works as expected, and discusses how testing is needed because humans make mistakes and software errors can have expensive and dangerous consequences. The document also provides definitions of quality, contrasts popular versus technical views of quality, and outlines key aspects of quality like functionality, reliability, and value.
Trends in Software Testing: There has been a slow realization among the top executives that simply outsourcing testing to the lowest bidder is not resulting in a sufficient level of quality in their software products. In this session, Paul Holland will discuss how American companies are starting to reconsider “factory school” testing and are no longer satisfied with the current situation of simply outsourcing their “checking”. As the development side of software continues its dramatic shift toward Agile development – what role can testers have and how can testers still add value?
Agile Testing: Best Practices and Methodology Zoe Gilbert
Agile testing focuses on delivering value to customers through frequent testing and feedback. It differs from the traditional waterfall model which separates development and testing. The document discusses four main agile testing methodologies: behavior driven development, acceptance test driven development, exploratory testing, and session based testing. It also covers the agile testing quadrants framework and how companies can implement best practices for agile testing.
Damian Gordon was a Dutch computer scientist born in 1930 in Rotterdam who received the 1972 Turing Award. He developed several programming language principles including that testing shows presence of bugs but not absence, exhaustive testing is impossible, early testing is important, and defects often cluster in small areas of code. He stressed the importance of risk analysis, test objectives, and regularly updating test cases to find new issues rather than relying on the same cases. Testing approaches must also be tailored to contexts like safety-critical systems versus ecommerce.
This document discusses agile test planning and compares it to traditional test planning methods. It proposes a new template for agile test planning that combines elements of the IEEE 829 test plan standard and James Bach's heuristic test strategy model. The document reviews literature on agile principles, quality assurance, and test planning. It analyzes the components of IEEE 829 and identifies which could be adopted for agile test planning while still adhering to agile values. A research methodology using multiple case studies is presented to analyze the effectiveness of the proposed new agile test planning template.
Test analysis & design good practices@TDT Iasi 17Oct2013Tabăra de Testare
The document discusses test analysis and design best practices. It covers defining test objectives, analyzing test items to identify conditions, designing test cases using various techniques, and ensuring traceability between requirements and test cases. Good practices for writing effective test cases are also presented, such as using a standardized naming convention and writing steps that verify a single testing idea. The importance of analysis and design in translating requirements into testable items prior to execution is emphasized.
Tackling software testing challenges in the agile eraQASymphony
This document provides an overview of testing challenges in the Agile development era and discusses different testing methodologies. It contains introductions to four chapters that will be included in the eBook. The chapters are written by Vu Lam, CEO of QASymphony, and Sellers Smith, Director of Quality Assurance and Agile Evangelist for Silverpop.
The first chapter discusses how testers need to be reimagined for the Agile age. Testers must adopt an Agile mindset and be involved earlier in the development process. They also need tools designed specifically for Agile testing. The second chapter explores different testing methods including automated, exploratory, and user acceptance testing. It advises using
The document discusses strategies for building test strategies in Agile and DevOps environments. It advocates taking an iterative approach to test strategies that can accommodate changing requirements. Documenting test strategies improves communication across teams and helps ensure quality. The document recommends using a "layered approach" to test strategy similar to building a house, with unit testing as the foundation and other testing types building on top of it. This approach facilitates collaboration and success.
A Rapid Introduction to Rapid Software TestingTechWell
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Michael Bolton introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Michael to see how rapid testing focuses on both the mind set and skill set of the individual tester who uses tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
The document provides an overview of building a quality testing framework. It discusses setting goals, defining a vision and timeline, establishing processes and roadmaps, gaining acceptance, and making improvements. Key aspects include test planning, case design, defect management, metrics, involvement of QA early, and continuous improvement. The overall message is that quality assurance principles applied throughout the development and testing process can help prevent bugs and ensure high quality work.
The document discusses how test axioms can be used to advance testing practices. It introduces 16 proposed test axioms grouped into stakeholder, design, and delivery axioms. The axioms represent critical thinking processes for testing any system. The document discusses how the axioms can help testers design test strategies, assess improvement opportunities, and define needed skills. It also proposes a "first equation of testing" that separates axioms, context, values, and thinking to allow for different valid approaches. Additionally, the concept of "quantum testing" is introduced to discuss assigning significance to tests rather than defining their value, which can only be determined by stakeholders.
Software Testing adds organizational value in quantitative and qualitative ways. Successful organizations recognize the importance of quality. Establishing a quality-oriented mindset is the responsibility of business leadership.
Basically this slid will help to Learn software quality testing on scratch level.
Software testing is the quality measures conducted to provide stakeholders with information about the quality of the product or service. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. It is an important part of the entire Software Development ensuring that the functionalities of the system are tested to the finest and assures the quality, correctness and completeness of the product. Software testing, depending on the testing method employed, can be implemented at any time in the development process.
Stages of testing:
o Test planning
o Test Analysis
o Test verification & Construction
o Test execution
o Defect tracking and management
o Quality Analysis Bug tracking
o Report
o Final testing & implementation
This document discusses various topics related to test management. It covers independent and integrated testing, the roles of test leaders and testers, defining the skills test staff need, test plans and estimates, configuration management, risk and testing, and incident management. The document provides information on each of these topics in 1-3 paragraphs per section to outline the key aspects and considerations for test management.
Overcoming The Challenges Faced in Exploratory TestingSarah Elson
It is pretty evident from the name ‘Exploratory Testing’, that, it is the continuous process of learning through a cycle of trial and error. Unlike scripted testing, exploratory testing does not have test cases which can be executed and compared with the results. Rather, it is an intelligent way of testing which calls for innovation and individual thought process of the tester. This is also a reason why despite automation being the big word in the modern day, exploratory testing is a hot topic.
Isabel Evans stopped drawing and painting after being told she was not very good at it, which led to a loss of confidence in her creative and professional abilities. However, she realized that attempting creative activities is important for cognitive and emotional development, and that making mistakes and learning from failures allows for growth. By reengaging with failure through art and with support from others, Isabel was able to regain confidence in her abilities and reboot her career. The document discusses different perspectives on failure and the importance of learning from mistakes.
Instill a DevOps Testing Culture in Your Team and Organization TechWell
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build ArchitectureTechWell
This document summarizes a half-day tutorial on test design for fully automated build architectures presented by Melissa Benua of mParticle at STAREAST 2018. The tutorial covered guiding principles for test design including prioritizing important and reliable tests, structuring automated pipelines around components, packages, and releases, and monitoring test results through code coverage, flaky test handling, and logging versus counters. It also included exercises mapping test cases to functional boundaries and categories of tests to pipeline stages.
System-Level Test Automation: Ensuring a Good StartTechWell
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test StrategyTechWell
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for SuccessTechWell
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your SanityTechWell
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps StrategyTechWell
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOpsTechWell
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—LeadershipTechWell
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile TeamsTechWell
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile GameTechWell
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile TeamsTechWell
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery ProcessTechWell
The document summarizes a presentation about including databases in a continuous integration/delivery process. It discusses treating database code like application code by placing it under version control and integrating databases into the DevOps software development pipeline. This allows databases to be built, tested, and released like other software through continuous integration, delivery, and deployment.
Mobile Testing: What—and What Not—to AutomateTechWell
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for SuccessTechWell
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile TransformationTechWell
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Webinar: Designing a schema for a Data WarehouseFederico Razzoli
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
1. MG
AM Tutorial
9/30/2013 8:30:00 AM
"Rapid Software Testing:
Strategy"
Presented by:
James Bach
Satisfice Inc
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073
888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
2. James Bach
Satisfice, Inc.
James Bach is founder and principal consultant of Satisfice, Inc., a software testing and quality
assurance company. In the eighties, James cut his teeth as a programmer, tester, and SQA
manager in Silicon Valley in the world of market-driven software development. For nearly ten
years, he has traveled the world teaching rapid software testing skills and serving as an expert
witness on court cases involving software testing.
4. What is Rapid Testing?
Rapid testing is a mind-set
and a skill-set of testing
focused on how to do testing
more quickly,
less expensively,
with excellent results.
This is a general testing methodology.
It adapts to any kind of project or product.
5. The Premises of Rapid Testing
1.
Software projects and products are relationships between people, who are
creatures both of emotion and rational thought.
2.
Each project occurs under conditions of uncertainty and time pressure.
3.
Despite our best hopes and intentions, some degree of inexperience,
carelessness, and incompetence is normal.
A test is an activity; it is performance, not artifacts.
4.
5.
Testing’s purpose is to discover the status of the product and any threats to
its value, so that our clients can make informed decisions about it.
6.
We commit to performing credible, cost-effective testing, and we will inform
our clients of anything that threatens that commitment.
7.
We will not knowingly or negligently mislead our clients and colleagues.
8.
Testers accept responsibility for the quality of their work, although they
cannot control the quality of the product.
6. What is a test strategy?
Test strategy is the set of ideas that guide your choice of tests.
A set of ideas does not necessarily mean
a document. The test strategy may be
entirely in your head. Or it may be in
several heads, and emerge through
discussion, over time.
It may be documented partially on a
whiteboard or Post-Its or in a mindmap.
Or it could be in a formal document all
dressed like Cinderella at the royal ball.
7. What is a test strategy?
Test strategy is the set of ideas that guide your choice of tests.
To guide is to influence but not
necessarily to determine. Testing is
shaped by many factors in addition to
strategy, including opportunities, skills,
mistakes, time pressures, limitations of
tools, testability, and unconscious biases.
8. What is a test strategy?
Test strategy is the set of ideas that guide your choice of tests.
I mean choice in the most expansive sense of the word,
not simply the selection of existing test cases.
Choice of tests includes choices of what tests to design
and how to design them and all decisions made during
test design. It includes choices made during test
execution, too, including how to perform tests and
what mix of tests to perform in response to which
perceived risks.
9. Why have a test strategy?
If you test, then you already have a test strategy, so that’s
not a meaningful question… Here are some better questions:
Why have an explicit test strategy?
Why worry about your test strategy?
Why explain it? Why document it?
Why not let the tests “speak for themselves?”
1. To get more credibility, control, agility, and accountability, for
less time and effort.
2. Tests don’t talk.
11. Strategic Thinking Begins with the Context
Mission
Find Important Problems
Assess Quality
Certify to Standard
Fulfill Process Mandates
Satisfy Stakeholders
Assure Accountability
Advise about QA
Advise about Testing
Advise about Quality
Maximize Efficiency
Minimize Cost
Minimize Time
Development
Product
Project Lifecycle
Project Management
Configuration Management
Defect Prevention
Development Team
Test Team
Expertise
Loading
Cohesion
Motivation
Leadership
Project Integration
Requirements
Test
Process
Product Mission
Stakeholders
Quality Criteria
Reference Material
Strategy
Logistics
Work-products
Test Lab
Test Platforms
Test Tools
Test Library
Problem Tracking System
Office Facilities
12. Ask yourself
What testing is easy (even if not very important)?
What testing is important (to find big bugs)?
What testing is expected (by people who matter)?
How can tools help?
Have we advocated for testability?
Are we minimizing administrative costs?
13. Cost as a Simplifying Factor
Try quick tests as well as careful tests
A quick test is a cheap test that has some value
but requires little preparation, knowledge,
or time to perform.
Happy Path
Tour the Product
Sample Data
Variables
Files
Complexity
Menus & Windows
Keyboard & Mouse
–
–
–
–
–
–
Interruptions
Undermining
Adjustments
Dog Piling
Continuous Use
Feature Interactions
Click on Help
14. Cost as a Simplifying Factor
Try quick tests as well as careful tests
A quick test is a cheap test that has some value
but requires little preparation, knowledge,
or time to perform.
Input Constraint Attack
Click Frenzy
Shoe Test
Blink Test
Error Message Hangover
Resource Starvation
Multiple Instances
Crazy Configs
Cheap Tools
15. Value (or Risk) as a Simplifying Factor
Find problems that matter
In general it can vastly simplify testing if we focus on
whether the product has a problem that matters,
rather than whether the product merely satisfies all
relevant standards.
Effective testing requires that we understand
standards as they relate to how our clients value the
product.
Instead of thinking pass vs. fail,
consider thinking problem vs. no problem.
16. One way to make a strategy…
Learn the product.
Think of important potential problems.
Think of how to search the product for those problems.
Think of how to search the product, in general.
1.
2.
3.
4.
Think of ways that:
will take advantage of the resources you have.
comprise a mix of different techniques.
comprise something that you really can actually do.
serve the specific mission you are expected to fulfill.
19. Risk-Based Test Project Cycle:
Testing itself is risk analysis.
Analyze
Potential
Risks
New
Project
Long
loop
Perform
Appropriate
Testing
Exploratory
vs. Scripted
Short
loop
Experience
Problems &
Potentialities
Experience
Problems
In the Field
ship
Analyze
Actual
Risks
20. A Heuristic Test Strategy Model
Project
Environment
Tests
Quality
Criteria
18
Product
Elements
Perceived
Quality
21. A Heuristic Test Strategy Model
Project
Environment
Tests
Quality
Criteria
19
Product
Elements
Perceived
Quality
23. Designed by James Bach
james@satisfice.com
www.satisfice.com
Copyright 1996-2013, Satisfice, Inc.
Version 5.2
6/23/2013
The Heuristic Test Strategy Model is a set of patterns for designing a test strategy. The immediate purpose of
this model is to remind testers of what to think about when they are creating tests. Ultimately, it is intended to
be customized and used to facilitate dialog and direct self-learning among professional testers.
Project Environment includes resources, constraints, and other elements in the project that may enable or
hobble our testing. Sometimes a tester must challenge constraints, and sometimes accept them.
Product Elements are things that you intend to test. Software is complex and invisible. Take care to cover all of
it that matters, not just the parts that are easy to see.
Quality Criteria are the rules, values, and sources that allow you as a tester to determine if the product has
problems. Quality criteria are multidimensional and often hidden or self-contradictory.
Test Techniques are heuristics for creating tests. All techniques involve some sort of analysis of project
environment, product elements, and quality criteria.
Perceived Quality is the result of testing. You can never know the "actual" quality of a software product, but
through the application of a variety of tests, you can make an informed assessment of it.
-1-
24. General Test Techniques
A test technique is a heuristic for creating tests. There are many interesting techniques. The list includes nine general
techniques. By “general technique” we mean that the technique is simple and universal enough to apply to a wide variety
of contexts. Many specific techniques are based on one or more of these nine. And an endless variety of specific test
techniques may be constructed by combining one or more general techniques with coverage ideas from the other lists in
this model.
Function Testing
Claims Testing
Test what it can do
Verify every claim
1.
2.
3.
4.
Identify things that the product can do (functions and
sub-functions).
Determine how you’d know if a function was capable of
working.
Test each function, one at a time.
See that each function does what it’s supposed to do and
not what it isn’t supposed to do.
1.
2.
3.
4.
Identify reference materials that include claims about
the product (implicit or explicit). Consider SLAs, EULAs,
advertisements, specifications, help text, manuals, etc.
Analyze individual claims, and clarify vague claims.
Verify that each claim about the product is true.
If you’re testing from an explicit specification, expect it
and the product to be brought into alignment.
Domain Testing
User Testing
Divide and conquer the data
Involve the users
1.
2.
3.
Look for any data processed by the product. Look at
outputs as well as inputs.
Decide which particular data to test with. Consider
things like boundary values, typical values, convenient
values, invalid values, or best representatives.
Consider combinations of data worth testing together.
1.
2.
3.
4.
5.
Identify categories and roles of users.
Determine what each category of user will do (use
cases), how they will do it, and what they value.
Get real user data, or bring real users in to test.
Otherwise, systematically simulate a user (be careful—
it’s easy to think you’re like a user even when you’re
not).
Powerful user testing is that which involves a variety of
users and user roles, not just one.
Stress Testing
Risk Testing
Overwhelm the product
Imagine a problem, then look for it.
1.
2.
3.
Look for sub-systems and functions that are vulnerable
to being overloaded or “broken” in the presence of
challenging data or constrained resources.
Identify data and resources related to those subsystems and functions.
Select or generate challenging data, or resource
constraint conditions to test with: e.g., large or complex
data structures, high loads, long test runs, many test
cases, low memory conditions.
1.
2.
3.
4.
5.
What kinds of problems could the product have?
Which kinds matter most? Focus on those.
How would you detect them if they were there?
Make a list of interesting problems and design tests
specifically to reveal them.
It may help to consult experts, design documentation,
past bug reports, or apply risk heuristics.
Flow Testing
Automatic Checking
Do one thing after another
Check a million different facts
1.
2.
3.
Perform multiple activities connected end-to-end; for
instance, conduct tours through a state model.
Don’t reset the system between actions.
Vary timing and sequencing, and try parallel threads.
1.
2.
3.
4.
5.
6.
Scenario Testing
Test to a compelling story
1.
2.
3.
Begin by thinking about everything going on around the
product.
Design tests that involve meaningful and complex
interactions with the product.
A good scenario test is a compelling story of how
someone who matters might do something that matters
with the product.
-2-
Look for or develop tools that can perform a lot of
actions and check a lot things.
Consider tools that partially automate test coverage.
Consider tools that partially automate oracles.
Consider automatic change detectors.
Consider automatic test data generators.
Consider tools that make human testing more powerful.
25. Project Environment
Creating and executing tests is the heart of the test project. However, there are many factors in the project environment
that are critical to your decision about what particular tests to create. In each category, below, consider how that factor
may help or hinder your test design process. Try to exploit every resource.
Mission. Your purpose on this project, as understood by you and your customers.
Do you know who your customers are? Whose opinions matter? Who benefits or suffers from the work you do?
Do you know what your customers expect of you on this project? Do you agree?
Maybe your customers have strong ideas about what tests you should create and run.
Maybe they have conflicting expectations. You may have to help identify and resolve those.
Information. Information about the product or project that is needed for testing.
Whom can we consult with to learn about this project?
Are there any engineering documents available? User manuals? Web-based materials? Specs? User stories?
Does this product have a history? Old problems that were fixed or deferred? Pattern of customer complaints?
Is your information current? How are you apprised of new or changing information?
Are there any comparable products or projects from which we can glean important information?
Developer Relations. How you get along with the programmers.
Hubris: Does the development team seem overconfident about any aspect of the product?
Defensiveness: Is there any part of the product the developers seem strangely opposed to having tested?
Rapport: Have you developed a friendly working relationship with the programmers?
Feedback loop: Can you communicate quickly, on demand, with the programmers?
Feedback: What do the developers think of your test strategy?
Test Team. Anyone who will perform or support testing.
Do you know who will be testing? Do you have enough people?
Are there people not on the “test team” that might be able to help? People who’ve tested similar products before and might
have advice? Writers? Users? Programmers?
Are there particular test techniques that the team has special skill or motivation to perform?
Is any training needed? Is any available?
Who is co-located and who is elsewhere? Will time zones be a problem?
Equipment & Tools. Hardware, software, or documents required to administer testing.
Hardware: Do we have all the equipment you need to execute the tests? Is it set up and ready to go?
Automation: Are any test tools needed? Are they available?
Probes: Are any tools needed to aid in the observation of the product under test?
Matrices & Checklists: Are any documents needed to track or record the progress of testing?
Schedule. The sequence, duration, and synchronization of project events
Test Design: How much time do you have? Are there tests better to create later than sooner?
Test Execution: When will tests be executed? Are some tests executed repeatedly, say, for regression purposes?
Development: When will builds be available for testing, features added, code frozen, etc.?
Documentation: When will the user documentation be available for review?
Test Items. The product to be tested.
Scope: What parts of the product are and are not within the scope of your testing responsibility?
Availability: Do you have the product to test? Do you have test platforms available? When do you get new builds?
Volatility: Is the product constantly changing? What will be the need for retesting?
New Stuff: What has recently been changed or added in the product?
Testability: Is the product functional and reliable enough that you can effectively test it?
Future Releases: What part of your tests, if any, must be designed to apply to future releases of the product?
Deliverables. The observable products of the test project.
Content: What sort of reports will you have to make? Will you share your working notes, or just the end results?
Purpose: Are your deliverables provided as part of the product? Does anyone else have to run your tests?
Standards: Is there a particular test documentation standard you’re supposed to follow?
Media: How will you record and communicate your reports?
-3-
26. Product Elements
Ultimately a product is an experience or solution provided to a customer. Products have many dimensions. So, to test well,
we must examine those dimensions. Each category, listed below, represents an important and unique aspect of a product.
Testers who focus on only a few of these are likely to miss important bugs.
Structure. Everything that comprises the physical product.
Code: the code structures that comprise the product, from executables to individual routines.
Hardware: any hardware component that is integral to the product.
Non-executable files: any files other than multimedia or programs, like text files, sample data, or help files.
Collateral: anything beyond software and hardware that is also part of the product, such as paper documents, web links and content,
packaging, license agreements, etc.
Function. Everything that the product does.
Application: any function that defines or distinguishes the product or fulfills core requirements.
Calculation: any arithmetic function or arithmetic operations embedded in other functions.
Time-related: time-out settings; daily or month-end reports; nightly batch jobs; time zones; business holidays; interest calculations; terms and
warranty periods; chronograph functions.
Transformations: functions that modify or transform something (e.g. setting fonts, inserting clip art, withdrawing money from account).
Startup/Shutdown: each method and interface for invocation and initialization as well as exiting the product.
Multimedia: sounds, bitmaps, videos, or any graphical display embedded in the product.
Error Handling: any functions that detect and recover from errors, including all error messages.
Interactions: any interactions between functions within the product.
Testability: any functions provided to help test the product, such as diagnostics, log files, asserts, test menus, etc.
Data. Everything that the product processes.
Input: any data that is processed by the product.
Output: any data that results from processing by the product.
Preset: any data that is supplied as part of the product, or otherwise built into it, such as prefabricated databases, default values, etc.
Persistent: any data that is stored internally and expected to persist over multiple operations. This includes modes or states of the product,
such as options settings, view modes, contents of documents, etc.
Sequences/Combinations: any ordering or permutation of data, e.g. word order, sorted vs. unsorted data, order of tests.
Cardinality: Numbers of objects or fields may vary (e.g. zero, one, many, max, open limit). Some may have to be unique (e.g. database keys).
Big/Little: variations in the size and aggregation of data.
Noise: any data or state that is invalid, corrupted, or produced in an uncontrolled or incorrect fashion.
Lifecycle: transformations over the lifetime of a data entity as it is created, accessed, modified, and deleted.
Interfaces. Every conduit by which the product is accessed or expressed.
User Interfaces: any element that mediates the exchange of data with the user (e.g. navigation, display, data entry).
System Interfaces: any interface with something other than a user, such as other programs, hard disk, network, etc.
API/SDK: Any programmatic interfaces or tools intended to allow the development of new applications using this product.
Import/export: any functions that package data for use by a different product, or interpret data from a different product.
Platform. Everything on which the product depends (and that is outside your project).
External Hardware: hardware components and configurations that are not part of the shipping product, but are required (or
optional) in order for the product to work: systems, servers, memory, keyboards, the Cloud.
External Software: software components and configurations that are not a part of the shipping product, but are required (or
optional) in order for the product to work: operating systems, concurrently executing applications, drivers, fonts, etc.
Internal Components: libraries and other components that are embedded in your product but are produced outside your project.
Operations. How the product will be used.
Users: the attributes of the various kinds of users.
Environment: the physical environment in which the product operates, including such elements as noise, light, and distractions.
Common Use: patterns and sequences of input that the product will typically encounter. This varies by user.
Disfavored Use: patterns of input produced by ignorant, mistaken, careless or malicious use.
Extreme Use: challenging patterns and sequences of input that are consistent with the intended use of the product.
Time. Any relationship between the product and time.
Input/Output: when input is provided, when output created, and any timing relationships (delays, intervals, etc.) among them.
Fast/Slow: testing with “fast” or “slow” input; fastest and slowest; combinations of fast and slow.
Changing Rates: speeding up and slowing down (spikes, bursts, hangs, bottlenecks, interruptions).
Concurrency: more than one thing happening at once (multi-user, time-sharing, threads, and semaphores, shared data).
-4-
27. Quality Criteria Categories
A quality criterion is some requirement that defines what the product should be. By thinking about different kinds of
criteria, you will be better able to plan tests that discover important problems fast. Each of the items on this list can be
thought of as a potential risk area. For each item below, determine if it is important to your project, then think how you
would recognize if the product worked well or poorly in that regard.
Capability. Can it perform the required functions?
Reliability. Will it work well and resist failure in all required situations?
Robustness: the product continues to function over time without degradation, under reasonable conditions.
Error handling: the product resists failure in the case of errors, is graceful when it fails, and recovers readily.
Data Integrity: the data in the system is protected from loss or corruption.
Safety: the product will not fail in such a way as to harm life or property.
Usability. How easy is it for a real user to use the product?
Learnability: the operation of the product can be rapidly mastered by the intended user.
Operability: the product can be operated with minimum effort and fuss.
Accessibility: the product meets relevant accessibility standards and works with O/S accessibility features.
Charisma. How appealing is the product?
Aesthetics: the product appeals to the senses.
Uniqueness: the product is new or special in some way.
Necessity: the product possesses the capabilities that users expect from it.
Usefulness: the product solves a problem that matters, and solves it well.
Entrancement: users get hooked, have fun, are fully engaged when using the product.
Image: the product projects the desired impression of quality.
Security. How well is the product protected against unauthorized use or intrusion?
Authentication: the ways in which the system verifies that a user is who he says he is.
Authorization: the rights that are granted to authenticated users at varying privilege levels.
Privacy: the ways in which customer or employee data is protected from unauthorized people.
Security holes: the ways in which the system cannot enforce security (e.g. social engineering vulnerabilities)
Scalability. How well does the deployment of the product scale up or down?
Compatibility. How well does it work with external components & configurations?
Application Compatibility: the product works in conjunction with other software products.
Operating System Compatibility: the product works with a particular operating system.
Hardware Compatibility: the product works with particular hardware components and configurations.
Backward Compatibility: the products works with earlier versions of itself.
Resource Usage: the product doesn’t unnecessarily hog memory, storage, or other system resources.
Performance. How speedy and responsive is it?
Installability. How easily can it be installed onto its target platform(s)?
System requirements: Does the product recognize if some necessary component is missing or insufficient?
Configuration: What parts of the system are affected by installation? Where are files and resources stored?
Uninstallation: When the product is uninstalled, is it removed cleanly?
Upgrades/patches: Can new modules or versions be added easily? Do they respect the existing configuration?
Administration: Is installation a process that is handled by special personnel, or on a special schedule?
Development. How well can we create, test, and modify it?
Supportability: How economical will it be to provide support to users of the product?
Testability: How effectively can the product be tested?
Maintainability: How economical is it to build, fix or enhance the product?
Portability: How economical will it be to port or reuse the technology elsewhere?
Localizability: How economical will it be to adapt the product for other places?
-5-