Does test automation add value? Good automation does, but poor automation reduces value, delaying decisions, and increasing the likelihood of errors of judgement.
Automation tools are written and serviced by engineers, but people who use automation might not always be technical. To understand what they need, we need to understand them. User eXperience (UX) methods will help.
Test automation requires consideration of the UX for the tool and the tests, supporting improved decision making, and increasing automation’s value.
We need to be open by default – use the strength of the community to solve the complex problems we face of the exponential digital growth and beyond.
Outside your team, your organization and the circle around that.
And besides the users which always have to be involved.
Ux for test tools tx-75minskey v10 16-9 slideshare nokia test dive 2017Isabel Evans
“TX to prevent “shelfware”: Understanding the tester’s experience of automation and tools” (75 mins)
There is a taken-for-granted assumption in the testing industry that many software testing tools become “shelfware” (that is, they are purchased but not used) because they are hard to implement and use. If there is a problem with shelfware, this raises questions, for example: Is this because the tools are flawed, and don’t give the testers the support and information they need? Or is it because the testers need to become more technical and “step up” to the requirements of the tools?
These questions matter because testing, and the automation of test activities, is time consuming, difficult to do, and expensive, but heavily relied on by teams and organisations. Maybe, if the User eXpereince (UX) for tools was improved this could help with the implementation and usage of the tools. Perhaps we should consider not just the functional and technical aspects of the product but also emotional responses including trust and credibility, making a product meaningful and pleasant to use, and measures of the efficiency and effectiveness with which people can carry out their tasks.
Good automation tools should help us make good decisions about the SUT and maximise the value of the limited time we have, to deliver software products to market. Poor automation tools may delay decision making, increase the likelihood of errors of judgement, and frustrate both engineers and managers.
Once activities have been automated and industrialised, people are still required to operate the automation, or even over-ride it if it malfunctions. Some evidence (for example quoted in “The Glass Cage” by Nicholas Carr) suggests that people may become over-reliant and over-trusting of automation and not notice when it goes wrong. What then is the best UX for test tools? One that provides as easy an experience for the tester as possible, or one that maximises their decision making and alertness? And, can both those qualities be delivered in one interface?
The talk draws on Isabel’s practical experience in industry, as well as research and study with Julian Harty, Stuart Reid, Dorothy Graham, Nadine Raes and others. Isabel is embarking on a PhD study to research this matter in more depth. Isabel hopes to provoke feedback and discussion during the presentation.
Key points
• Issues with the UX of automation solutions may affect the success of automation projects;
• Understanding the needs of the testers and managers using the automation may reduce those issues;
• Adopting human-centric design practices can help you to design, build or select automation that supports testers.
Agile india 1 day workshop quality in use user experience v5 for sharingIsabel Evans
The document discusses quality in use and user experience. It introduces key concepts like quality, user experience, quality in use, and internal quality. It explains that quality in use looks at how a product influences users' effectiveness, productivity, safety and satisfaction. The document also discusses applying user-centered design principles like creating personas, contexts of use, and quality attributes to design products that meet users' needs.
Quality in use 45 min presentation 16 9 slideshare nokia test dive 2017Isabel Evans
In today’s business environment, the user experience and the commercial imperatives have become overwhelmingly important. As testers, it is vital that we understand quality in use and the user experience, in order that we focus our tests correctly.
"Quality in use" measures human, business, and societal impacts of products (usability, accessibility, flexibility, commercial, safety). This builds to a User Experience (UX) and are underpinned by technical and engineering qualities. For the people selling, supporting, or using the products, this is the beating heart of the customer experience. Without these "big picture" attributes, delivered software will not be acceptable, may result in reduced profits, and may not be legal. In the tutorial, Isabel will use examples from real projects to discuss how to design tests derived from the user personas, contexts of use, and acceptance criteria.
The document discusses the importance of developer experience (DX) and how to improve it. DX refers to the interactions and events between developers and tools/APIs, both positive and negative. Good DX matters because it leads to innovative usage and evangelism, while poor DX results in minimal usage and high turnover. The document provides tips for DX providers to consider users at each stage, from signing up and getting started to ongoing use and support. It emphasizes the importance of documentation, API design, and issue tracking/support to ensure developers enjoy and want to continue using a tool.
User experience (UX) encompasses all aspects of a user's interaction with a company, its services, and products. UX involves a person's behaviors, attitudes, and emotions when using a product or service. It also includes their perceptions of aspects like usability, ease of use, and efficiency. UX is dynamic as it changes over time with usage circumstances and system changes. To design for positive UX, companies use user-centered design approaches like personas, user stories, prototypes, and usability testing to understand users and optimize the product around their needs and goals. Various tools and methods are used to measure and improve UX.
This document discusses various aspects of user experience (UX) design including visual design, system design, branding, customer service, packaging, product unboxing, and how human emotion determines UX. It provides techniques for UX design such as using humor, recognizing patterns, engagement, communication, and building relationships. It also covers ergonomics guidelines for UX like consistency, simplicity, feedback, attention, and modality. The document examines the influence of design on UX and discusses simplifying interactions through minimalism and asking questions about users. Finally, it discusses gamifying interactions and experience to influence human habits.
This document discusses various aspects of user experience (UX) design including visual design, system design, branding, customer service, packaging, product unboxing, and how human emotion determines UX. It provides techniques for UX design such as using humor, recognizing patterns, engagement, communication, and building relationships. It also covers ergonomics guidelines for UX like consistency, simplicity, feedback, attention, and modality. Finally, it discusses how design influences UX and techniques like minimalism, simplifying interactions by asking who, what, why, and when questions, and gamifying interactions.
We need to be open by default – use the strength of the community to solve the complex problems we face of the exponential digital growth and beyond.
Outside your team, your organization and the circle around that.
And besides the users which always have to be involved.
Ux for test tools tx-75minskey v10 16-9 slideshare nokia test dive 2017Isabel Evans
“TX to prevent “shelfware”: Understanding the tester’s experience of automation and tools” (75 mins)
There is a taken-for-granted assumption in the testing industry that many software testing tools become “shelfware” (that is, they are purchased but not used) because they are hard to implement and use. If there is a problem with shelfware, this raises questions, for example: Is this because the tools are flawed, and don’t give the testers the support and information they need? Or is it because the testers need to become more technical and “step up” to the requirements of the tools?
These questions matter because testing, and the automation of test activities, is time consuming, difficult to do, and expensive, but heavily relied on by teams and organisations. Maybe, if the User eXpereince (UX) for tools was improved this could help with the implementation and usage of the tools. Perhaps we should consider not just the functional and technical aspects of the product but also emotional responses including trust and credibility, making a product meaningful and pleasant to use, and measures of the efficiency and effectiveness with which people can carry out their tasks.
Good automation tools should help us make good decisions about the SUT and maximise the value of the limited time we have, to deliver software products to market. Poor automation tools may delay decision making, increase the likelihood of errors of judgement, and frustrate both engineers and managers.
Once activities have been automated and industrialised, people are still required to operate the automation, or even over-ride it if it malfunctions. Some evidence (for example quoted in “The Glass Cage” by Nicholas Carr) suggests that people may become over-reliant and over-trusting of automation and not notice when it goes wrong. What then is the best UX for test tools? One that provides as easy an experience for the tester as possible, or one that maximises their decision making and alertness? And, can both those qualities be delivered in one interface?
The talk draws on Isabel’s practical experience in industry, as well as research and study with Julian Harty, Stuart Reid, Dorothy Graham, Nadine Raes and others. Isabel is embarking on a PhD study to research this matter in more depth. Isabel hopes to provoke feedback and discussion during the presentation.
Key points
• Issues with the UX of automation solutions may affect the success of automation projects;
• Understanding the needs of the testers and managers using the automation may reduce those issues;
• Adopting human-centric design practices can help you to design, build or select automation that supports testers.
Agile india 1 day workshop quality in use user experience v5 for sharingIsabel Evans
The document discusses quality in use and user experience. It introduces key concepts like quality, user experience, quality in use, and internal quality. It explains that quality in use looks at how a product influences users' effectiveness, productivity, safety and satisfaction. The document also discusses applying user-centered design principles like creating personas, contexts of use, and quality attributes to design products that meet users' needs.
Quality in use 45 min presentation 16 9 slideshare nokia test dive 2017Isabel Evans
In today’s business environment, the user experience and the commercial imperatives have become overwhelmingly important. As testers, it is vital that we understand quality in use and the user experience, in order that we focus our tests correctly.
"Quality in use" measures human, business, and societal impacts of products (usability, accessibility, flexibility, commercial, safety). This builds to a User Experience (UX) and are underpinned by technical and engineering qualities. For the people selling, supporting, or using the products, this is the beating heart of the customer experience. Without these "big picture" attributes, delivered software will not be acceptable, may result in reduced profits, and may not be legal. In the tutorial, Isabel will use examples from real projects to discuss how to design tests derived from the user personas, contexts of use, and acceptance criteria.
The document discusses the importance of developer experience (DX) and how to improve it. DX refers to the interactions and events between developers and tools/APIs, both positive and negative. Good DX matters because it leads to innovative usage and evangelism, while poor DX results in minimal usage and high turnover. The document provides tips for DX providers to consider users at each stage, from signing up and getting started to ongoing use and support. It emphasizes the importance of documentation, API design, and issue tracking/support to ensure developers enjoy and want to continue using a tool.
User experience (UX) encompasses all aspects of a user's interaction with a company, its services, and products. UX involves a person's behaviors, attitudes, and emotions when using a product or service. It also includes their perceptions of aspects like usability, ease of use, and efficiency. UX is dynamic as it changes over time with usage circumstances and system changes. To design for positive UX, companies use user-centered design approaches like personas, user stories, prototypes, and usability testing to understand users and optimize the product around their needs and goals. Various tools and methods are used to measure and improve UX.
This document discusses various aspects of user experience (UX) design including visual design, system design, branding, customer service, packaging, product unboxing, and how human emotion determines UX. It provides techniques for UX design such as using humor, recognizing patterns, engagement, communication, and building relationships. It also covers ergonomics guidelines for UX like consistency, simplicity, feedback, attention, and modality. The document examines the influence of design on UX and discusses simplifying interactions through minimalism and asking questions about users. Finally, it discusses gamifying interactions and experience to influence human habits.
This document discusses various aspects of user experience (UX) design including visual design, system design, branding, customer service, packaging, product unboxing, and how human emotion determines UX. It provides techniques for UX design such as using humor, recognizing patterns, engagement, communication, and building relationships. It also covers ergonomics guidelines for UX like consistency, simplicity, feedback, attention, and modality. Finally, it discusses how design influences UX and techniques like minimalism, simplifying interactions by asking who, what, why, and when questions, and gamifying interactions.
In her more than thirty years in the IT industry, Isabel Evans says she has learned more from her failures than she has from her successes. Why is this? And what has she learned? That making mistakes is the way to learn, and that allowing yourself to be wrong allows you to grow. Join Isabel to enjoy her greatest failures, and learn not to make the same mistakes she has made. Recently, someone described Isabel as unusual in the technology industries as she is an “elderly woman,” so she has taken as her motto Bob Dylan’s line: “I was so much older then—I’m younger than that now.” Isabel shares why being Generation A means continuing to fail, fail, and finally succeed—over and over again. As someone affected by the “imposter syndrome,” she reflects on confidence dropping as expertise grows, the necessity of dealing with constant change, and why we can never know everything. Isabel may be an elderly woman in tech but she is still planning to make more mistakes and learn more new skills and knowledge. Join Isabel for this stage of her journey.
'10 Great but now Overlooked Tools' by Graham ThomasTEST Huddle
The idea for this presentation came directly from EuroSTAR 2011. Sitting on the bus back to the conference centre after attending the Gala Dinner, a discussion started, about industry luminaries who turn up at conferences and give presentations which roughly say "Don't do all the stuff that I told you to do 5 years ago! Do this stuff now." But, but, but . . . .
As we got talking I realised how many simple effective tools I no longer used, because they have either become overlooked, forgotten and thus fallen into disuse, or because modern methods claim not to need them and they are redundant. I wondered if any of them were worth looking at again - starting with my trusty flowcharting template; I realised it is a great tool which I have overlooked for far too long!
Here is my list of 10 great but now overlooked tools:
• Flowcharts
• Prototypes
• Project Plans
• Mind Maps
• Tools we already have at our disposal like ....
• Aptitude Tests
• Hexadecimal Calculators
• Desk Checking
• Data Dictionaries and Workbenches
This is my list of really useful tools that I think are overlooked. In the webinar I will outline each tool, why I think it was great, and what we are missing out by not using it.
And it naturally follows that if there are some tools we have overlooked then there are also some tools that we should get rid of! I will identify some.
Hopefully this webinar will give you a different perspective on tools to use for testing, some tools that may be improved upon or plain discarded, and help you think about the tools you currently use and maybe to view them in a different light.
This document discusses the importance and benefits of user testing websites through diy methods. It begins by defining usability as how well users can achieve goals on a product and their satisfaction level. User testing helps remove obstacles between users and their goals, leading to more conversions and money. While we think we know our users, testing reveals how they actually use sites. Common mistakes are obvious, but some bad designs seem good initially. The document recommends testing at all stages of a project with inexpensive methods like remote and in-person testing. Only a few users and tasks are needed, and changes do not need to be big or expensive to make large impacts to metrics like conversions. The key is to test early and often.
The document describes a workshop on agile usability testing through user checks. User checks involve testing a design with real users within their context and retesting after improvements within one week. This allows testing early and often to improve the design iteratively based on user feedback. The workshop covers how to structure user check sessions, including introducing tasks, observing users and evaluating findings after each session to prioritize improvements for retesting. Volunteers then do a practice user check session with observers collecting feedback on sticky notes to discuss findings and potential design updates.
The document summarizes different low-cost methods for conducting user research on web products with limited resources. It discusses using heatmapping and analytics tools to evaluate existing use, as well as virtual usability testing, guerrilla testing, and microfeedback forms to gather user experience feedback during the design process. Specific tools mentioned include CrazyEgg, Google Analytics, Usabilla, and building your own microfeedback forms. Examples are provided from a case study of redesigning a university library website.
Hacking UX: Product Design Thinking for TechiesMelissa Ng
Developers often struggle with user experience (UX) design because their technical mindset does not always align with how users think and behave. They may focus too much on execution and technical requirements rather than usability. Understanding user needs through research methods like interviews is important for designing products that meet business goals and satisfy customers. The workshop aimed to get developers doing hands-on user research exercises to better understand UX design processes. Participants conducted speed interviews with each other about a travel app concept to generate insights for creating user personas.
People factors in automation v3 half day tutorial star canada 2017 stareast...Isabel Evans
Workshop: Successful test automation is not just about selecting and implementing tools and a technical infrastructure. People in teams make the changes that are required. People ensure the success or failure of the automation project. Understanding and managing expectations, attitudes toward change, teamwork, motivation, and communication are all vital if automation projects are to succeed. Isabel Evans identifies and discusses human factors around automation, teamwork, and human behavior to enable you to understand resistance to change, overcome mistrust of automation, and moderate inflated expectations of what automation can achieve. Learn why people react as they do to the prospect and actuality of automation projects. Join Isabel to explore new strategies for managing people and teams through their changing emotional responses
Feedback loops between tooling and cultureChris Winters
Discussion of how tools technologists create impact culture, and how culture impacts those tools. Not really a standalone presentation but hopefully useful.
Joint slides Isabel Evans Alan Richardson Feb UKStar 2017Alan Richardson
People and automation – a conversation
UX? What about TX for Test Automation?
Are we technical enough? Are the problems that people report with tool adoption a problem of testers not being technical enough or of tools not being easy to use? Are we over emphasising the technical and ignoring the personal?
What made you a software testing leader?Rosie Sherry
The document discusses leadership in the software testing field from the perspectives of experts James Bach and Michael Bolton. It begins by providing context on Bach and Bolton's work inspiring and training testers around the world. When asked about their paths to leadership, Bach notes he always had a leadership sense from a young age and was thrown out of his house at 14, which led him to independence. Bolton reflects on a recent trip where frigid weather highlighted the incredible safety record of airlines, achieved through rigorous testing and evaluation. The discussion centers on organic versus intentional routes to leadership positions in the testing field.
What makes software development complex isn't the code, it's the humans. The most effective way to improve our capabilities in software development is to better understand ourselves.
In this talk, I'll introduce a conceptual model for human interaction, identity, culture, communication, relationships, and learning based on the foundational model of Idea Flow. If you were to write a simulator to describe the interaction of humans, this talk would describe the architecture.
Learn how to understand the humans on your team and fix the bugs in communication, by thinking about your teammates like code!
Edit
Archive
Delete
I'm not a scientist or a psychologist. These ideas are based on a combination of personal experience, reading lots of cognitive science books, and a couple years of running experiments on developers. As I struggled through the challenges of getting a software concept from my head to another developer's head (interpersonal Idea Flow), I learned a whole lot about human interaction.
As software developers, we have to work together, think together, and solve problems together to do our jobs. Code? We get it. Humans? WTF?!
Fortunately, humans are predictably irrational, predictably emotional, and predictably judgmental creatures. Of course those pesky humans will always do a few unexpected things, but once we know the algorithm for peace and harmony among humans, we can start debugging the communication problems on our team.
Since the dawn of software development, we've struggled with a huge disconnect between the management world and the engineering world. We try to explain our problems in terms of “technical debt”, but somehow the message seems to get lost in translation, and we drive our projects into the ground, over and over again.
What if we could detect the earliest indicators of a project going off the rails, and had data to convince management to take action? What if we could bridge this communication gap once and for all?
In this session, we'll focus on a key paradigm shift for how we can measure the human factors in software development, and translate the “friction” we experience into explicit risk models for project decision-making.
The 10 Commandments of UX provide guiding principles for user experience design:
1. Understand the user's perspective rather than your own perspective or the client's perspective.
2. Understand the problem you are trying to solve for the user and identify the core problem before forming solutions.
3. Avoid over-engineering and focus on simplicity - most of the time simpler is better. Ask questions to ensure you understand user needs and expectations.
An Introduction to User Experience for Dev's & TechiesScott Savage
Presented by Scott A. Savage (www.scottAsavage.com) for Web Content Mavens at General Assembly in Washington, DC on March 18, 2015.
This presentation provides an overview of how developers and non-user experience people can integrate good user experience ideas and methodologies into their professional processes and work.
This document provides an overview and definitions of usability testing. It discusses that usability testing involves having users complete tasks while thinking out loud to uncover usability issues. It recommends testing with 5 users to find 80% of issues. The document outlines best practices for planning a test, including developing test plans and tasks, finding and screening participants, conducting sessions, analyzing data, and reporting findings. It emphasizes that usability testing should involve observing how users complete realistic tasks rather than just asking for feedback.
Guerilla Usability Testing, or How I learned that perfectly imperfect tests a...Sara Snyder
This document discusses the benefits of guerrilla usability testing and provides tips for low-cost, DIY testing. It outlines that imperfect tests are still worthwhile as they can uncover unexpected issues, fix problems early, and introduce objectivity. The document then shares three stories of guerrilla testing experiences, highlighting lessons learned around recruitment strategies, engaging stakeholders, and testing on the go. It emphasizes that the best usability test is one that is done repeatedly and stresses making the testing and reporting process painless.
This document discusses different definitions and conceptions of artificial intelligence (AI). It begins by describing two conceptions: 1) computational models of human behavior, meaning programs that behave externally like humans, and 2) computational models of human thought processes, meaning programs that operate internally like human thought. It then discusses the idea of 3) computational systems that behave intelligently, but notes the difficulty in defining intelligence. The document suggests focusing instead on 4) computational systems that behave rationally. It concludes by mentioning some AI applications and noting the course will focus on building rationally behaving computational systems, while also discussing techniques useful for a variety of applications.
The document discusses common user experience mistakes made by recruitment websites and provides recommendations for improving user experience. It summarizes that a Forrester study found 12 major US job boards all failed user experience testing, with issues like tasks being difficult to complete and excessive advertising obscuring content. The document then details specific user experience mistakes, such as sites requiring users to click in and out of pages to compare jobs ("pogo sticking") and making unsubscribing from email alerts very difficult. It recommends user experience training for all staff, iterative user research, and having user needs represented at the highest levels to avoid such issues long-term.
Getting into UX: How to take your first steps to a career in user experiencePhil Barrett
Want to work in UX but can't get a job without experience? Here are a few ideas about how to break into the UX business, make a portfolio, win at your interview and design assessment - and whether UX is the right career for you. You can start doing UX in the job you already have, then build a portfolio from that.
Paulo Fonseca gave a presentation on how to become a successful UX designer. He emphasized that UX designers need to exercise empathy, observe people deeply without judgment, ask thoughtful questions to understand problems from different perspectives, and talk to humans to understand their experiences. Designers also need strong critical thinking skills to analyze problems logically and have the courage to speak up with honest feedback and new ideas. The presentation highlighted key skills like listening without dominating conversations, reframing questions to be answerable, and focusing on facts over opinions.
What do you do when you are not working? Whatever it is, you probably have a place where you work on your interests, some tools and equipment, and especially some things you always have with you. Perhaps you have a room or shed or tool rack with your favorite and your most used equipment easily at hand in a workbox. Wouldn’t it be great to have your own workbox for testing? Well, you already do! Everyone’s “mental tool set” is different, but we all need versatile, strong, and multipurpose approaches to our work. In thirty years of software testing, Isabel Evans has developed her own trusted workbox of approaches, methods, and ideas that help her communicate, manage, improve, test, work in teams, and solve problems. Isabel shares her workbox with you and uses a mix of teaching, coaching, discussion, and hands-on exercises to help you share your workboxes and restock your “mental tool set” for testing.
I was so much older then isabel btd2016 lightningkey (3)Isabel Evans
This document summarizes the lightning talks given at the BTD2016 conference. It includes:
- Brief biographies of each speaker: Mieke Gevers, Mark Tomlinson, Gil Zilberfeld, Doug Hoffman, Debbie Friedenburg, Matt Griscom, and Isabel Evans.
- An overview of Isabel Evans' talk where she reflected on rebooting her career at age 25 and her experiences over the past 50 years in various roles.
- Notes from Evans' talk on dealing with imposter phenomenon and expanding one's knowledge and skills over time.
- The document closes by thanking attendees and inviting questions.
In her more than thirty years in the IT industry, Isabel Evans says she has learned more from her failures than she has from her successes. Why is this? And what has she learned? That making mistakes is the way to learn, and that allowing yourself to be wrong allows you to grow. Join Isabel to enjoy her greatest failures, and learn not to make the same mistakes she has made. Recently, someone described Isabel as unusual in the technology industries as she is an “elderly woman,” so she has taken as her motto Bob Dylan’s line: “I was so much older then—I’m younger than that now.” Isabel shares why being Generation A means continuing to fail, fail, and finally succeed—over and over again. As someone affected by the “imposter syndrome,” she reflects on confidence dropping as expertise grows, the necessity of dealing with constant change, and why we can never know everything. Isabel may be an elderly woman in tech but she is still planning to make more mistakes and learn more new skills and knowledge. Join Isabel for this stage of her journey.
'10 Great but now Overlooked Tools' by Graham ThomasTEST Huddle
The idea for this presentation came directly from EuroSTAR 2011. Sitting on the bus back to the conference centre after attending the Gala Dinner, a discussion started, about industry luminaries who turn up at conferences and give presentations which roughly say "Don't do all the stuff that I told you to do 5 years ago! Do this stuff now." But, but, but . . . .
As we got talking I realised how many simple effective tools I no longer used, because they have either become overlooked, forgotten and thus fallen into disuse, or because modern methods claim not to need them and they are redundant. I wondered if any of them were worth looking at again - starting with my trusty flowcharting template; I realised it is a great tool which I have overlooked for far too long!
Here is my list of 10 great but now overlooked tools:
• Flowcharts
• Prototypes
• Project Plans
• Mind Maps
• Tools we already have at our disposal like ....
• Aptitude Tests
• Hexadecimal Calculators
• Desk Checking
• Data Dictionaries and Workbenches
This is my list of really useful tools that I think are overlooked. In the webinar I will outline each tool, why I think it was great, and what we are missing out by not using it.
And it naturally follows that if there are some tools we have overlooked then there are also some tools that we should get rid of! I will identify some.
Hopefully this webinar will give you a different perspective on tools to use for testing, some tools that may be improved upon or plain discarded, and help you think about the tools you currently use and maybe to view them in a different light.
This document discusses the importance and benefits of user testing websites through diy methods. It begins by defining usability as how well users can achieve goals on a product and their satisfaction level. User testing helps remove obstacles between users and their goals, leading to more conversions and money. While we think we know our users, testing reveals how they actually use sites. Common mistakes are obvious, but some bad designs seem good initially. The document recommends testing at all stages of a project with inexpensive methods like remote and in-person testing. Only a few users and tasks are needed, and changes do not need to be big or expensive to make large impacts to metrics like conversions. The key is to test early and often.
The document describes a workshop on agile usability testing through user checks. User checks involve testing a design with real users within their context and retesting after improvements within one week. This allows testing early and often to improve the design iteratively based on user feedback. The workshop covers how to structure user check sessions, including introducing tasks, observing users and evaluating findings after each session to prioritize improvements for retesting. Volunteers then do a practice user check session with observers collecting feedback on sticky notes to discuss findings and potential design updates.
The document summarizes different low-cost methods for conducting user research on web products with limited resources. It discusses using heatmapping and analytics tools to evaluate existing use, as well as virtual usability testing, guerrilla testing, and microfeedback forms to gather user experience feedback during the design process. Specific tools mentioned include CrazyEgg, Google Analytics, Usabilla, and building your own microfeedback forms. Examples are provided from a case study of redesigning a university library website.
Hacking UX: Product Design Thinking for TechiesMelissa Ng
Developers often struggle with user experience (UX) design because their technical mindset does not always align with how users think and behave. They may focus too much on execution and technical requirements rather than usability. Understanding user needs through research methods like interviews is important for designing products that meet business goals and satisfy customers. The workshop aimed to get developers doing hands-on user research exercises to better understand UX design processes. Participants conducted speed interviews with each other about a travel app concept to generate insights for creating user personas.
People factors in automation v3 half day tutorial star canada 2017 stareast...Isabel Evans
Workshop: Successful test automation is not just about selecting and implementing tools and a technical infrastructure. People in teams make the changes that are required. People ensure the success or failure of the automation project. Understanding and managing expectations, attitudes toward change, teamwork, motivation, and communication are all vital if automation projects are to succeed. Isabel Evans identifies and discusses human factors around automation, teamwork, and human behavior to enable you to understand resistance to change, overcome mistrust of automation, and moderate inflated expectations of what automation can achieve. Learn why people react as they do to the prospect and actuality of automation projects. Join Isabel to explore new strategies for managing people and teams through their changing emotional responses
Feedback loops between tooling and cultureChris Winters
Discussion of how tools technologists create impact culture, and how culture impacts those tools. Not really a standalone presentation but hopefully useful.
Joint slides Isabel Evans Alan Richardson Feb UKStar 2017Alan Richardson
People and automation – a conversation
UX? What about TX for Test Automation?
Are we technical enough? Are the problems that people report with tool adoption a problem of testers not being technical enough or of tools not being easy to use? Are we over emphasising the technical and ignoring the personal?
What made you a software testing leader?Rosie Sherry
The document discusses leadership in the software testing field from the perspectives of experts James Bach and Michael Bolton. It begins by providing context on Bach and Bolton's work inspiring and training testers around the world. When asked about their paths to leadership, Bach notes he always had a leadership sense from a young age and was thrown out of his house at 14, which led him to independence. Bolton reflects on a recent trip where frigid weather highlighted the incredible safety record of airlines, achieved through rigorous testing and evaluation. The discussion centers on organic versus intentional routes to leadership positions in the testing field.
What makes software development complex isn't the code, it's the humans. The most effective way to improve our capabilities in software development is to better understand ourselves.
In this talk, I'll introduce a conceptual model for human interaction, identity, culture, communication, relationships, and learning based on the foundational model of Idea Flow. If you were to write a simulator to describe the interaction of humans, this talk would describe the architecture.
Learn how to understand the humans on your team and fix the bugs in communication, by thinking about your teammates like code!
Edit
Archive
Delete
I'm not a scientist or a psychologist. These ideas are based on a combination of personal experience, reading lots of cognitive science books, and a couple years of running experiments on developers. As I struggled through the challenges of getting a software concept from my head to another developer's head (interpersonal Idea Flow), I learned a whole lot about human interaction.
As software developers, we have to work together, think together, and solve problems together to do our jobs. Code? We get it. Humans? WTF?!
Fortunately, humans are predictably irrational, predictably emotional, and predictably judgmental creatures. Of course those pesky humans will always do a few unexpected things, but once we know the algorithm for peace and harmony among humans, we can start debugging the communication problems on our team.
Since the dawn of software development, we've struggled with a huge disconnect between the management world and the engineering world. We try to explain our problems in terms of “technical debt”, but somehow the message seems to get lost in translation, and we drive our projects into the ground, over and over again.
What if we could detect the earliest indicators of a project going off the rails, and had data to convince management to take action? What if we could bridge this communication gap once and for all?
In this session, we'll focus on a key paradigm shift for how we can measure the human factors in software development, and translate the “friction” we experience into explicit risk models for project decision-making.
The 10 Commandments of UX provide guiding principles for user experience design:
1. Understand the user's perspective rather than your own perspective or the client's perspective.
2. Understand the problem you are trying to solve for the user and identify the core problem before forming solutions.
3. Avoid over-engineering and focus on simplicity - most of the time simpler is better. Ask questions to ensure you understand user needs and expectations.
An Introduction to User Experience for Dev's & TechiesScott Savage
Presented by Scott A. Savage (www.scottAsavage.com) for Web Content Mavens at General Assembly in Washington, DC on March 18, 2015.
This presentation provides an overview of how developers and non-user experience people can integrate good user experience ideas and methodologies into their professional processes and work.
This document provides an overview and definitions of usability testing. It discusses that usability testing involves having users complete tasks while thinking out loud to uncover usability issues. It recommends testing with 5 users to find 80% of issues. The document outlines best practices for planning a test, including developing test plans and tasks, finding and screening participants, conducting sessions, analyzing data, and reporting findings. It emphasizes that usability testing should involve observing how users complete realistic tasks rather than just asking for feedback.
Guerilla Usability Testing, or How I learned that perfectly imperfect tests a...Sara Snyder
This document discusses the benefits of guerrilla usability testing and provides tips for low-cost, DIY testing. It outlines that imperfect tests are still worthwhile as they can uncover unexpected issues, fix problems early, and introduce objectivity. The document then shares three stories of guerrilla testing experiences, highlighting lessons learned around recruitment strategies, engaging stakeholders, and testing on the go. It emphasizes that the best usability test is one that is done repeatedly and stresses making the testing and reporting process painless.
This document discusses different definitions and conceptions of artificial intelligence (AI). It begins by describing two conceptions: 1) computational models of human behavior, meaning programs that behave externally like humans, and 2) computational models of human thought processes, meaning programs that operate internally like human thought. It then discusses the idea of 3) computational systems that behave intelligently, but notes the difficulty in defining intelligence. The document suggests focusing instead on 4) computational systems that behave rationally. It concludes by mentioning some AI applications and noting the course will focus on building rationally behaving computational systems, while also discussing techniques useful for a variety of applications.
The document discusses common user experience mistakes made by recruitment websites and provides recommendations for improving user experience. It summarizes that a Forrester study found 12 major US job boards all failed user experience testing, with issues like tasks being difficult to complete and excessive advertising obscuring content. The document then details specific user experience mistakes, such as sites requiring users to click in and out of pages to compare jobs ("pogo sticking") and making unsubscribing from email alerts very difficult. It recommends user experience training for all staff, iterative user research, and having user needs represented at the highest levels to avoid such issues long-term.
Getting into UX: How to take your first steps to a career in user experiencePhil Barrett
Want to work in UX but can't get a job without experience? Here are a few ideas about how to break into the UX business, make a portfolio, win at your interview and design assessment - and whether UX is the right career for you. You can start doing UX in the job you already have, then build a portfolio from that.
Paulo Fonseca gave a presentation on how to become a successful UX designer. He emphasized that UX designers need to exercise empathy, observe people deeply without judgment, ask thoughtful questions to understand problems from different perspectives, and talk to humans to understand their experiences. Designers also need strong critical thinking skills to analyze problems logically and have the courage to speak up with honest feedback and new ideas. The presentation highlighted key skills like listening without dominating conversations, reframing questions to be answerable, and focusing on facts over opinions.
What do you do when you are not working? Whatever it is, you probably have a place where you work on your interests, some tools and equipment, and especially some things you always have with you. Perhaps you have a room or shed or tool rack with your favorite and your most used equipment easily at hand in a workbox. Wouldn’t it be great to have your own workbox for testing? Well, you already do! Everyone’s “mental tool set” is different, but we all need versatile, strong, and multipurpose approaches to our work. In thirty years of software testing, Isabel Evans has developed her own trusted workbox of approaches, methods, and ideas that help her communicate, manage, improve, test, work in teams, and solve problems. Isabel shares her workbox with you and uses a mix of teaching, coaching, discussion, and hands-on exercises to help you share your workboxes and restock your “mental tool set” for testing.
I was so much older then isabel btd2016 lightningkey (3)Isabel Evans
This document summarizes the lightning talks given at the BTD2016 conference. It includes:
- Brief biographies of each speaker: Mieke Gevers, Mark Tomlinson, Gil Zilberfeld, Doug Hoffman, Debbie Friedenburg, Matt Griscom, and Isabel Evans.
- An overview of Isabel Evans' talk where she reflected on rebooting her career at age 25 and her experiences over the past 50 years in various roles.
- Notes from Evans' talk on dealing with imposter phenomenon and expanding one's knowledge and skills over time.
- The document closes by thanking attendees and inviting questions.
As software practitioners focusing on technology issues, we often find that our messages to management and the business are either not heard or are misinterpreted. And sometimes we do not hear the messages that they need us to hear. Isabel Evans examines our natural ability to tell stories and how everyone’s built-in receptiveness to narratives will help you communicate productively about testing and quality.
Isabel looks at how we can tell our testing stories in a way that is appealing to our audience. That means thinking about the role of oral, written, and visual representations of testing stories and practicing communicating through the analogies of novels, short stories, picture books, poems, and songs. Because we will need a variety of story formats for our testing messages to work best, Isabel shares how to adapt testing stories to different audiences. Learn how we can better listen to other people’s stories and adapt our listening style to different storytellers.
Quality in use why do we need to understand the user experience v1 handout ...Isabel Evans
Users have a choice - they can use or products or go elsewhere - in the words of the Clash - Should they stay or should they go? What if they do not have a choice? what happens to them then?
Learning to tell testing stories workshop v2 handout (3) euro star nov 2016Isabel Evans
This document outlines an upcoming workshop on learning to tell testing stories. The workshop will be led by Isabel Evans and held on Thursday from 09:30 to 11:30. The workshop will cover various aspects of storytelling as it relates to testing, including who tells stories, beginnings and headlines, brevity, serials and endings. Attendees will have opportunities to practice telling stories about their own projects in different formats like haiku and sonnets. The goal is to help testers learn to effectively communicate testing work and outcomes through storytelling.
State transition workshop sigist sept 2017 sue a isabel e v3Isabel Evans
Focus on state transition testing – a way to model your testing world! by Sue Atkins and Isabel Evans.
Test design is a fundamental part of our toolbox as testers, whether we are working with exploratory approaches, designing scripts to be built into automation or carrying out manual scripted testing. As part of the September SIGiST theme of “Increasing our capabilities” we are delighted to offer this masterclass workshop focused on one important test design technique: State Transition Testing.
State transition modelling and testing is useful for understanding diverse types of application and events, such as movement between screens in an application, navigation around websites, and triggers for action in embedded systems.
In 90 minutes, Sue and Isabel will introduce the State Transition technique, show examples and provide you with exercises to try it for yourself. We both use this technique in our own testing, finding it can be applied to
- Review specifications and find potential defects and missing requirements;
- Derive a test basis from discussion of unwritten requirements and designs;
- Derive tests and expected results;
- Drive the direction for a non-scripted approach to test execution;
- Provide input to automated tests.
The workshop will include taught elements, exercises and discussion.
My failures in software testing v7 star east 2017Isabel Evans
In her more than thirty years in the IT industry, Isabel Evans says she has learned more from her failures than she has from her successes. Why is this? And what has she learned? That making mistakes is the way to learn, and that allowing yourself to be wrong allows you to grow. Join Isabel to enjoy her greatest failures, and learn not to make the same mistakes she has made. Recently, someone described Isabel as unusual in the technology industries as she is an “elderly woman,” so she has taken as her motto Bob Dylan’s line: “I was so much older then—I’m younger than that now.” Isabel shares why being Generation A means continuing to fail, fail, and finally succeed—over and over again. As someone affected by the “imposter syndrome,” she reflects on confidence dropping as expertise grows, the necessity of dealing with constant change, and why we can never know everything. Isabel may be an elderly woman in tech but she is still planning to make more mistakes and learn more new skills and knowledge. Join Isabel for this stage of her journey.
Leading following managing you can help your group thrive star canada 2017 al...Isabel Evans
As testers or test managers, being effective mentors, coaches, managers and leaders is critical to our team success. Quite often we also have a role in driving change, influencing others and helping individuals and teams move from where they are to the next level of excellence. We must interact with many people and work together in project teams as efficiently and effectively as possible. Join Isabel Evans as she discusses the range of interaction approaches or styles of leadership and management, what styles we feel most comfortable with and how we react to both being leaders and being led. Regardless of the software life cycle model we use, as testers, we need to understand these interactions, and when to adopt a leadership, mentoring, coaching, following, or learning attitude to help our group thrive. It’s not just humans who work in groups. Other animals can tell us about how we interact with individuals, teams, and groups both as leaders and followers. Use their example to leave with an understanding of leadership styles from authoritarian to collaborative and how we react to them, and learn how to use these approaches most effectively and efficiently.
Agile india leading managing-following - keynote v5 for sharingIsabel Evans
The document discusses leadership, management, and followership in teams. It uses examples from animal behavior like orcas, wolves, and chimpanzees to illustrate how different species have leaders, followers, and ways of cooperating or competing within groups. It also discusses different leadership and followership styles that people exhibit, and how understanding habits, territory, and using coaching can help groups thrive. The overall message is that by remembering we are social beings, respecting others, and continuously learning and improving ourselves, we can be happy and make the world a little better.
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
The Rising Future of CPaaS in the Middle East 2024Yara Milbes
Explore "The Rising Future of CPaaS in the Middle East in 2024" with this comprehensive PPT presentation. Discover how Communication Platforms as a Service (CPaaS) is transforming communication across various sectors in the Middle East.
Consistent toolbox talks are critical for maintaining workplace safety, as they provide regular opportunities to address specific hazards and reinforce safe practices.
These brief, focused sessions ensure that safety is a continual conversation rather than a one-time event, which helps keep safety protocols fresh in employees' minds. Studies have shown that shorter, more frequent training sessions are more effective for retention and behavior change compared to longer, infrequent sessions.
Engaging workers regularly, toolbox talks promote a culture of safety, empower employees to voice concerns, and ultimately reduce the likelihood of accidents and injuries on site.
The traditional method of conducting safety talks with paper documents and lengthy meetings is not only time-consuming but also less effective. Manual tracking of attendance and compliance is prone to errors and inconsistencies, leading to gaps in safety communication and potential non-compliance with OSHA regulations. Switching to a digital solution like Safelyio offers significant advantages.
Safelyio automates the delivery and documentation of safety talks, ensuring consistency and accessibility. The microlearning approach breaks down complex safety protocols into manageable, bite-sized pieces, making it easier for employees to absorb and retain information.
This method minimizes disruptions to work schedules, eliminates the hassle of paperwork, and ensures that all safety communications are tracked and recorded accurately. Ultimately, using a digital platform like Safelyio enhances engagement, compliance, and overall safety performance on site. https://safelyio.com/
Project Management: The Role of Project Dashboards.pdfKarya Keeper
Project management is a crucial aspect of any organization, ensuring that projects are completed efficiently and effectively. One of the key tools used in project management is the project dashboard, which provides a comprehensive view of project progress and performance. In this article, we will explore the role of project dashboards in project management, highlighting their key features and benefits.
The Key to Digital Success_ A Comprehensive Guide to Continuous Testing Integ...kalichargn70th171
In today's business landscape, digital integration is ubiquitous, demanding swift innovation as a necessity rather than a luxury. In a fiercely competitive market with heightened customer expectations, the timely launch of flawless digital products is crucial for both acquisition and retention—any delay risks ceding market share to competitors.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Drona Infotech is a premier mobile app development company in Noida, providing cutting-edge solutions for businesses.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdfBaha Majid
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
14 th Edition of International conference on computer visionShulagnaSarkar2
About the event
14th Edition of International conference on computer vision
Computer conferences organized by ScienceFather group. ScienceFather takes the privilege to invite speakers participants students delegates and exhibitors from across the globe to its International Conference on computer conferences to be held in the Various Beautiful cites of the world. computer conferences are a discussion of common Inventions-related issues and additionally trade information share proof thoughts and insight into advanced developments in the science inventions service system. New technology may create many materials and devices with a vast range of applications such as in Science medicine electronics biomaterials energy production and consumer products.
Nomination are Open!! Don't Miss it
Visit: computer.scifat.com
Award Nomination: https://x-i.me/ishnom
Conference Submission: https://x-i.me/anicon
For Enquiry: Computer@scifat.com
Enhanced Screen Flows UI/UX using SLDS with Tom KittPeter Caitens
Join us for an engaging session led by Flow Champion, Tom Kitt. This session will dive into a technique of enhancing the user interfaces and user experiences within Screen Flows using the Salesforce Lightning Design System (SLDS). This technique uses Native functionality, with No Apex Code, No Custom Components and No Managed Packages required.
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdfVALiNTRY360
Salesforce Healthcare CRM, implemented by VALiNTRY360, revolutionizes patient management by enhancing patient engagement, streamlining administrative processes, and improving care coordination. Its advanced analytics, robust security, and seamless integration with telehealth services ensure that healthcare providers can deliver personalized, efficient, and secure patient care. By automating routine tasks and providing actionable insights, Salesforce Healthcare CRM enables healthcare providers to focus on delivering high-quality care, leading to better patient outcomes and higher satisfaction. VALiNTRY360's expertise ensures a tailored solution that meets the unique needs of any healthcare practice, from small clinics to large hospital systems.
For more info visit us https://valintry360.com/solutions/health-life-sciences
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
Microservice Teams - How the cloud changes the way we workSven Peters
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
Preparing Non - Technical Founders for Engaging a Tech AgencyISH Technologies
Preparing non-technical founders before engaging a tech agency is crucial for the success of their projects. It starts with clearly defining their vision and goals, conducting thorough market research, and gaining a basic understanding of relevant technologies. Setting realistic expectations and preparing a detailed project brief are essential steps. Founders should select a tech agency with a proven track record and establish clear communication channels. Additionally, addressing legal and contractual considerations and planning for post-launch support are vital to ensure a smooth and successful collaboration. This preparation empowers non-technical founders to effectively communicate their needs and work seamlessly with their chosen tech agency.Visit our site to get more details about this. Contact us today www.ishtechnologies.com.au
Malibou Pitch Deck For Its €3M Seed Roundsjcobrien
French start-up Malibou raised a €3 million Seed Round to develop its payroll and human resources
management platform for VSEs and SMEs. The financing round was led by investors Breega, Y Combinator, and FCVC.
A neural network is a machine learning program, or model, that makes decisions in a manner similar to the human brain, by using processes that mimic the way biological neurons work together to identify phenomena, weigh options and arrive at conclusions.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian CompaniesQuickdice ERP
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Tuxt v5 scot sig 2017 ucaat 2016
1. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
UX? What about TX for Test Automation?
Isabel Evans fbcs citp
ie@isabelevans.uk
www.isabelevans.uk
Glasgow May 31st 2017
2. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Three key points
• Test automation requires consideration of the
UX for the tool and the tests;
• People who use automation might not always
be technical but they are always human;
• UX-D and UX-T for test automation supports
improved decision making and quality.
3. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
“Test automation requires
consideration of the UX for the tool
and the tests”
What is UX?
User eXperience
UX-D (Design) and UX-T (Testing)
4. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Making life
better
-
example
Cyclist’s UX
5. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
X:
Ignorance
A:
Uncertainty
B:
Awakening
C: Enlightenment
D: Wisdom
E: Certainty
We know why we
do not have UX
problems
It’s the stupid users!
Why are our users having a problem?
Do they always have to have a problem?
We are identifying and
resolving UX problems so our
users don’t experience them
We do UX defect
preventionMaturity
6. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
What do you test with?
Head
7. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
What do you test with,
when you test UX and think TX?
Head
Heart
Gut
Soul
8. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
This is the shape of the presentation:
• We are following a UX method
• Generic examples
– A user of Apple computers
– A hospital consultant
– An IT service desk support person
• Specific test automation example
9. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
“People who use automation might
not always be technical but they are
always human”
Who are these people?
Ordinary people
Technical people
10. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Generic Example Personas
(people with emotions)
“It was so beautiful I wanted to marry it
And then it lost my calendar entries and emails”
“This is the clunkiest piece of
technology I have ever had to use
I will have to ask my secretary to
print your test results”
11. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Generic Example Personas
(people working with technology)
http://blogs.ca.com/2016/01/27/moving-it-service-
management-to-the-21st-century/
“Ethnographic research paints a sad
picture of the current state of the
ITSM market.
…vision is to build a solution
designed for humans, not
processes.”
Moving IT Service Management to the 21st century
12. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Technical People on software projects
Why would I want to use a
tool called Github?
Too many geeks are making Automation Script piles
for other geeks, and [calling it] a tool!
it is like working with something designed to be used by
a 12-year-old boy in his bedroom in the 1980’s
a lack of consideration for how people work and
think … basically it’s still the mindset that the
human adapts to the computer, not vice-versa
13. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Alarming Development
“Programming is so hard that only highly talented,
trained, and dedicated individuals can do it passably well.
The inescapable conclusion is that programming as we
know it is just unnatural for humans. The solution is to
reinvent programming to suit
human cognitive skills
to program the way we think. This is a matter of usability.
The sad fact is that modern programming languages are
usability disasters, full of design mistakes inherited from
earlier eras.” http://alarmingdevelopment.org/
14. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Developers Liberation Front
Software developers only use a small subset of
the available tools, and those that a developer
does use are often not fully leveraged.
“We believe that the solution to this problem
can be found by
rethinking the design of
software development tools
based on a better understanding of why
developers use and do not use these tools.”
https://www.youtube.com/watch?v=oQ455i1aCQI http://research.csc.ncsu.edu/dlf/
15. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
“UXD and UXT for test automation
supports improved decision making
and quality”
What decisions?
Trivial decisions
Life-changing decisions
16. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Software Dev / Test Tool users?
The test tool marked all the tests as passed except 1, but in
fact none of the tests marked “passed” had actually run…
so now I wanna know why raising a string exception is bad.
Like what should I be doing instead? Since it thinks it’s a
problem. And so none of these [messages] really help me
I spend 50% of my time wrestling with the
technology instead of solving the problem I
am working on
a lack of consideration for how people work and
think … basically it’s still the mindset that the human
adapts to the computer, not vice-versa
17. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
I need to know… NOW! …AGAIN! …AGA
WHY HAVEN’T WE RELEASED YET
AND WHAT ARE THE RISKS?
WHAT DID I DO WRONG AND WHAT DO I CHANGE?
WHAT STEP DO I TAKE NEXT?
HOW MUCH LONGER WILL THIS TAKE?
18. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
“What about TX for Test
Automation?”
Yeah, but how?
TX = Tester eXperience
19. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Start to think TX
Identify WHO uses your tool
Identify WHY they use it
Identify WHAT they want to do
Identify their EMOTIONS and EMPATHISE!
Score the UX, Quality in Use (QiU) and Internal Quality (IQ) attributes
Write RICH STORIES
Do a USABILITY REVIEW
20. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
TX: Who? Why?
Automation
user?
Developer
Test
engineer
User tester
Test
manager
Product
owner
Automation
specialist
Domain
specialist
WHO
WHY
WHAT
EMOTIONS
UX, QiU, IQ
RICH STORIES
USABILITY REVIEW
21. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
TX: What tasks?
Automation
user?
building
tests
running
tests
checking
results
managing
fault reports
assessing
risk
checking
completion
WHO
WHY
WHAT
EMOTIONS
UX, QiU, IQ
RICH STORIES
USABILITY REVIEW
22. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
TX: What emotions?
WHO
WHY
WHAT
EMOTIONS
UX, QiU, IQ
RICH STORIES
USABILITY REVIEW
23. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Functionality
Performance
Security
Maintainability
Interoperability
Portability
Compatibility
Etc.
Usability
Flexibility
Safety
Accessibility
Etc.
valuable useful
credible findable
usable accessible
meaningful
flowing
playful immersive
seductive
pleasurable
desirable, etc.
Internal
quality
Quality
in Use UX-D
TX: Which attributes?
WHO
WHY
WHAT
EMOTIONS
UX, QiU, IQ
RICH STORIES
USABILITY REVIEW
24. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Attributes Generically:
Different people have different needs
0
2
4
6
8
10
effectiveness
efficiency
conformity
extendability
desirability
excitement
flow
credibility
Quality attribute expectations compared
hospital consultant Apple lover
25. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Attributes Generically:
Different people have different needs
Effectiveness
Efficiency
Satisfaction
ConformityExtendibility
Flow
Credibility
Service Desk Worker
26. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Attributes: Different automation users
have different needs
Effectiveness
Efficiency
Satisfaction
Conformity
Extendibility
Accessibility
Commercial
Health & Safety
Desirability
Flow
test manager automation specialist senior stakeholder
27. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
User Stories…
https://twitter.com/jediuserstories
As a wookie,
I want to rrrrraaaaawwwrr
so I can rrwwwwaaarrgggghhh.
@gojkoadzic user story format and some
words of wisdom from an agile Australia
conference
@sammy_lee12 Oct 10
WHO
WHY
WHAT
EMOTIONS
UX, QiU, IQ
RICH STORIES
USABILITY REVIEW
28. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Rich User Stories Generic Example 1
“As a non-technical person
I want to transfer to the latest gadgets and software
without being tied to one source
Without losing my calendar entries and emails
Because otherwise I am sad and frustrated”
Interoperability,
compatibility,
portability
Flow
Trust
Seductiveness
Flexibility
29. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Rich User Stories Example 2
“As a consultant doctor
I want to concentrate on treating my patients
and communicating well with them
I don’t want to be blocked by the software
Because otherwise my patients and I become frustrated and are
subjected to unnecessary worry”
Flow Trust Speed
Usability
Flexibility
Safety
Functional suitability
Security
BYOD /tablet?
30. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Rich User Stories Example 3
As a service desk worker
I want to use software that supports the flow of my work
And treats me like a human being
And allows me to support my customers without frustration
So that they and I can converse calmly, and trust each other
Flow
Trust
Speed Usability
Flexibility
Performance
Functional suitability
31. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Test automation user: Rich User Story
As a domain specialist tester
I want to use software dev/test tools that provide me with
information in my domain language
That don’t force me to engage with technical issues
That provide information for the developers that they & I can trust
And don’t make me feel stupid
So that we make decisions we both trust without interrupting our
flow of work.
Functional Suitability
Usability
Effectiveness
Conformance
Flow,
credibility,
trust
32. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Check your tools interfaces today…
Easy usability testing - Heuristic Evaluation
Visibility of system
status
Match between
system and the real
world
User control and
freedom
Consistency and
standards
Error prevention
Recognition rather
than recall
Flexibility and
efficiency of use
Aesthetic and
minimalist design
Help users
recognize, diagnose,
and recover from
errors
Help and
documentationhttps://www.nngroup.com/articl
es/ten-usability-heuristics/
WHO
WHY
WHAT
EMOTIONS
UX, QiU, IQ
RICH STORIES
USABILITY REVIEW
33. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
“What about TX for Test
Automation?”
And what are
you doing, Isabel?
34. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Tester eXperience Workbox…?
R&D Awareness Guidelines
Prototyping Meta-tool? Analytics
PhD studies
35. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
“What about TX for Test
Automation?”
And what could you do?
36. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
What could you do?
• Join in when I am ready for industry surveys
• Send me examples (good and bad)
• Email me feedback (www.isabelevans.uk)
• Cheer me on with encouraging noises…
• Apply UX
– To the software you are testing
– To tools you are acquiring and using
– To tools you are building
37. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Email me feedback on my blogposts
• Why we need a better experience of software
– [ref 1] http://bit.ly/2by8XuA Blog post
• Why we need a better toolset
– [ref 2] http://bit.ly/2bM9DNj Blog post
• A vision for the future
– [ref 3] http://bit.ly/2c0tEld Wiktionary definition
– [ref 4] http://bit.ly/2bwAEsb Blog post
Links on www.isabelevans.uk
38. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Don’t just test with your head
Head
39. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Test UX and think TX
Head
Heart
Gut
Soul
40. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
Three key points
• Test automation requires consideration of the
UX for the tool and the tests;
• People who use automation might not always
be technical but they are always human;
• UX-D and UX-T for test automation supports
improved decision making and quality.
41. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
References
• Quality in Use: Meeting User Needs for Quality, Nigel Bevan, Serco Usability Services Journal of System and Software,
1999 (in press)
• “The test tool marked all the tests as passed except 1, but in fact none of the tests marked “passed” had actually run”
Quote from Fewster and Graham “Experiences of Test Automation”
• Quotes from attendees at the WII briefing meeting: “I spend 50% of my time wrestling with the technology instead of
solving the problem I am working on” and “it is like working with something designed to be used by a 12-year-old boy
in his bedroom in the 1980’s”. “Why would I want to use a tool called Github?”
• Gender and other bias in IT tools, for example in tool default behaviour, use of language, voice recognition, gendering
of support tools, is increasingly being studied and remarked on e.g. http://huff.to/1I5pek4, http://bit.ly/1MXNTPf ,
http://bit.ly/2bfI5lY.
• Problems with customer support tools: “Ethnographic research paints a sad picture of the current state of the ITSM
market. …vision is to build a solution designed for humans, not processes” [http://blogs.ca.com/2016/01/27/moving-
itservice-management-to-the-21st-century/]
• Evidence that tools do not work for IT people “…a lack of consideration for how people work and think … basically it’s
still the mindset that the human adapts to the computer, not vice-versa.” (A Taxonomy of Tool-Related Issues Affecting
the Adoption of Model-Driven Engineering by Whittle, Hutchinson, Rouncefield, Burden and Heldal)
• Evidence that developers do not find tools easy to use: “…so now I wanna know why raising a string exception is bad.
Like what should I be doing instead? Since it thinks it’s a problem. And so none of these really help me…” (Why Don’t
Software Developers Use Static Analysis Tools to Find Bugs? By Johnson, Song, and Murphy-Hill).
• ISO 25000 Series of standards (quality in use attributes)
• http://alarmingdevelopment.org/
• http://blogs.ca.com/2016/01/27/moving-it-service-management-to-the-21st-century/
• https://www.youtube.com/watch?v=oQ455i1aCQI
• https://www.nngroup.com/articles/ten-usability-heuristics/
• http://research.csc.ncsu.edu/dlf/
42. Be happy - do good - leave the world a better place than you found it
Isabel
Evans
UX? What about TX for Test Automation?
Isabel Evans fbcs citp
ie@isabelevans.uk
www.isabelevans.uk
Thank you for listening
Questions?