Jon Hagar author of "Software Test Attacks to Break Mobile and Embedded Devices" presents Software testing concepts for mobile and imbedded devices in this webinar- hosted by XBOSoft.
The document discusses testing in Agile environments. It covers traditional vs Agile testing approaches, the role of testers in Agile projects, and specific technical skills for Agile testers. In Agile, testing is iterative and incremental, occurring alongside development. Testers collaborate with developers to help define requirements and acceptance criteria, automate tests, and find bugs through exploratory testing. Their role focuses more on communication and facilitating quality than traditional documentation-heavy testing.
Agile Metrics to Boost Software Quality improvementXBOSoft
Why don't metrics apply to Agile development methodologies? Wrong! They Do, but you have to know how and when.
Find out in this webinar (recording) in special collaboration with the Chicago Quality Assurance Association (CQAA).
Agile, a development methodology, designed to allow team members to work iteratively during the development process instead of delivering a final product all at once, is now 20 years old. And when it comes to testing within an Agile process, there are those that use pyramids, and rectangles as mental models for where you should put your effort, or not.
Sometimes, software quality in Agile is mistranslated as the idea that everyone is responsible for software testing. But within Agile software development, ensuring quality is much more than testing and must include activities at different levels, including estimates for the workload for each iteration. Otherwise, testing happens last minute—or sometimes not at all, depending on time constraints. To have a successful Agile team, most software developers know that velocity is an essential component.
But it’s not just about measuring velocity, as velocity is only one factor or measurement for success. There are many other factors to measure when you want to assess the success of your Agile team in delivering a quality product. In this webinar, we specifically look at some key metrics for us the measure the success and progress of our quality in Agile.
Tune in with Philip Lew as he goes through ways you can gather insights in slicing, dicing, and analyzing (and interpreting) data. We’ll use Jira as an example, but you can do this with practically any issue tracking collaboration tool to help your team improve software quality.
Agile Test Management Using Jira and ZephyrXBOSoft
Do you have traceability where you can efficiently determine the cause of defects if there was an unclear requirement? Are you sure your test cases cover your requirements? Can you easily execute targeted regression when you’ve updated your software’s functionality? Now with software development teams mostly working from home or in dispersed geographies, supporting effective collaboration between remote workers is critical. In this XBOSoft quarterly webinar, our CEO, Philip Lew, teams up with BDQ’s CEO Chris Bland, to discuss the problems with working remotely, integrating the phases of testing in development in an Agile, and how this can be done using Zephyr, one of the predominant plugins in the Atlassian marketplace for test management. In this webinar, you will learn how to:
--Link tests with user stories and group tests within test cycles.
--Tie your results (defects) all the way back to user stories for effective defect root cause analysis.
--Classify defects to analyze and prioritize your test efforts.
--Use the traceability matrix with Zephr for deep visibility into your Agile process.
Agile User Acceptance Testing - Incorporating UAT into AgileXBOSoft
This document discusses incorporating user acceptance testing (UAT) into Agile development processes. It provides an overview of XBOSoft, a company dedicated to software quality improvement. It then discusses some common problems with traditional UAT approaches and how UAT can be better integrated into Agile. Key aspects covered include developing epics and user stories, writing acceptance criteria, and defining acceptance tests. The presentation provides examples and best practices for representing requirements in a way that facilitates effective UAT within an Agile framework.
Defect Patterns Analysis for Agile and Waterfall - XBOSoft Webinar with Micha...XBOSoft
Whether you’re waterfall or agile, this presentation will uncover 3 keys to accelerating schedule by managing defect prevention, detection, and remediation by software teams. Actual Industry Case Studies will reveal how to implement an end-to-end defect strategy that maximizes the likelihood of team’s success. Topics covered will include waterfall, Agile, pair programming, test-driven development, and outsourced projects. We’ll also look at techniques that use defect curves to “predict the trajectory” of a project and its Development and QA phases.
Proactive SQA™ Shifting Left w/Proactive Software Quality PracticesXBOSoft
This webinar hosted by XBOSoft featured our guest speaker, Robin Goldsmith. Robin, an expert in software requirements and business analysis, presented how to develop a definition of software quality as a first step any software development process. Although most of what is called SQA today actually is just testing, true SQA is much different from quality control (QC) testing. SQA can and should do far more, contributing proactively to assure the software process in fact does the right things well so it truly produces high quality cheaper, preventing errors or catching them earlier when they can be fixed more easily. This interactive webinar positions SQA and explains the six proactive functions it should perform to provide far greater value.
Is this possible? Artificial Intelligence Based Test Automation but with no AI? Well, according to Jeremias Roessler, it is! Find out how in this quarterly webinar slidedeck with XBOSoft's special guest speaker, Jeremy Rößler. What good are 400 additional AI-generated UI tests, if we don’t want to maintain our existing human-created ones? This question lies at the heart of AI-based test generation. Recheck-web addresses this issue elegantly and without any “AI-magic” … using a whole different approach to test automation. This refreshingly unusual approach to test automation (difference testing) has many advantages over conventional test automation and he shows how to overcome the oracle problem. This approach makes tests easy to create and maintain, robust and more complete. You can use this approach today in your existing UI testing setup for websites (currently available for Selenium/Java, more to come).
This document summarizes a presentation about improving software development practices at a company. It discusses bringing in experts to teach test-driven development, refactoring, and applying agile principles like Scrum. Over several years, it shows how the company gradually adopted more practices like automated unit testing, design principles, embedded agile, and combining agile with Six Sigma. Coaching individual teams and a whole module helped advance skills and standards, but spreading the changes more widely remained a challenge.
The document discusses testing in Agile environments. It covers traditional vs Agile testing approaches, the role of testers in Agile projects, and specific technical skills for Agile testers. In Agile, testing is iterative and incremental, occurring alongside development. Testers collaborate with developers to help define requirements and acceptance criteria, automate tests, and find bugs through exploratory testing. Their role focuses more on communication and facilitating quality than traditional documentation-heavy testing.
Agile Metrics to Boost Software Quality improvementXBOSoft
Why don't metrics apply to Agile development methodologies? Wrong! They Do, but you have to know how and when.
Find out in this webinar (recording) in special collaboration with the Chicago Quality Assurance Association (CQAA).
Agile, a development methodology, designed to allow team members to work iteratively during the development process instead of delivering a final product all at once, is now 20 years old. And when it comes to testing within an Agile process, there are those that use pyramids, and rectangles as mental models for where you should put your effort, or not.
Sometimes, software quality in Agile is mistranslated as the idea that everyone is responsible for software testing. But within Agile software development, ensuring quality is much more than testing and must include activities at different levels, including estimates for the workload for each iteration. Otherwise, testing happens last minute—or sometimes not at all, depending on time constraints. To have a successful Agile team, most software developers know that velocity is an essential component.
But it’s not just about measuring velocity, as velocity is only one factor or measurement for success. There are many other factors to measure when you want to assess the success of your Agile team in delivering a quality product. In this webinar, we specifically look at some key metrics for us the measure the success and progress of our quality in Agile.
Tune in with Philip Lew as he goes through ways you can gather insights in slicing, dicing, and analyzing (and interpreting) data. We’ll use Jira as an example, but you can do this with practically any issue tracking collaboration tool to help your team improve software quality.
Agile Test Management Using Jira and ZephyrXBOSoft
Do you have traceability where you can efficiently determine the cause of defects if there was an unclear requirement? Are you sure your test cases cover your requirements? Can you easily execute targeted regression when you’ve updated your software’s functionality? Now with software development teams mostly working from home or in dispersed geographies, supporting effective collaboration between remote workers is critical. In this XBOSoft quarterly webinar, our CEO, Philip Lew, teams up with BDQ’s CEO Chris Bland, to discuss the problems with working remotely, integrating the phases of testing in development in an Agile, and how this can be done using Zephyr, one of the predominant plugins in the Atlassian marketplace for test management. In this webinar, you will learn how to:
--Link tests with user stories and group tests within test cycles.
--Tie your results (defects) all the way back to user stories for effective defect root cause analysis.
--Classify defects to analyze and prioritize your test efforts.
--Use the traceability matrix with Zephr for deep visibility into your Agile process.
Agile User Acceptance Testing - Incorporating UAT into AgileXBOSoft
This document discusses incorporating user acceptance testing (UAT) into Agile development processes. It provides an overview of XBOSoft, a company dedicated to software quality improvement. It then discusses some common problems with traditional UAT approaches and how UAT can be better integrated into Agile. Key aspects covered include developing epics and user stories, writing acceptance criteria, and defining acceptance tests. The presentation provides examples and best practices for representing requirements in a way that facilitates effective UAT within an Agile framework.
Defect Patterns Analysis for Agile and Waterfall - XBOSoft Webinar with Micha...XBOSoft
Whether you’re waterfall or agile, this presentation will uncover 3 keys to accelerating schedule by managing defect prevention, detection, and remediation by software teams. Actual Industry Case Studies will reveal how to implement an end-to-end defect strategy that maximizes the likelihood of team’s success. Topics covered will include waterfall, Agile, pair programming, test-driven development, and outsourced projects. We’ll also look at techniques that use defect curves to “predict the trajectory” of a project and its Development and QA phases.
Proactive SQA™ Shifting Left w/Proactive Software Quality PracticesXBOSoft
This webinar hosted by XBOSoft featured our guest speaker, Robin Goldsmith. Robin, an expert in software requirements and business analysis, presented how to develop a definition of software quality as a first step any software development process. Although most of what is called SQA today actually is just testing, true SQA is much different from quality control (QC) testing. SQA can and should do far more, contributing proactively to assure the software process in fact does the right things well so it truly produces high quality cheaper, preventing errors or catching them earlier when they can be fixed more easily. This interactive webinar positions SQA and explains the six proactive functions it should perform to provide far greater value.
Is this possible? Artificial Intelligence Based Test Automation but with no AI? Well, according to Jeremias Roessler, it is! Find out how in this quarterly webinar slidedeck with XBOSoft's special guest speaker, Jeremy Rößler. What good are 400 additional AI-generated UI tests, if we don’t want to maintain our existing human-created ones? This question lies at the heart of AI-based test generation. Recheck-web addresses this issue elegantly and without any “AI-magic” … using a whole different approach to test automation. This refreshingly unusual approach to test automation (difference testing) has many advantages over conventional test automation and he shows how to overcome the oracle problem. This approach makes tests easy to create and maintain, robust and more complete. You can use this approach today in your existing UI testing setup for websites (currently available for Selenium/Java, more to come).
This document summarizes a presentation about improving software development practices at a company. It discusses bringing in experts to teach test-driven development, refactoring, and applying agile principles like Scrum. Over several years, it shows how the company gradually adopted more practices like automated unit testing, design principles, embedded agile, and combining agile with Six Sigma. Coaching individual teams and a whole module helped advance skills and standards, but spreading the changes more widely remained a challenge.
HPQC ALM was the tool of choice for organizations to manage their software testing process for decades, however, it is quickly falling out of favor with today’s savvier testers. Learn more in this webinar slide deck.
Evolve or Die: Healthcare IT Testing | QASymphony WebinarQASymphony
Modern software testing for Healthcare Organizations. Learn about best practices for software testing in the healthcare industry featuring Mike Cooper, Chief Quality Officer of Healthcare IT Leaders and Kevin Dunne, VP of Business Development at QASymphony
Integrating hardware development processes (using the Waterfall method / V-model) and Agile software development. This presentation explains the basics of the V-model and how it has evolved into an iterative model, but also tells you about managing hardware and software lifecycle processes in a single release. Then, a live demonstration shows you how to integrate these lifecycles (xLM) in practice.
Closing the Requirements and Testing Loop WebinarQASymphony
QASYMPHONY & BLUEPRINT PARTNER UP
Learn about the new partnership between QASymphony and Blueprint. Connecting software requirements with proper test coverage still remains an age old problem for software development teams. This new partnership will provide alignment between requirements and testing teams of all types to get the visibility and traceability needed to understand their requirements coverage.
In this webinar, Kevin Dunne, QASymphony's VP of Strategy and Business Development and Ruth Zive, VP of Marketing at Blueprint will answer the following questions:
What is QASymphonys qTest Platform?
How is this platform enhanced by Blueprint?
How does the integration between qTest and Blueprint work?
Why does your team need this offering?
Ken Whitaker shares pragmatic techniques to help project managers and software development leaders put into practice innovative scheduling techniques, make consistent customer-centric decisions, reduce project risk, quickly negotiate with product owners the most important project scope, and transition teams to become more agile. Ken shares revealing statistical data on how waterfall is simply not suited for modern-day adaptive software development projects. With fellow participants, you’ll spend time performing a “Scrum walkabout” to get the idea of just how an agile project really works. These best practices are presented to motivate your team to deliver projects on time, every time. Although this tutorial doesn’t incorporate intensive role-play, we’ll have lively interaction that will incorporate lessons learned from actual case studies and attendees’ project experiences. Take away powerful, yet simple, ways to bridge the gap between PMI’s PMBOK® Guide and agile.
Exploratory Testing with JIRA | QASymphony WebinarQASymphony
Kyle McMeekin presented on using JIRA for exploratory testing. He discussed problems with traditional scripted testing approaches and explained exploratory testing as a more flexible parallel process. Exploratory testing allows testers to investigate opportunities, share knowledge, and keep testing engaging. Session-based testing provides structure for exploratory testing by tracking test charters, notes, issues and more. Tools like JIRA Capture and qTest Explorer help capture evidence from exploratory testing sessions.
Shift left, shift right the testing swing.
This deck shows the testing framework we use today in our agile & Devops team. We do Behavior Driven Development (Shift left) and test in production as well (shift right).
Continuous Integration Is for Everyone—Especially DevOpsTechWell
Continuous delivery and deployment are taking center stage in the DevOps conversations. Neither continuous delivery nor deployment are easy to jump into, and both make a lot of assumptions about the applications being released. Continuous integration (CI), however, is for everyone who wants higher development velocity and better quality. CI can be implemented in development shops from brand new to large enterprise teams. When implemented, CI helps the organization take a giant leap into modern development. With the ever-growing expectation for DevOps teams to produce faster, high-quality software releases, continuous testing—a key CI driver—must occur at all stages of the software delivery chain. Chris Riley covers the important tenets of CI metrics, key CI components, testing, infrastructure, and end-to-end testing. Learn how CI can fit into all development shops, and take back strategies for tackling the challenges of a new system including change control, management, and sustainability.
The document discusses the principles and practices of continuous delivery in an agile context. It emphasizes automating the entire software delivery process from code commits through deployment to production to minimize risks and ensure fast, reliable software updates. This includes having automated tests, continuous integration, monitoring systems, and the ability to rollback changes. It also stresses the importance of collaboration across teams to establish a shared goal of delivering value to customers through working software.
If you like the ideas raised in this presentation, don't forget to check out my latest book, Directing the Agile Organisation (http://theagiledirector.com/book).
This document summarizes a presentation on how to build high-performing IT teams. It begins by making the case that high-performing teams are both more agile and reliable based on data. It then discusses identifying the desired organizational state with high trust cultures, aligned goals, and other attributes. Next, it covers aligning incentives across business, development, operations, and quality teams to focus on customer value. The document also reviews common team structures and implementing technical practices like infrastructure as code, version control, peer review, and continuous delivery to measure results.
Soft Skills You Need Are Not Always Taught in ClassTechWell
For years in the software industry, the focus of discussion, programs, and expense has been on career skill development to enhance team performance. To support skill development, a variety of certifications and training opportunities have been created to increase technical knowledge acquisition. Gaining technical knowledge is important, but this knowledge is often secondary to having other skills that are of more value to the organization. Jon Hagar explores these so-called “soft” skills—analysis, rational thought, communication, mentoring, technical debt management, reframing problems, modeling, time management, and social aptitude—and discusses the differences between knowledge from study and practiced skills. Delegates are asked to consider the value and to discuss how to develop and improve such skills. Finally, through an entertaining analogy Jon highlights the differences between skill and knowledge.
Going the Next Step? Agile Values and Hardware Development by Urs BoehmPeter Stevens
Hardware and software development have different requirements for efficient development processes. Properly used, the agile methods can be used successfully here. The speaker shows the differences and shows how agile methods and processes can be used as efficiently as possible for the hardware and hardware-related software development.
Critical Capabilities to Shifting Left the Right WaySmartBear
The concept of testing earlier in the SDLC isn't new, but the term "shift left" has reignited its importance. See how shifting left can help you, and how to do it right.
QA team transition to agile testing at Alcatel LucentAgileSparks
In this session I will outline/explore the journey of a common QA team without coding skills into Agile testing arena. Main focus on Acceptance Test Driven Development and executable specs. The session will be based on a real case study from Alcatel Lucent Haifa. At the end of the session you will understand the concept of executable specs,and ATDD, You will see real example of test implementation in ATDD tool (Cucumber) and will understand the steps required to make such transition with some do/not do tips in tool and process implementation (based on Alcatel case study).
You will get (printed) the suggested implementation plan and do/not do tips of ATDD automation tools implementation
Please visit wingman-sw.com if you would like a copy of the PDF or the associated paper.
Embedded systems development can benefit from Agile software development. This paper and presentation tells you about why you should care, what problems Agile is designed to solve and what agile is. This topic has evolved over the years. I started presenting it in 2004 (or maybe earlier) at the Embedded Systems Conference.
This document discusses managing agile projects using Scrum. It provides an overview of Scrum, including common roles, artifacts, and events like sprints, sprint planning, daily scrums, sprint reviews, and retrospectives. It also discusses how project management practices from PMBOK like scope, schedule, cost can be addressed in Scrum, with the product backlog, release planning, and tracking work remaining. The document aims to explain how to use Scrum for managing agile software development projects.
This document discusses improving project estimation and predicting delivery dates. It begins by noting that detailed estimation does not strongly influence lead times due to typically low flow efficiencies in systems. Lead time histograms are proposed as a better approach to predict completion dates with confidence levels, as they incorporate all system factors without personal bias. Class of service and work item characteristics can identify the most accurate histogram. Considering cost of delay functions alongside histograms helps determine when work should start to balance timely delivery and optimization of resources. The document advocates predicting customer expectations rather than effort or duration and focuses on statistical prediction over detailed planning.
This document discusses the role of a QA Engineer in JIRA. It notes that the QA Engineer works with a team of 15 people including developers, product managers, UX designers, and other QAs. It emphasizes that with Agile development, testing is now a shared responsibility of developers rather than being isolated to testers. Developers are expected to write and execute both manual and automated tests as part of development. The document outlines the development and release process at JIRA, with major releases every 2-3 months and bugfix releases every 2 weeks for the on-demand product. It stresses testing early and often through the development cycle rather than relying on testing at the end. Automated regression tests run on every code change to prevent
This talk will explain the secret of the success of the Eclipse Platform team. The Eclipse Way is an agile software development process that we started right at the beginning when we started to develop Eclipse back in 1999. It was and is used by the Eclipse Platform team and got continuously improved over time. During the session you will hear about all our practices, like milestones, early and iterative planning, continuous integration and the endgame. I will also reveal some of the history behind the Eclipse top-level project.
More details: https://confengine.com/eclipse-summit-2016/proposal/2386/the-eclipse-way
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, Jon 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, 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.
Use Combinatorial Testing for Mobile Device FragmentationJosiah Renaudin
A common problem in mobile systems testing is the number of hardware, operational, and software configurations that need to be tested. For example, the so-called Android fragmentation problem might lead a test team to test hundreds of device and software configurations, yielding thousands or even tens-of-thousands of tests. A branch of mathematics, called combinatorics, and associated tools exist that allow teams to minimize the number of test cases required, while assuring high error finding percentages. Jon Hagar defines the fragmentation problem and then examines test patterns supported by tools that can help improve testing success. Jon outlines how combinatorial test patterns can be applied to other testing situations. To solve real-world fragmentation problems, he identifies specific tools, which you can take back to your project for quick use. Reference work and data are provided to help your team justify adding combinatorial testing to your mobile test activities.
HPQC ALM was the tool of choice for organizations to manage their software testing process for decades, however, it is quickly falling out of favor with today’s savvier testers. Learn more in this webinar slide deck.
Evolve or Die: Healthcare IT Testing | QASymphony WebinarQASymphony
Modern software testing for Healthcare Organizations. Learn about best practices for software testing in the healthcare industry featuring Mike Cooper, Chief Quality Officer of Healthcare IT Leaders and Kevin Dunne, VP of Business Development at QASymphony
Integrating hardware development processes (using the Waterfall method / V-model) and Agile software development. This presentation explains the basics of the V-model and how it has evolved into an iterative model, but also tells you about managing hardware and software lifecycle processes in a single release. Then, a live demonstration shows you how to integrate these lifecycles (xLM) in practice.
Closing the Requirements and Testing Loop WebinarQASymphony
QASYMPHONY & BLUEPRINT PARTNER UP
Learn about the new partnership between QASymphony and Blueprint. Connecting software requirements with proper test coverage still remains an age old problem for software development teams. This new partnership will provide alignment between requirements and testing teams of all types to get the visibility and traceability needed to understand their requirements coverage.
In this webinar, Kevin Dunne, QASymphony's VP of Strategy and Business Development and Ruth Zive, VP of Marketing at Blueprint will answer the following questions:
What is QASymphonys qTest Platform?
How is this platform enhanced by Blueprint?
How does the integration between qTest and Blueprint work?
Why does your team need this offering?
Ken Whitaker shares pragmatic techniques to help project managers and software development leaders put into practice innovative scheduling techniques, make consistent customer-centric decisions, reduce project risk, quickly negotiate with product owners the most important project scope, and transition teams to become more agile. Ken shares revealing statistical data on how waterfall is simply not suited for modern-day adaptive software development projects. With fellow participants, you’ll spend time performing a “Scrum walkabout” to get the idea of just how an agile project really works. These best practices are presented to motivate your team to deliver projects on time, every time. Although this tutorial doesn’t incorporate intensive role-play, we’ll have lively interaction that will incorporate lessons learned from actual case studies and attendees’ project experiences. Take away powerful, yet simple, ways to bridge the gap between PMI’s PMBOK® Guide and agile.
Exploratory Testing with JIRA | QASymphony WebinarQASymphony
Kyle McMeekin presented on using JIRA for exploratory testing. He discussed problems with traditional scripted testing approaches and explained exploratory testing as a more flexible parallel process. Exploratory testing allows testers to investigate opportunities, share knowledge, and keep testing engaging. Session-based testing provides structure for exploratory testing by tracking test charters, notes, issues and more. Tools like JIRA Capture and qTest Explorer help capture evidence from exploratory testing sessions.
Shift left, shift right the testing swing.
This deck shows the testing framework we use today in our agile & Devops team. We do Behavior Driven Development (Shift left) and test in production as well (shift right).
Continuous Integration Is for Everyone—Especially DevOpsTechWell
Continuous delivery and deployment are taking center stage in the DevOps conversations. Neither continuous delivery nor deployment are easy to jump into, and both make a lot of assumptions about the applications being released. Continuous integration (CI), however, is for everyone who wants higher development velocity and better quality. CI can be implemented in development shops from brand new to large enterprise teams. When implemented, CI helps the organization take a giant leap into modern development. With the ever-growing expectation for DevOps teams to produce faster, high-quality software releases, continuous testing—a key CI driver—must occur at all stages of the software delivery chain. Chris Riley covers the important tenets of CI metrics, key CI components, testing, infrastructure, and end-to-end testing. Learn how CI can fit into all development shops, and take back strategies for tackling the challenges of a new system including change control, management, and sustainability.
The document discusses the principles and practices of continuous delivery in an agile context. It emphasizes automating the entire software delivery process from code commits through deployment to production to minimize risks and ensure fast, reliable software updates. This includes having automated tests, continuous integration, monitoring systems, and the ability to rollback changes. It also stresses the importance of collaboration across teams to establish a shared goal of delivering value to customers through working software.
If you like the ideas raised in this presentation, don't forget to check out my latest book, Directing the Agile Organisation (http://theagiledirector.com/book).
This document summarizes a presentation on how to build high-performing IT teams. It begins by making the case that high-performing teams are both more agile and reliable based on data. It then discusses identifying the desired organizational state with high trust cultures, aligned goals, and other attributes. Next, it covers aligning incentives across business, development, operations, and quality teams to focus on customer value. The document also reviews common team structures and implementing technical practices like infrastructure as code, version control, peer review, and continuous delivery to measure results.
Soft Skills You Need Are Not Always Taught in ClassTechWell
For years in the software industry, the focus of discussion, programs, and expense has been on career skill development to enhance team performance. To support skill development, a variety of certifications and training opportunities have been created to increase technical knowledge acquisition. Gaining technical knowledge is important, but this knowledge is often secondary to having other skills that are of more value to the organization. Jon Hagar explores these so-called “soft” skills—analysis, rational thought, communication, mentoring, technical debt management, reframing problems, modeling, time management, and social aptitude—and discusses the differences between knowledge from study and practiced skills. Delegates are asked to consider the value and to discuss how to develop and improve such skills. Finally, through an entertaining analogy Jon highlights the differences between skill and knowledge.
Going the Next Step? Agile Values and Hardware Development by Urs BoehmPeter Stevens
Hardware and software development have different requirements for efficient development processes. Properly used, the agile methods can be used successfully here. The speaker shows the differences and shows how agile methods and processes can be used as efficiently as possible for the hardware and hardware-related software development.
Critical Capabilities to Shifting Left the Right WaySmartBear
The concept of testing earlier in the SDLC isn't new, but the term "shift left" has reignited its importance. See how shifting left can help you, and how to do it right.
QA team transition to agile testing at Alcatel LucentAgileSparks
In this session I will outline/explore the journey of a common QA team without coding skills into Agile testing arena. Main focus on Acceptance Test Driven Development and executable specs. The session will be based on a real case study from Alcatel Lucent Haifa. At the end of the session you will understand the concept of executable specs,and ATDD, You will see real example of test implementation in ATDD tool (Cucumber) and will understand the steps required to make such transition with some do/not do tips in tool and process implementation (based on Alcatel case study).
You will get (printed) the suggested implementation plan and do/not do tips of ATDD automation tools implementation
Please visit wingman-sw.com if you would like a copy of the PDF or the associated paper.
Embedded systems development can benefit from Agile software development. This paper and presentation tells you about why you should care, what problems Agile is designed to solve and what agile is. This topic has evolved over the years. I started presenting it in 2004 (or maybe earlier) at the Embedded Systems Conference.
This document discusses managing agile projects using Scrum. It provides an overview of Scrum, including common roles, artifacts, and events like sprints, sprint planning, daily scrums, sprint reviews, and retrospectives. It also discusses how project management practices from PMBOK like scope, schedule, cost can be addressed in Scrum, with the product backlog, release planning, and tracking work remaining. The document aims to explain how to use Scrum for managing agile software development projects.
This document discusses improving project estimation and predicting delivery dates. It begins by noting that detailed estimation does not strongly influence lead times due to typically low flow efficiencies in systems. Lead time histograms are proposed as a better approach to predict completion dates with confidence levels, as they incorporate all system factors without personal bias. Class of service and work item characteristics can identify the most accurate histogram. Considering cost of delay functions alongside histograms helps determine when work should start to balance timely delivery and optimization of resources. The document advocates predicting customer expectations rather than effort or duration and focuses on statistical prediction over detailed planning.
This document discusses the role of a QA Engineer in JIRA. It notes that the QA Engineer works with a team of 15 people including developers, product managers, UX designers, and other QAs. It emphasizes that with Agile development, testing is now a shared responsibility of developers rather than being isolated to testers. Developers are expected to write and execute both manual and automated tests as part of development. The document outlines the development and release process at JIRA, with major releases every 2-3 months and bugfix releases every 2 weeks for the on-demand product. It stresses testing early and often through the development cycle rather than relying on testing at the end. Automated regression tests run on every code change to prevent
This talk will explain the secret of the success of the Eclipse Platform team. The Eclipse Way is an agile software development process that we started right at the beginning when we started to develop Eclipse back in 1999. It was and is used by the Eclipse Platform team and got continuously improved over time. During the session you will hear about all our practices, like milestones, early and iterative planning, continuous integration and the endgame. I will also reveal some of the history behind the Eclipse top-level project.
More details: https://confengine.com/eclipse-summit-2016/proposal/2386/the-eclipse-way
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, Jon 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, 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.
Use Combinatorial Testing for Mobile Device FragmentationJosiah Renaudin
A common problem in mobile systems testing is the number of hardware, operational, and software configurations that need to be tested. For example, the so-called Android fragmentation problem might lead a test team to test hundreds of device and software configurations, yielding thousands or even tens-of-thousands of tests. A branch of mathematics, called combinatorics, and associated tools exist that allow teams to minimize the number of test cases required, while assuring high error finding percentages. Jon Hagar defines the fragmentation problem and then examines test patterns supported by tools that can help improve testing success. Jon outlines how combinatorial test patterns can be applied to other testing situations. To solve real-world fragmentation problems, he identifies specific tools, which you can take back to your project for quick use. Reference work and data are provided to help your team justify adding combinatorial testing to your mobile test activities.
Implement Combinatorial Test Patterns for Better Mobile and IoT TestingJosiah Renaudin
A common problem in mobile and IoT systems is the large number and combinations of hardware, operational, and software configurations that need to be tested. For example, the so-called Android fragmentation problem might lead a test team to test hundreds of device and several software configurations, potentially yielding thousands or even tens of thousands of tests. Combinatorial testing, a technique involving mathematics and specific tooling, allows teams to reduce the number of test cases, while still assuring good error finding capabilities. Jon Hagar examines test combinatorial patterns supported by tools that will help you speed up testing these many configurations and use for other test tasks, too. During this session Jon will identify and demonstrate specific tools to solve real-world mobile and IoT testing problems. Take back reference materials and data to help your team justify adding combinatorial testing to its toolkit and regular testing activities.
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.
IoT Software Testing Challenges: The IoT World Is Really DifferentTechWell
The Internet of Things (IoT) is poised to become the next growth area—and biggest challenge—for software development and testing. Although many traditional test techniques and strategies remain viable, IoT testing includes working with huge amounts of data, multiple communication channels, device protocols, resource limitations (battery or memory), sensors, controllers, cloud-hardware-device integration, and security concerns. Jon Hagar says that successful IoT testers must develop new knowledge and skills and apply them based on real data and proven test design methods. Testing analytics should include raw test data, data relationships across software integration boundaries, and social media inputs—as well as a keen understanding of sociological and psychological factors. Jon shares insights into math-based testing, model-based testing, attack-based and exploratory testing for IoT applications and systems. Take back a new holistic view for your IoT testing which considers the world environment, connected systems, local systems, and the IoT device itself.
XBOSoft Mobile Security Webinar with Jon D. HagarXBOSoft
Mobile Security is a real world threat in today's technology sector, these slides explore testing attack concepts and how to prevent hacks and vulnerabilities creeping up in your mobile app development or device deployment. Jon D Hagar goes through methodologies all software developers and software testers need to follow to ensure mobile security risks are minimizes and controlled.
Exploratory Mobile Testing Webinar_XBOSoft_jean_annharrisonXBOSoft
To Automate or not to Automate your Mobile Testing.
In mobile testing just poking at the GUI will leave bugs hiding. So different tests and a variety of testers are needed. Context is also important; there is no one test set or test approach that will work all the time.
JeanAnn Harrison has years of experience with mobile testing and is a well-known figure in the QA and software testing community. She regularly speaks at conferences and publishes in software testing magazines.
In these slides JeanAnn discusses mobile testing strategies that deliver the right results.
You will learn:
- Types of Mobile Testing
- When and when not to automate your mobile testing
- Mobile exploratory testing strategies and guidelines
- Lesson learned
IoT Software Testing Challenges: The IoT World Is Really DifferentTechWell
With billions of devices containing new software connected to the Internet, the Internet of Things (IoT) is poised to become the next growth area for software development and testing. Although many traditional test techniques and strategies remain viable, challenges in IoT testing include huge amounts of data, multiple communication channels, device protocols, resource limitations (battery or memory), addressing sensors and controllers, cloud-hardware-device integration, and security concerns. Jon Hagar says that for IoT testers to be successful, they must develop new knowledge and skills, and apply them based on real data and proven test design methods. Testing analytics should include raw test data, data relationships across software integration boundaries, and social media inputs, as well as a keen understanding of sociological and psychological factors. Jon shares insights into math-based testing, model-based testing, attack-based exploratory testing, and appropriate types of standards as basics of IoT testing. Take back a new holistic view for your IoT testing which considers the world environment, connected systems, local systems, and the IoT device itself.
Expert tester and speaker JeanAnn Harrison reveals critical mobile tests that can be used on many mobile devices, even proprietary. Exercises and ideas for testing that you can use and build on. Sponsored by XBOSoft.
Exploratory testing and the mobile tester : A presentation by Jon HagarGallop Solutions
The document discusses various testing attacks that can be performed on mobile and embedded systems. It begins by providing context on mobile testing and defines key terms. It then outlines 33 different attacks that target common issues like static code analysis bugs, data computation errors, hardware/software interface problems, security vulnerabilities, and usability defects. Several attacks are described in more detail, including developer attacks, basic tester attacks, and dangerous security attacks. The document aims to educate testers on effective exploratory testing techniques for breaking mobile and IoT devices.
Top IOT Testing Challenges Webinar with Jon HagarXBOSoft
Our special guest embedded and IOT testing expert Jon Hagar shares his thoughts on mobile testing, embedded testing, and IOT testing and how they intersect to form the perfect storm in the coming 4th Industrial Revolution where all businesses become software businesses and security/privacy reach new heights of concern.
Some of the most famous information breaches over the past few years have been a result of entry through embedded and IoT system environments. Often these breaches are a result of unexpected system architecture and service connectivity on the network that allows the hacker to enter through an embedded device and make their way to the financial or corporate servers. Experts in embedded security discuss key security issues for embedded systems and how to address them.
Yow connected developing secure i os applicationsmgianarakis
This document provides an overview of how to design secure iOS applications. It discusses the iOS application attack surface and common security issues, including binary and runtime security issues. It outlines secure iOS application design principles such as not trusting the client/runtime environment and not storing sensitive data on devices. It then discusses specific techniques for implementing binary and runtime security, such as adding anti-debugging controls, jailbreak detection, and address space validation. It also covers securing memory and the importance of transport layer security.
Softwere Testing Aplication Specific Techniquesmaharajdey
This document discusses various types of software testing techniques including:
1. Unit testing focuses on testing individual units of code to check if they are fit for use.
2. Integration testing tests software modules when integrated together to expose defects.
3. Acceptance testing determines if the software meets acceptance criteria and is performed by end users before moving to production.
It also provides examples of why software testing is important to avoid costly failures and ensure quality, security, and customer satisfaction. A variety of testing types are described from functional to load testing.
Mobile App Test Attacks to Efficiently Explore SoftwareTEST Huddle
In the tradition of James Whittaker’s book series How to Break … Software, Jon Hagar applies the testing “attack” concept to the domain of mobile app software. Jon defines the sub-domain of mobile software and examines industry product failure caused by defects in that software. Next, Jon summarizes a set of attacks against mobile software based on these common modes of failure that testers can direct against their own app software to quickly find bugs. Specific attack methods identified include developer based cases, computation and control structures for batteries and sensor hubs, hardware-software interfaces, and communications. This session is based on the book: “Software Test Attacks to Break Mobile and Embedded Devices” CRC press, 2013
Key Takeaways:
- Breaking Mobile App Software to find bugs
- Embedded risk-based exploratory testing concepts
- Attack based testing specific to mobile devices
Mobile App Testing: The Good, the Bad, and the UglyTechWell
The document discusses mobile application testing and provides examples of issues that can arise. It describes current problems like management not allowing enough testing time or prioritizing speed over quality. This can lead to bugs being missed and poor user experiences. The document also introduces taxonomies to help categorize different types of bugs, like those related to timing, to aid in more effective testing. Overall, it advocates for improved mobile app testing practices to avoid common pitfalls and ensure high quality user experiences.
Enhancing Mobile Apps Quality-Manual Testing RevisitedMindfire Solutions
The document discusses enhancing mobile app quality through manual testing. It covers topics like the versatile nature of mobile apps, how to test on actual devices, common bug types, and case studies. Testing on different devices and configurations is important due to variations in screen size, inputs, and other factors. Usability testing is also paramount to ensure good user experiences and high app ratings.
How to Test Security and Vulnerability of Your Android and iOS AppsBitbar
Watch a live presentation at http://offer.bitbar.com/how-to-test-security-and-vulnerability-of-your-android-and-ios-apps
Majority of today’s mobile apps consist of third-party code/libraries. This is a prudent and well-accepted development practice that offloads the task of developing code for non-core functions of your mobile app – or game. Identifying third-party code, its vulnerabilities and its license restrictions, is highly critical in order to understand your security exposure and your liability.
Stay tuned and join our upcoming webinars at http://bitbar.com/testing/webinars/
Lec 1 Introduction to Software Engg.pptxAbdullah Khan
The document contains questions related to software engineering. It begins by defining software and a computer program. It then discusses why software is important, common problems in software development, and examples of severe consequences of software failures. The document asks about software engineering, the differences between computer science and software engineering, and challenges in the field. It also addresses major activities in software development and sources of inherent complexity. Overall, the document poses questions to introduce various foundational concepts in software engineering.
What Aircrews Can Teach Software Testing Teams - XBOSoft Webinar w/Peter VarholXBOSoft
Aircrew resource management principles enable any team member to question decisions and directions that seem to be wrong. Testing teams, whose members have diverse experience and expertise that give them different perspectives, need to embrace these principles to make the right decisions.
United Flight 232 should have crashed with 296 lives lost. In contrast, Asiana Flight 214 should not have crashed at all. The critical difference between the two was the interactions of their respective aircrews. Aircrew resource management refers to how cockpit crew members work together to make flights as safe and efficient as possible. These principles have been applied to other professional fields, and should be a central practice of every testing team.
Testing teams require expertise in all aspects of software design, development, test, delivery, and operations. There can be no “command pilot” whose expertise over all aspects of testing is greater than the combined expertise and experience of others. And while the leader of the team is the final authority, he or she must listen to and consider team members whose knowledge and experience can make the difference between success and failure.
This presentation discusses how aircrew resource management has evolved to focus on expertise, collaboration, and decision-making in the cockpit. It applies these lessons to testing teams, where complementary expertise is necessary to deliver high quality and working applications, updated continuously. It highlights the characteristics of successful aircrew teams and how those characteristics apply to building and delivering great software.
Attendees will learn:
1. What testing teams can learn from successful teams in other fields.
2. How testing teams must work collaboratively, especially in crises and under pressure.
3. How blind deference to authority and automation can be detrimental to a testing team.
Challenges in Using Big Data for Software QAXBOSoft
In this webinar, our guest speakers, Jennifer Bonine and Rick Faulise from TapQA shared their thoughts on using #BigData for #softwaretesting and #SoftwareQA. What #metrics to use and what not to use, and how to combine them together to get some real meaning and insights versus just data.
Mobile Testing Challenges and Solutions XBOSoft WebinarXBOSoft
In this webinar, XBOSoft's VP of Engineering discusses some of the challenges that he and his team have faced in the areas of mobile test automation and mobile usability testing. He'll discuss how to gain the best platform coverage, when to use automation, when not to, and when to use shared cloud services versus emulators and real devices.
Heidi Araya - XBOSoft Webinar Guest Speaker - Working with Remote Agile TeamsXBOSoft
In this XBOSoft webinar, we were glad to have Heidi Araya, a seasoned agile coach, discuss the reality or non-reality of agile teams being colocated. She covered many tips and techniques for working remotely in an agile environment.
XBOSoft webinar - How Did I Miss That Bug - Cognitive Biases in Software TestingXBOSoft
The document discusses cognitive biases that can cause testers to miss bugs. It explains that software testing involves both objective comparisons to specifications as well as subjective judgments, and that missed bugs result from errors in judgment influenced by cognitive biases. Some biases discussed include representative bias, confirmation bias, and anchoring effect. The document advocates managing cognitive biases through techniques like exploratory testing, which focuses more on intuition and learning than requirements coverage. It suggests testers, managers, and the QA profession shift focus from finding bugs to providing information.
PSQT Keynote: Quality Challenges in the Internet of Things EraXBOSoft
The Internet of Things is made up of three core elements: things, communications and computing. Things are devices connected to the Internet such as a watch, car or appliances in your home. For IoT to work, these things need to be connected, communicating statuses and other information with each other in real time. And with this information, the last element of IoT is computing and storage. What will all this information be used for? What actions can or should be taken? How and where will the information be stored, on a server, on a mobile phone? And who will it be accessible by?
IoT offers both efficiency and automation to daily life, and with an estimated 26 billion connected devices by 2020, there’s bound to be issues with security, reliability and connectivity within that enormous, intricate network. This makes the role of QA critical.
For example: security. Will someone be able to hack into my home network and then into my wearable device and steal my medical information? Then there’s data storage, the actual efficiency of the device and user interactions to account for. IoT is still growing so quickly that QA testers must be able to keep up with the increasing complexity of it as it continues to expand.
Simply making sure that the device and its software works correctly in a controlled environment in isolation is not acceptable. Yet, how can you test all the scenarios? Scenarios include not only the multitude of devices that can connect together in a combination of ecosystems, but also, the data they produce. How we develop test data sets that accurately represent the real world must also be considered, as well as how we can make sure it is secure with such a multitude of sensors collecting data. Lastly, IoT is not about devices. We still have to make sure the user has an integrated experience across devices and software. Hence, usability in IoT could be the most overlooked game breaker for IoT. In this session, find out the latest technologies, thought patterns, techniques and methods to move beyond old school QA (desktops, web and mobile) where devices work mostly in isolation.
7 Habits of Highly Effective Agile Testing - Test IstanbulXBOSoft
This document summarizes a presentation on applying Stephen Covey's 7 Habits of Highly Effective People to agile testing. It discusses the original 7 habits and how they can help teams succeed with agile. Maintaining an improvement mindset, treating users as the top priority, and building trust are some key ways the habits were applied. Regular retrospectives and a focus on efficiency and effectiveness were emphasized as important agile practices.
Managing Agile Software Projects With Risk and UncertaintyXBOSoft
In chasing velocity, we often ignore or don’t understand the uncertainties and associated risks in our processes and their results. Agile is designed to handle uncertainty in requirements as new features are requested and priorities shift. But shouldn’t we also be thinking about and mitigating the uncertainties that are unique or even introduced by using agile? Phil Lew suggests that our problem is that we sometimes carry assumptions which either cause us to spend too much effort on things we can’t control or give us unfounded comfort and reassurance. If we can’t understand the uncertainties and risks, how can we have confidence in our software as systems become more complex? Phil overlays classic risk management techniques with an agile process to identify and address the uncertainties that matter—and those that don’t. Then Phil outlines methods that you can use to address these risks while maintaining rhythm in your agile software processes. Come and learn about risks you never thought of and see how you can manage or avoid them.
Testing in Agile with Coaching Agile Journeys and XBOSoftXBOSoft
Philip Lew joins Coaching Agile Journeys to discuss Testing in Agile. In this webinar, Phil covers the agile process and how agile testing not only fits in, but how software testers can move up and downstream to improve quality throughout.
Using JMeter and Google Analytics for Software Performance TestingXBOSoft
Ed Curran, VP of Engineering at XBOSoft, shares some of his hands on experience in working with JMeter for load and performance testing. In the webinar, he provided explanations of different types of performance testing and how you can use Google Analytics to understand what users are really doing on your web apps and then how to leverage JMeter and analyze the results to improve your app's performance.
Storytelling: Discover the Big Picture for Agile Efforts Webinar - Tom Cagley...XBOSoft
This document summarizes a webinar about using storytelling for agile efforts. It introduces the speakers and provides an overview of how storytelling has been used historically. Additionally, it discusses different types of story patterns that can be used, elements of business stories, facilitating storytelling sessions, and using a process of generating a "big picture" story. Examples of techniques like the Lean Change Canvas and a six-word story exercise are also presented.
ASTQB w/ XBOSoft CEO Phil Lew: Agile and Waterfall - What Do Testers Do Diffe...XBOSoft
ASTQB invited XBOSoft CEO Phil Lew to present a webinar on the differences between Agile testing and other testing methods.
Visit xbosoft.com for more Agile testing resources.
When Agile is a Quality Game Changer Webinar - Michael Mah, Philip LewXBOSoft
Accelerate your Agile success with in-depth research and smarter decisions. Michael Mah of QSM Associates shows you what it takes to find and utilize patterns of successful Agile development in this quarterly XBOSoft webinar.
QAI QUEST 2016 Webinar Series: Pairwise Testing w/ Philip LewXBOSoft
In anticipation of the QAI QUEST 2016 Conference & Expo in Chicago, Illinois, XBOSoft’s CEO Philip Lew presented a live webinar on Pairwise Testing. Find out what pairwise testing is, the advantages and disadvantages of implementing this method, and when to use it and how.
For Philip Lew's demonstration of pairwise testing, view the recorded webinar at https://vimeo.com/155889518
FluentConf 2016: Avoiding Critical UX Mistakes with Philip LewXBOSoft
Here are the slides from XBOSoft CEO Philip Lew's presentation at the 2016 Fluent Conference in San Francisco (March 7-10, 2016). Lew covered how to avoid critical UX mistakes and how to keep your users coming back with more than just "pretty colors and buttons."
Are You Making These 7 'Testing Metric' Mistakes? Webinar - Mark Bentsen, Phi...XBOSoft
Find out if you're making these common testing metric mistakes and what to do if you are. In this hour-long XBOSoft webinar, ARGO Data's Quality Assurance Manager will teach you how to improve your metrics and build better software testing and QA teams.
Challenges & Successes of Agile Implementation Webinar with BlackLine - XBOSoftXBOSoft
In this hour-long webinar, BlackLine's Director of Software Development Greg Burns and Scrum Master and Agile Coach Ron Ben Yosef discuss the company's agile conversion experience -- the challenges, successes, and benefits gained from implementation.
Agile Product and User-Centered Design Methodologies Webinar - XBOSoftXBOSoft
This document summarizes an Agile product and user-centered design webinar hosted by XBOSoft. The webinar discusses integrating user research methods like usability testing, personas and prototypes into Agile software development processes. It emphasizes establishing a culture where employees are empowered to explore user needs and provide early, continuous feedback to improve products. The webinar aims to help organizations make better products faster by putting users first.
Software quality improvement expert Jan Princen and XBOSoft CEO Philip Lew discuss the use of Predictive Analytics to prevent software defects in this XBOSoft webinar on Defect Prevention.
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.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
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
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
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!
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
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.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
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
2. XBOSoft info
• Founded in 2006
• Dedicated to software quality
• Software QA consulting
• Software testing services
• Offices in San Francisco, Beijing, Oslo and
Amsterdam
4. Housekeeping
• Everyone except the speakers is muted
• Questions via the gotowebinar control on the right side of your
screen
• Questions can be asked throughout the webinar, we’ll try to fit
them in when appropriate
• General Q & A at the end of the webinar
• You will receive info on recording after the webinar
5. About Jon Hagar
Jon….
• has over 30 years in software testing/verification and
validation
• is the owner of Grand Software Testing, a company
specializing in software test consulting and training for
mobile and embedded systems.
• author of “Software Test Attacks to Break Mobile and
Emedded Devices”
6. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 6
SOFTWARE TESTING CONCEPTS
FOR MOBILE AND EMBEDDED
DEVICES
Jon Hagar
embedded@ecentral.com
jon.d.hagar@gmail.com
breakingembeddedsoftware.wordpress.com
7. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 7How to Attack Embedded Software 7
AGENDA FOR TODAY
• Introductions
• Definitions
• Risk based concepts
• Exploratory approaches
• Attacking the scenario(s)
• Mobile and embedded tester skills
• Wrap up and references
8. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 8How to Attack Embedded Software 8
MOBILE, SMART, AND HANDHELD
• As the names imply, these are devices—small, held in the hand, often
connected to communication networks, including
• Cell and smart phones – apps
• Tablets
• Medical devices
• Typically have:
• Many of the problems of classic “embedded” systems
• The power of PCs/IT
• More user interface (UI) than classic embedded systems
• Fast updates
• Are getting more power, memory, and features (software e.g., apps)
• The “hot” area of computers/software
• Testing rules are “evolving”
9. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 9How to Attack Embedded Software 9
CLOSE COUSINS:
Embedded Software Systems . . .
• Interacts with unique hardware/systems to solve specialized problems in
the “real world”
• IT software runs with largely “generic” hardware
• Users are barely aware the device uses or has software
• Usually have significant hardware interface issues and concerns
• Initialization, noise, power up/down, timers, sensors, etc.
• Often are resource constrained
• RAM, ROM, stack, power, speed, time, etc.
• Typically has a restricted or no Human User/Computer Interface (HCI) but
is evolving rapidly
• Often no way (or only a risky way) to update and/or change the software
• Involves risks, hazards, safety, and/or some specialized domain knowledge
and logic/algorithms usually controlling hardware
10. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 10How to Attack Embedded Software 10
WHAT DO THESE LOOK LIKE?
Examples
– Avionics systems: planes, cars, rockets, military,…..
– Telecom: switch, routers, phones, cell devices,….
– Transportation: traffic control, railroad, trucking, ….
– Industrial control: lighting, machines, HVAC, nuclear/power,…
– Medical: pacemaker, dispensers, …….
– Home and office systems: control, entertainment (TV box), …
– And the list goes on
• Now starting to include PDA’s and other items that “blur” the
lines
11. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 11How to Attack Embedded Software 11
TYPES OF MOBILE-
EMBEDDED APPS
• Native Applications
• Local to device
• Hybrid Applications
• Local to device but
interacts w/internet
• Web Applications
• Not local to device
All interactions on
internet
And JeanAnn Haarrison
12. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 12How to Attack Embedded Software 12
THE “WORLD” OF MOBILE-
SMART/EMBEDDED SOFTWARE
• Inputs and outputs involve hardware, software, and humans
• Time dependent
• NOTE: most software has “time” (performance) issues but here things are
often “hard real time”
• In Mobile/Embedded real-time may be a requirement
Software
Stimulus-Inputs Response-Outputs
Expected
Unexpected
Wanted
UnwantedHardware
13. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 13How to Attack Embedded Software 13
MOBILE AND EMBEDDED SOFTWARE TESTING:
THE SAME BUT DIFFERENT
• Same patterns in programming errors =>
same test patterns to be applied
• But there are Differences
• The development lifecycle
• Mobile and embedded error patterns
• “Embedded” unique sensor (input and output)
• Mobility
• Network connections
• Resources
14. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 14How to Attack Embedded Software 14
Hardware Change
Hardware New Product
EXAMPLE HIGH LEVEL MOBILE-EMBEDDED
LIFECYCLE DIFFERENCE
System Creation
Hardware Build
Software Build
Software Build
Software Build
Software Build
Hw
Issue
Feature
Results: Software is “late”
Software Build
Months, Days, Hours
15. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 15How to Attack Embedded Software 15
THE ERROR (BUG) PATTERN:
SIMILAR AND DIFFERENT
• Handheld/Embedded software has
similar defects to other software
• Requirements & Design
• Logic & Math
• Control Flow
• Data
• Initialization & Mode changes
• Interfaces
• Security
• Gaming
• etc. . .
Mobile/Embedded additions
• Software and hardware
development cycles done in
parallel, where aspects of the
hardware may be unknown to the
software development effort
• Limited resources
• Control/use of unique hardware
(sensors)
• Hardware problems which are often
fixed with software late in the
project
• (a big one) Very tight real-time
(often in milli- or micro-second
ranges) or load performance issues
16. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 16How to Attack Embedded Software 16
MORE SAMPLE MOBILE-EMBEDDED PRODUCT
ERRORS TESTERS SHOULD CONSIDER
• Mobility -
• Environment and device susceptible to outside influence: noise, weather, heat, cold,
• Network connect: wifi, data, changing signal, etc
• Battery factors: Heat, charge level, charge duration, device conflicts
• Output —outputs to devices and electronics that are susceptible to noise
influences, calibrations, changes to hardware, and time
• Inputs – Sensors, speed, timing, and interrupts all can impact
devices/software
• Complexity—the size of the system or some aspect of the system makes
missed bugs likely
• Device Resources -
• Screen size
• Memory
• CPU speed
17. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 17How to Attack Embedded Software 17
THUS TESTERS SHOULD THINK: RISKS
• You cannot test everything
• Risk-based testing helps bound the test scope problem
• Testing is about providing information and understanding
• Test exploration gets you started with whatever you have (or
don’t have)
18. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 18How to Attack Embedded Software 18
IN MOBILE AND EMBEDDED:
EXPLORATORY TESTING
• Rapid feedback
• Learning
• Upfront rapid
learning
• Attacking
• Address risk
• Independent assessment
• Target a defect
• Prototyping
• Need information
• Test beyond the
requirements
Yes, we must test requirements
(necessary, but not sufficient)
So include exploratory risk-based testing:
19. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 19How to Attack Embedded Software 19
MUCH INFORMATION EXISTS ON EXPLORATORY
RISK-BASED TESTING
• Exploratory Testing: Based in the scientific method, where we
plan-design, execute, learn, and change the test effort with
limited “scripting”
• Check out works by:
• Kaner
• Bach
• Whittaker
• ISO 29119
• I like to recommend and do exploratory attack-based testing
20. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 20How to Attack Embedded Software 20
WHY ATTACK?
• Attacking your software is in part, the process of attempting to
demonstrate a system (hardware, firmware, software and operations)
does not meet requirements, functional and non-functional
objectives.
• Mobile/embedded software testing must include "the system"
(hardware, software, operations, users)
• Attack common modes of failure, especially where the application is
engaged and visible by the user.
Attack testing with approaches to include:
Tools Levels
Patterns Techniques
21. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 21How to Attack Embedded Software 21
SO, WHAT IS AN ATTACK?
• Based on a common mode of failure seen over and over
• Maybe seen as a negative, when it is really a positive
• Goes after the “bugs” that may be in the software
• Uses one or more classic test techniques and concepts
• A Pattern (more than a process) which must be modified for
the context at hand to do the testing
• Many testers learn these for a domain after years and form
a mental “pattern” model (most good testers attack)
22. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 22How to Attack Embedded Software 22
KINDS OF ATTACKS
• Whittaker offers a good starting point for software
attacks in general that can be applied to embedded:
• User Interface Attacks
• Data and Computation
• File System Interface
• Software/OS Interface
• Whittaker’s “How to Break Software” lists 23 attacks
• “Software Test Attacks to Break Mobile and Embedded
Devices” lists 33 attacks and 8 sub attacks
23. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 23How to Attack Embedded Software 23
MOBILE AND EMBEDDED ATTACK
CLASSIFICATION
• Developer Attacks (unit/code testing)
• Control System Attacks
• Hardware-Software Attacks
• Mobile and Embedded Software Domain Attacks
• Time Attacks (Performance)
• Human User Interface Attacks
• Smart and/or Mobile Phone Functional App Attacks
• Mobile/Embedded Security Attacks
• Generic Attacks
• Functional, mind mapping, and combinatorial tests
24. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 24
A DETAILED LIST OF ATTACKS
• Attack 1: Static Code Analysis
• Attack 2: Finding White–Box Data Computation Bugs
• Attack 3: White–Box Structural Logic Flow Coverage
• Attack 4: Finding Hardware–System Unhandled Uses in Software
• Attack 5: Hw-Sw and Sw-Hw signal Interface Bugs
• Attack 6: Long Duration Control Attack Runs
• Attack 7: Breaking Software Logic and/or Control Laws
• Attack 8: Forcing the Unusual Bug Cases
• Attack 9 Breaking Software with Hardware and System Operations
• 9.1 Sub–Attack: Breaking Battery Power
• Attack 10: Finding Bugs in Hardware–Software Communications
• Attack 11: Breaking Software Error Recovery
• Attack 12: Interface and Integration Testing
• 12.1 Sub–Attack: Configuration Integration Evaluation
• Attack 13: Finding Problems in Software–System Fault Tolerance
• Attack 14: Breaking Digital Software Communications
• Attack 15: Finding Bugs in the Data
• Attack 16: Bugs in System–Software Computation
• Attack 17: Using Simulation and Stimulation to Drive Software Attacks
• Attack 18: Bugs in Timing Interrupts and Priority Inversion
• Attack 19: Finding Time Related Bugs
• Attack 20: Time Related Scenarios, Stories and Tours
• Attack 21: Performance Testing Introduction
• Attack 22: Finding Supporting (User) Documentation Problems
• Sub–Attack 22.1: Confirming Install–ability
• Attack 23: Finding Missing or Wrong Alarms
• Attack 24: Finding Bugs in Help Files
• Attack 25: Finding Bugs in Apps
• Attack 26: Testing Mobile and Embedded Games
• Attack 27: Attacking App–Cloud Dependencies
• Attack 28 Penetration Attack Test
• Attack 28.1 Penetration Sub–Attacks: Authentication — Password Attack
• Attack 28.2 Sub–Attack Fuzz Test
• Attack 29: Information Theft—Stealing Device Data
• Attack 29.1 Sub Attack –Identity Social Engineering
• Attack 30: Spoofing Attacks
• Attack 30.1 Location and/or User Profile Spoof Sub–Attack
• Attack 30.2 GPS Spoof Sub–Attack
• Attack 31: Attacking Viruses on the Run in Factories or PLCs
• Attack 32: Using Combinatorial Tests
• Attack 33: Attacking Functional Bugs
25. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 25How to Attack Embedded Software 25
AN EXAMPLE DETAILED TAXONOMY:
A2D AND D2A BUG POSSIBILITIES
Type Situation Impact Notes
A2D A2D representation information is lost
because measurement is not precise
Software computation
is based on incorrect
data
Number of bits used to store the analog converted
data is not large enough or sampling rate to get
bits is not correct.
A2D A2D information is contaminated with noise Software computation
use noise when it
should not
The noise term may not be known, accounted for,
or misrepresented.
A2D A2D information is calculated correctly Computation has
unknown error
Sources of error can come from: calibrations used
on variables, variables lacking initialization, or
calculations are not done with enough accuracy
(single versus double floating point
D2A D2A conversion losses “least significant
bits” (LSB) in conversions, but bits are, in
fact, important because computer word
sizes are too small
Output to analog
device is wrong
Number of bits stored from the digital world to the
analog world do not have enough precision, so
analog data is incorrect.
D2A D2A information does not account for noise
of the real world
Software computation
does not include a
factor for noise
The analog values are not correct given the noise
of the real world (output data may be lost in the
noise).
D2A D2A information is calculated correctly
because of internal factors
Computation has
unknown error
Sources of error can come from: calibrations used
on variables, variables lacking initialization, or
calculations are not done with enough accuracy
(single versus double floating point
26. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 26How to Attack Embedded Software 26
FINALLY, IN ADDITION TO TESTER SKILLS:
SKILL FOR THE MOBILE/EMBEDDED TESTER
• Tester skills: planning, design, execution, reporting, exploration, techniques,
tools…………………….
• Exposure or knowledge about products from the domain in which you are
testing: aerospace, medical, automobile manufacturing, smart apps,
airplanes, factory systems, robotics, regulated environments, etc.
• Knowledge of hard sciences: math, physics, electronics, hardware,
engineering, etc. for logical thought processes
• Knowledge of Soft sciences: psychology, philosophy, sociology, human
factors (human machine interface), gaming, arts… for creative & conceptual
thought processes
• Passion – follow your bliss
27. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 27How to Attack Embedded Software 27
FOR THE SOFTWARE YOU TEST
ASK YOURSELF
• Do you know how it fails?
• Do you test for success or failure?
• Both?
• Where can you improve?
28. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 28How to Attack Embedded Software 28
SUMMARY: THANK YOU (IDEAS USED FROM)
• James Whittaker (attacks)
• Elisabeth Hendrickson (simulations)
• Lee Copeland (techniques)
• Brian Merrick (testing)
• James Bach (exploratory & tours)
• Cem Kaner (test thinking)
• JeanAnn Harrison
• Many teachers
• Generations past and future
• Books, references, etc.
29. Jon Hagar Copy right 2013 Software Test Attacks to Break Mobile and Embedded Devices 29How to Attack Embedded Software 29
BOOK LIST (MY FAVORITES)
• “Software Test Attacks to Break Mobile and Embedded Devices”
– Jon Hagar,
• “How to Break Software” James Whittaker, 2003
• And his other “How To Break…” books
• “Testing Embedded Software” Broeckman and Notenboom, 2003
• “A Practitioner’s Guide to Software Test Design” Copeland, 2004
• “A Practitioner’s Handbook for Real-Time Analysis” Klein et. al., 1993
• “Computer Related Risks”, Neumann, 1995
• “Safeware: System Safety and Computers”, Leveson, 1995
• Honorable mentions:
• “Embedded System and Software Validation” Roychoudhury, 2009
• “Systems Testing with an Attitude” Petschenik 2005
• “Software System Testing and Quality Assurance” Beizer, 1987
• “Testing Computer Software” Kaner et. al., 1988
• “Systematic Software Testing” Craig & Jaskiel, 2001
• “Managing the Testing Process” Black, 2002