Software testing _mod_9
•Download as PPT, PDF•
1 like•748 views
The document discusses qualities of good testers, noting that they practice epistemology and have skills like critical thinking. Good testers have attitudes of being cautious, curious, and critical. Soft skills are also important for testers, including skills like communication, time management, and maintaining a positive attitude.
Report
Share
Report
Share
![[object Object],[object Object]](https://image.slidesharecdn.com/softwaretestingmod9-101020141747-phpapp02/85/Software-testing-_mod_9-1-320.jpg)
Recommended
Graham Thomas - Software Testing Secrets We Dare Not Tell - EuroSTAR 2013
EuroSTAR Software Testing Conference 2013 presentation on Software Testing Secrets We Dare Not Tell by Graham Thomas.
See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Rapid Software Testing: Reporting
Test reporting is something few testers take time to practice. Nevertheless, it's a fundamental skill—vital for your professional credibility and your own self management. Many people think management judges testing by bugs found or test cases executed. Actually, testing is judged by the story it tells. If your story sounds good, you win. A test report is the story of your testing. It begins as the story we tell ourselves, each moment we are testing, about what we are doing and why. We use the test story within our own minds, to guide our work. James Bach explores the skill of test reporting and examines some of the many different forms a test report might take. As in other areas of testing, context drives good reporting. Sometimes we make an oral report; occasionally we need to write it down. Join James for an in-depth look at the art of the reporting.
Best pratice
The document discusses several important topics for software development including unit testing, clean coding principles, design patterns, and useful development tools. It emphasizes that tests are important for preventing bugs and should be included in all projects. Clean coding principles like DRY, KISS and SRP help produce code that is easier to read, change and maintain. Design patterns provide solutions to common problems and a shared vocabulary for developers. Useful tools include IDEs, version control systems, code analysis tools and text editors which can help programmers work more efficiently if used properly.
How to think smarter about software development
In 2011, the website edge.org asked the question, 'What scientific concept would improve everybody's cognitive toolkit?'. There were answers from renowned intellectuals. I have listed some of the concepts which are relevant to software development.
Rapid Software Testing: Strategy
A test strategy is the set of ideas that guides your test design. It's what explains why you test this instead of that, and why you test this way instead of that way. Strategic thinking matters because testers must make quick decisions about what needs testing right now and what can be left alone. You must be able to work through major threads without being overwhelmed by tiny details. James Bach describes how test strategy is organized around risk but is not defined before testing begins. Rather, it evolves alongside testing as we learn more about the product. We start with a vague idea of our strategy, organize it quickly, and document as needed in a concise way. In the end, the strategy can be as formal and detailed as you want it to be. In the beginning, though, we start small. If you want to focus on testing and not paperwork, this approach is for you.
Rehan Pair Testing Final
The document discusses pair testing, which involves two team members testing software together on one system. One member controls the keyboard and mouse while the other makes notes and asks questions. Pair testing provides benefits like improved bug finding and knowledge sharing between testers and developers. It allows testers to approach testing from different perspectives. The document outlines the pair testing process, environment, session preparation, and benefits of pair testing.
How did i miss that bug rtc
The document discusses how cognitive biases can cause testers to miss bugs. It explains that people have two types of thinking: System 1 thinking is fast, intuitive, and prone to biases, while System 2 thinking is slower, more deliberate, and logical. Common biases that can affect testers include the representative bias, the curse of knowledge, the congruence bias, and the confirmation bias. The document recommends that testers employ more System 1 thinking through techniques like exploratory testing to leverage their intuition to find bugs. It also suggests test managers create an environment where testers feel comfortable using more System 1 thinking approaches.
Software Test Engineering - A guide to becoming successful tester
An slide deck for advising modern day software test engineering individuals on how to train your self to stay above the competition. Testing is not just automation or conformance with the requirements. Its much more than that and practicing the mentioned traits will help become a top notch testing professional.
Recommended
Graham Thomas - Software Testing Secrets We Dare Not Tell - EuroSTAR 2013
EuroSTAR Software Testing Conference 2013 presentation on Software Testing Secrets We Dare Not Tell by Graham Thomas.
See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Rapid Software Testing: Reporting
Test reporting is something few testers take time to practice. Nevertheless, it's a fundamental skill—vital for your professional credibility and your own self management. Many people think management judges testing by bugs found or test cases executed. Actually, testing is judged by the story it tells. If your story sounds good, you win. A test report is the story of your testing. It begins as the story we tell ourselves, each moment we are testing, about what we are doing and why. We use the test story within our own minds, to guide our work. James Bach explores the skill of test reporting and examines some of the many different forms a test report might take. As in other areas of testing, context drives good reporting. Sometimes we make an oral report; occasionally we need to write it down. Join James for an in-depth look at the art of the reporting.
Best pratice
The document discusses several important topics for software development including unit testing, clean coding principles, design patterns, and useful development tools. It emphasizes that tests are important for preventing bugs and should be included in all projects. Clean coding principles like DRY, KISS and SRP help produce code that is easier to read, change and maintain. Design patterns provide solutions to common problems and a shared vocabulary for developers. Useful tools include IDEs, version control systems, code analysis tools and text editors which can help programmers work more efficiently if used properly.
How to think smarter about software development
In 2011, the website edge.org asked the question, 'What scientific concept would improve everybody's cognitive toolkit?'. There were answers from renowned intellectuals. I have listed some of the concepts which are relevant to software development.
Rapid Software Testing: Strategy
A test strategy is the set of ideas that guides your test design. It's what explains why you test this instead of that, and why you test this way instead of that way. Strategic thinking matters because testers must make quick decisions about what needs testing right now and what can be left alone. You must be able to work through major threads without being overwhelmed by tiny details. James Bach describes how test strategy is organized around risk but is not defined before testing begins. Rather, it evolves alongside testing as we learn more about the product. We start with a vague idea of our strategy, organize it quickly, and document as needed in a concise way. In the end, the strategy can be as formal and detailed as you want it to be. In the beginning, though, we start small. If you want to focus on testing and not paperwork, this approach is for you.
Rehan Pair Testing Final
The document discusses pair testing, which involves two team members testing software together on one system. One member controls the keyboard and mouse while the other makes notes and asks questions. Pair testing provides benefits like improved bug finding and knowledge sharing between testers and developers. It allows testers to approach testing from different perspectives. The document outlines the pair testing process, environment, session preparation, and benefits of pair testing.
How did i miss that bug rtc
The document discusses how cognitive biases can cause testers to miss bugs. It explains that people have two types of thinking: System 1 thinking is fast, intuitive, and prone to biases, while System 2 thinking is slower, more deliberate, and logical. Common biases that can affect testers include the representative bias, the curse of knowledge, the congruence bias, and the confirmation bias. The document recommends that testers employ more System 1 thinking through techniques like exploratory testing to leverage their intuition to find bugs. It also suggests test managers create an environment where testers feel comfortable using more System 1 thinking approaches.
Software Test Engineering - A guide to becoming successful tester
An slide deck for advising modern day software test engineering individuals on how to train your self to stay above the competition. Testing is not just automation or conformance with the requirements. Its much more than that and practicing the mentioned traits will help become a top notch testing professional.
Defining Test Competence
In this article I explore the concept of test competence, and how it is connected to complex problems.
Becoming a software testing expert
This document discusses becoming a software testing expert. It provides 10 claims about testing and asks the reader to analyze them. It also presents 3 "expert challenges" involving testing scenarios and asks the reader to provide the expected results or test cases. The document emphasizes that expertise is situational and depends on factors like one's technical knowledge and ability to explain their methodology. It suggests drivers for developing expertise like practicing, gathering resources, and associating with other experts. The overall document provides guidance and questions to help the reader assess and improve their expertise in software testing.
Shrini Kulkarni - Software Metrics - So Simple, Yet So Dangerous
EuroSTAR Software Testing Conference 2009 presentation on Software Metrics - So Simple, Yet So Dangerous by Shrini Kulkarni. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Comm1
The document discusses best practices for conducting software reviews. It notes that reviews, inspections, and walkthroughs are often used interchangeably but mean different things. It recommends adopting written procedures for reviews and focusing on the product, not the producer, during reviews. Reviews should be planned in advance and have 3 to 7 participants with relevant skills and knowledge. The purpose of reviews is to find defects, so discussions should focus on that rather than fixing defects or criticizing style over substance.
Exploratory testing workshop
The document summarizes an exploratory testing workshop. It discusses exploratory testing approaches, common traps testers fall into, and provides tips for effective exploratory testing. As an exercise, participants are asked to use exploratory testing to find issues with a Tilted Twister device within 20 minutes. Key problems identified include inability to detect color differences, motor arm overshooting, difficulty turning it on, calibration cube being too big, and taking too long to solve with memory issues. The debrief discusses the testing process and importance of the tester mindset in exploratory and automated testing.
Rik Teuben - Many Can Quarrel, Fewer Can Argue
EuroSTAR Software Testing Conference 2009 presentation on Many Can Quarrel, Fewer Can Argue by Rik Teuben. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Rapid Software Testing
This document provides an overview and introduction to the Rapid Software Testing course. It acknowledges those who contributed to developing the course material. The document outlines some assumptions about the audience for the course, including that attendees test software and want to improve their testing process. It presents the primary goal of the course as teaching how to test under uncertainty and with scrutiny. Key themes of Rapid Testing are also summarized, including putting the tester's mind at the center and considering cost versus value in testing activities.
Exploratory Testing Explained
Exploratory testing is an approach to testing that emphasizes the freedom and responsibility of testers to continually optimize the value of their work. It is the process of three mutually supportive activities done in parallel: learning, test design, and test execution. With skill and practice, exploratory testers typically uncover an order of magnitude more problems than when the same amount of effort is spent on procedurally scripted testing. All testers conduct exploratory testing in one way or another, but few know how to do it systematically to obtain the greatest benefits. Even fewer can articulate the process. Jon Bach looks at specific heuristics and techniques of exploratory testing that will help you get the most from this highly productive approach. Jon focuses on the skills and dynamics of exploratory testing, and how it can be combined with scripted approaches.
Santa Barbara Agile: Exploratory Testing Explained and Experienced
Exploratory Testing Explained and Experienced
- Exploratory testing is an approach to software testing that involves dynamically testingsoftware without a fixed plan, using the results of previous tests to determine subsequent tests.
- It is a disciplined approach that finds unknown unknowns and helps testers examine software from different perspectives to uncover more bugs. Tests are performances rather than fixed artifacts.
- Exploratory testing requires testers to be able to strategically choose and defend their test approaches, explain what they have tested, and determine when they are done testing rather than just finding bugs randomly. It is a more systematic approach than unplanned testing.
5 myths and realities
The document discusses 5 myths about software testing and what it takes to become a great tester. The myths are that software testing does not require passion, challenge, programming skills, analysis, or offer career growth opportunities. However, software testing requires broad technical skills, deep domain knowledge, problem solving abilities, programming, analytical reasoning, and innovative thinking. Becoming a great tester also requires soft skills, the right attitude, passion for technology, and a willingness to continually learn and adapt to changes. The document provides a roadmap for testers to define career plans, leverage social abilities, and remain determined and innovative to succeed in software testing roles.
[Hoang nguyen] The Psychology in Software Testing
The document discusses the psychology of software testing and testers. It addresses cognitive biases that testers may face, such as confirmation bias, cognitive dissonance, and belief bias, as well as cognitive illusions and finding patterns where none exist. The document also presents statistics on the personality types of 306 testers, with 46% being melancholic, 33% phlegmatic, 14% choleric, and 7% sanguine. Hiring suggestions are made based on matching personality types to the skills needed for testing.
Imrul: Context Driven Testing
Context-driven testing is a software testing methodology that focuses on tailoring testing objectives, techniques, and documentation to the specific context of each project situation. The context includes factors like the people involved, goals, resources, and timelines. The key principles of context-driven testing are that practices depend on context, there are no universally best practices, collaboration is important, projects evolve unpredictably, products must solve problems, testing is challenging intellectual work, and effective testing requires judgment tailored to each context. Context-driven testing contrasts with approaches that focus first on standardized practices or documentation over project-specific needs.
Software Analytics: The Dark Side and the Test Side
This document summarizes a keynote presentation on software testing and analytics. It discusses how common beliefs that testing takes up 50% of development time are not supported by recent software analytics research. This research observed 416 software engineers and found that actual time spent on testing ranged from 25-75%, with many developers overestimating their testing activities. It also found that testing practices like test-driven development and regular test execution are not widely followed in practice. Software analytics can help developers better understand their own testing behaviors.
Fact or Fiction? What Software Analytics Can Do For Us
This document summarizes findings from software analytics research on developer testing practices. It finds that developers overestimate the amount of time spent on testing, with most spending 25-75% of their time on test code compared to an estimated 50%. Tests are rarely executed in IDEs, with only 20% failing, compared to 60% failing in IDEs. Most projects have test code but over half of developers did not interact with tests. Testing is crucial for continuous integration, with 98% of projects failing builds when tests fail. The research helps developers understand their own behaviors and identifies challenges for improving tools and education.
Software Analytics
- Dr. Andy Zaidman is an associate professor in software engineering at Delft University of Technology who studies software analytics.
- His research has found that developers often overestimate the amount of time spent on testing activities like writing test code compared to actual measurements, with testing found to account for 28-72% of time rather than the commonly assumed 50%.
- Metrics and analytics can help developers better understand their development behaviors, but intuition also provides value by detecting code smells that may be more urgent to address or easier to understand problems with than metric-based detections alone.
Testing in the Wild
This document discusses strategies for handling non-ideal testing situations when adopting agile practices. It addresses problems like lack of test automation, test data issues, legacy reporting needs, geographic distribution of teams, and separation of testers and programmers. The proposed solutions generally involve starting small, using technology to facilitate remote collaboration, targeting important information in reports, and developing relationships between team members.
Testing Intelligence
Presentation created by me on \'Testing Intelligence\' on the grounds of QA Blog written by Mr. Joel Montvelisky
ATD2K16
The document discusses the Context Driven School of Testing. It outlines the seven basic principles of the Context Driven School, which focus on the importance of context, the unpredictability of projects, solving problems rather than following practices, testing as an intellectual process, and cooperation throughout projects. It also briefly describes five schools of testing - Analytical, Factory, Quality Assurance, Context Driven, and Agile - and notes that the Context Driven community values challenges and debate. The document emphasizes finding community and understanding different perspectives to improve testing practices.
Why all deadlines are bad for quality
In this article I will explore why I think that deadlines should never be communicated to the development teams, and why all deadlines are basically meaningless anyway.
Testing concepts ppt
Testing involves finding errors in a program. The goal is to assume a program contains errors and test to find as many as possible. Different testing techniques include white box testing by developers and black box testing by testers. Testing levels include unit, integration, system, and user acceptance testing. Developers and testers have different goals - developers want code to work while testers try to make code fail. Good development practices from a tester's view include doing own acceptance tests, fixing bugs, writing helpful error messages, and not artificially adding bugs. Good relationships between project managers, developers and testers help ensure quality.
Designing Teams for Emerging Challenges
The document discusses designing teams and processes to adapt to changing needs. It recommends structuring teams so members can work within their competencies and across projects fluidly with clear roles and expectations. The design process should support the team and their work, and be flexible enough to change with team, organization, and project needs. An effective team culture builds an environment where members feel free to be themselves, voice opinions, and feel supported.
UX, ethnography and possibilities: for Libraries, Museums and Archives
1) The document discusses how the University of York Library has used various user experience (UX) techniques like ethnographic observation and interviews to better understand user needs and behaviors.
2) Some changes implemented based on UX findings include installing hot water taps, changing hours, and adding blankets - aimed at improving the small details of user experience.
3) The presentation encourages other libraries, archives and museums to try incorporating UX techniques like behavioral mapping and cognitive interviews to inform design changes that enhance services for users.
More Related Content
What's hot
Defining Test Competence
In this article I explore the concept of test competence, and how it is connected to complex problems.
Becoming a software testing expert
This document discusses becoming a software testing expert. It provides 10 claims about testing and asks the reader to analyze them. It also presents 3 "expert challenges" involving testing scenarios and asks the reader to provide the expected results or test cases. The document emphasizes that expertise is situational and depends on factors like one's technical knowledge and ability to explain their methodology. It suggests drivers for developing expertise like practicing, gathering resources, and associating with other experts. The overall document provides guidance and questions to help the reader assess and improve their expertise in software testing.
Shrini Kulkarni - Software Metrics - So Simple, Yet So Dangerous
EuroSTAR Software Testing Conference 2009 presentation on Software Metrics - So Simple, Yet So Dangerous by Shrini Kulkarni. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Comm1
The document discusses best practices for conducting software reviews. It notes that reviews, inspections, and walkthroughs are often used interchangeably but mean different things. It recommends adopting written procedures for reviews and focusing on the product, not the producer, during reviews. Reviews should be planned in advance and have 3 to 7 participants with relevant skills and knowledge. The purpose of reviews is to find defects, so discussions should focus on that rather than fixing defects or criticizing style over substance.
Exploratory testing workshop
The document summarizes an exploratory testing workshop. It discusses exploratory testing approaches, common traps testers fall into, and provides tips for effective exploratory testing. As an exercise, participants are asked to use exploratory testing to find issues with a Tilted Twister device within 20 minutes. Key problems identified include inability to detect color differences, motor arm overshooting, difficulty turning it on, calibration cube being too big, and taking too long to solve with memory issues. The debrief discusses the testing process and importance of the tester mindset in exploratory and automated testing.
Rik Teuben - Many Can Quarrel, Fewer Can Argue
EuroSTAR Software Testing Conference 2009 presentation on Many Can Quarrel, Fewer Can Argue by Rik Teuben. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Rapid Software Testing
This document provides an overview and introduction to the Rapid Software Testing course. It acknowledges those who contributed to developing the course material. The document outlines some assumptions about the audience for the course, including that attendees test software and want to improve their testing process. It presents the primary goal of the course as teaching how to test under uncertainty and with scrutiny. Key themes of Rapid Testing are also summarized, including putting the tester's mind at the center and considering cost versus value in testing activities.
Exploratory Testing Explained
Exploratory testing is an approach to testing that emphasizes the freedom and responsibility of testers to continually optimize the value of their work. It is the process of three mutually supportive activities done in parallel: learning, test design, and test execution. With skill and practice, exploratory testers typically uncover an order of magnitude more problems than when the same amount of effort is spent on procedurally scripted testing. All testers conduct exploratory testing in one way or another, but few know how to do it systematically to obtain the greatest benefits. Even fewer can articulate the process. Jon Bach looks at specific heuristics and techniques of exploratory testing that will help you get the most from this highly productive approach. Jon focuses on the skills and dynamics of exploratory testing, and how it can be combined with scripted approaches.
Santa Barbara Agile: Exploratory Testing Explained and Experienced
Exploratory Testing Explained and Experienced
- Exploratory testing is an approach to software testing that involves dynamically testingsoftware without a fixed plan, using the results of previous tests to determine subsequent tests.
- It is a disciplined approach that finds unknown unknowns and helps testers examine software from different perspectives to uncover more bugs. Tests are performances rather than fixed artifacts.
- Exploratory testing requires testers to be able to strategically choose and defend their test approaches, explain what they have tested, and determine when they are done testing rather than just finding bugs randomly. It is a more systematic approach than unplanned testing.
5 myths and realities
The document discusses 5 myths about software testing and what it takes to become a great tester. The myths are that software testing does not require passion, challenge, programming skills, analysis, or offer career growth opportunities. However, software testing requires broad technical skills, deep domain knowledge, problem solving abilities, programming, analytical reasoning, and innovative thinking. Becoming a great tester also requires soft skills, the right attitude, passion for technology, and a willingness to continually learn and adapt to changes. The document provides a roadmap for testers to define career plans, leverage social abilities, and remain determined and innovative to succeed in software testing roles.
[Hoang nguyen] The Psychology in Software Testing
The document discusses the psychology of software testing and testers. It addresses cognitive biases that testers may face, such as confirmation bias, cognitive dissonance, and belief bias, as well as cognitive illusions and finding patterns where none exist. The document also presents statistics on the personality types of 306 testers, with 46% being melancholic, 33% phlegmatic, 14% choleric, and 7% sanguine. Hiring suggestions are made based on matching personality types to the skills needed for testing.
Imrul: Context Driven Testing
Context-driven testing is a software testing methodology that focuses on tailoring testing objectives, techniques, and documentation to the specific context of each project situation. The context includes factors like the people involved, goals, resources, and timelines. The key principles of context-driven testing are that practices depend on context, there are no universally best practices, collaboration is important, projects evolve unpredictably, products must solve problems, testing is challenging intellectual work, and effective testing requires judgment tailored to each context. Context-driven testing contrasts with approaches that focus first on standardized practices or documentation over project-specific needs.
Software Analytics: The Dark Side and the Test Side
This document summarizes a keynote presentation on software testing and analytics. It discusses how common beliefs that testing takes up 50% of development time are not supported by recent software analytics research. This research observed 416 software engineers and found that actual time spent on testing ranged from 25-75%, with many developers overestimating their testing activities. It also found that testing practices like test-driven development and regular test execution are not widely followed in practice. Software analytics can help developers better understand their own testing behaviors.
Fact or Fiction? What Software Analytics Can Do For Us
This document summarizes findings from software analytics research on developer testing practices. It finds that developers overestimate the amount of time spent on testing, with most spending 25-75% of their time on test code compared to an estimated 50%. Tests are rarely executed in IDEs, with only 20% failing, compared to 60% failing in IDEs. Most projects have test code but over half of developers did not interact with tests. Testing is crucial for continuous integration, with 98% of projects failing builds when tests fail. The research helps developers understand their own behaviors and identifies challenges for improving tools and education.
Software Analytics
- Dr. Andy Zaidman is an associate professor in software engineering at Delft University of Technology who studies software analytics.
- His research has found that developers often overestimate the amount of time spent on testing activities like writing test code compared to actual measurements, with testing found to account for 28-72% of time rather than the commonly assumed 50%.
- Metrics and analytics can help developers better understand their development behaviors, but intuition also provides value by detecting code smells that may be more urgent to address or easier to understand problems with than metric-based detections alone.
Testing in the Wild
This document discusses strategies for handling non-ideal testing situations when adopting agile practices. It addresses problems like lack of test automation, test data issues, legacy reporting needs, geographic distribution of teams, and separation of testers and programmers. The proposed solutions generally involve starting small, using technology to facilitate remote collaboration, targeting important information in reports, and developing relationships between team members.
Testing Intelligence
Presentation created by me on \'Testing Intelligence\' on the grounds of QA Blog written by Mr. Joel Montvelisky
ATD2K16
The document discusses the Context Driven School of Testing. It outlines the seven basic principles of the Context Driven School, which focus on the importance of context, the unpredictability of projects, solving problems rather than following practices, testing as an intellectual process, and cooperation throughout projects. It also briefly describes five schools of testing - Analytical, Factory, Quality Assurance, Context Driven, and Agile - and notes that the Context Driven community values challenges and debate. The document emphasizes finding community and understanding different perspectives to improve testing practices.
Why all deadlines are bad for quality
In this article I will explore why I think that deadlines should never be communicated to the development teams, and why all deadlines are basically meaningless anyway.
What's hot (19)
Shrini Kulkarni - Software Metrics - So Simple, Yet So Dangerous
Shrini Kulkarni - Software Metrics - So Simple, Yet So Dangerous
Santa Barbara Agile: Exploratory Testing Explained and Experienced
Santa Barbara Agile: Exploratory Testing Explained and Experienced
Software Analytics: The Dark Side and the Test Side
Software Analytics: The Dark Side and the Test Side
Fact or Fiction? What Software Analytics Can Do For Us
Fact or Fiction? What Software Analytics Can Do For Us
Viewers also liked
Testing concepts ppt
Testing involves finding errors in a program. The goal is to assume a program contains errors and test to find as many as possible. Different testing techniques include white box testing by developers and black box testing by testers. Testing levels include unit, integration, system, and user acceptance testing. Developers and testers have different goals - developers want code to work while testers try to make code fail. Good development practices from a tester's view include doing own acceptance tests, fixing bugs, writing helpful error messages, and not artificially adding bugs. Good relationships between project managers, developers and testers help ensure quality.
Designing Teams for Emerging Challenges
The document discusses designing teams and processes to adapt to changing needs. It recommends structuring teams so members can work within their competencies and across projects fluidly with clear roles and expectations. The design process should support the team and their work, and be flexible enough to change with team, organization, and project needs. An effective team culture builds an environment where members feel free to be themselves, voice opinions, and feel supported.
UX, ethnography and possibilities: for Libraries, Museums and Archives
1) The document discusses how the University of York Library has used various user experience (UX) techniques like ethnographic observation and interviews to better understand user needs and behaviors.
2) Some changes implemented based on UX findings include installing hot water taps, changing hours, and adding blankets - aimed at improving the small details of user experience.
3) The presentation encourages other libraries, archives and museums to try incorporating UX techniques like behavioral mapping and cognitive interviews to inform design changes that enhance services for users.
Visual Design with Data
An immersive workshop at General Assembly, SF. I typically teach this workshop at General Assembly, San Francisco. To see a list of my upcoming classes, visit https://generalassemb.ly/instructors/seth-familian/4813
I also teach this workshop as a private lunch-and-learn or half-day immersive session for corporate clients. To learn more about pricing and availability, please contact me at http://familian1.com
3 Things Every Sales Team Needs to Be Thinking About in 2017
Thinking about your sales team's goals for 2017? Drift's VP of Sales shares 3 things you can do to improve conversion rates and drive more revenue.
Read the full story on the Drift blog here: http://blog.drift.com/sales-team-tips
How to Become a Thought Leader in Your Niche
Are bloggers thought leaders? Here are some tips on how you can become one. Provide great value, put awesome content out there on a regular basis, and help others.
Viewers also liked (6)
UX, ethnography and possibilities: for Libraries, Museums and Archives
UX, ethnography and possibilities: for Libraries, Museums and Archives
3 Things Every Sales Team Needs to Be Thinking About in 2017
3 Things Every Sales Team Needs to Be Thinking About in 2017
Similar to Software testing _mod_9
Ste skills
The document outlines the key skills required of a software tester, including analytical and logical thinking, the ability to envision business situations, intellectual curiosity and creativity, a global approach to consider multiple stakeholders, critical thinking, applying fundamental knowledge, continuing to learn, planning and time management, effective communication, and respect for truth and integrity. It provides details on each skill area and emphasizes the importance of analysis, envisioning complex problems, asking questions, dealing with complex systems, impartial thought, applying knowledge to test situations, adapting to change, thorough planning, clear communication, and examining software with focus and integrity.
Michael Bolton - Two Futures of Software Testing
EuroSTAR Software Testing Conference 2008 presentation on Two Futures of Software Testing by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Rekard Edgren - Curing Our Binary Disease - EuroSTAR 2012
EuroSTAR Software Testing Conference 2012 presentation on Curing Our Binary Disease by Rekard Edgren.
See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
A Happy Marriage between Context-Driven and Agile
The document discusses how to achieve a happy marriage between context-driven and agile approaches to software development and testing. It advocates for involving testers from the start of projects and having them work closely with developers as part of integrated teams. The document also provides advice on skills needed for testers, such as domain knowledge and a willingness to learn, and emphasizes pairing with other roles like developers to facilitate collaboration and knowledge sharing.
Usability Testing
The document discusses usability testing and its key aspects. It defines usability testing as employing techniques to collect empirical data by observing representative end users perform realistic tasks on a product. There are different types of usability tests - exploratory, assessment, and validation - conducted at various stages of product development to evaluate usability. An effective moderator is important for a successful test, requiring skills like rapport building and objectivity. Tests involve representative tasks, questionnaires, and debriefing to understand user difficulties and identify areas for improvement.
Software testing-in-gurgaon
Basically this slid will help to Learn software quality testing on scratch level.
Software testing is the quality measures conducted to provide stakeholders with information about the quality of the product or service. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. It is an important part of the entire Software Development ensuring that the functionalities of the system are tested to the finest and assures the quality, correctness and completeness of the product. Software testing, depending on the testing method employed, can be implemented at any time in the development process.
Stages of testing:
o Test planning
o Test Analysis
o Test verification & Construction
o Test execution
o Defect tracking and management
o Quality Analysis Bug tracking
o Report
o Final testing & implementation
Exploratory Testing, A Guide Towards Better Test Coverage.pdf
As this type of testing doesn’t require any extensive test planning, the testing can even be done when requirement documents are not easily available.
Tech Talk #4 : Tester : Job finds resources - Trần Lệ Khuyên
The document provides information about software testing as a job or career. It defines a software tester's job as finding bugs in a software system to evaluate whether it meets technical and business requirements. It notes that testers help improve product quality to meet customer needs. Additionally, it lists reasons one may choose to become a tester, such as it being a stable job with growth opportunities, good income, and a chance to work with new technologies. The document outlines challenges testers face like working under pressure and dealing with complex systems, and lists desirable characteristics for testers like being creative, good communication skills, and able to work as part of a team.
Get things done : pragmatic project management
The document provides pragmatic advice for project management. It discusses challenges project managers may face including stakeholders, timelines, and fear, uncertainty, and doubt. It recommends communicating frequently with stakeholders, organizing work with tools like planning software and ticketing systems, addressing problems promptly through prototypes, and taking ownership of assignments to help ensure project success.
Effective Testing fo Startups
This document provides an introduction to software testing for startups. It discusses that testing early in the development cycle results in faster development, better software, and enhanced investment appeal. It recommends creating test cases based on functional specifications and menus. The document outlines six principles of testing, including that you cannot test every scenario and defects congregate in particular areas. It recommends testing frequently with both developers and testers working closely together.
How To Ask The Right Questions
This document provides guidance on how to effectively ask questions to gather user feedback. It discusses identifying goals and assumptions, engaging the right participants, formulating good open-ended questions, using follow-up questions and considering question format. Effective listening is also covered, including remaining neutral, engaging with participants and allowing silence. The overall aim is to facilitate discussions that prepare teams for gathering insightful client and user feedback.
Quality, Testing & Agile Methodologies
In this article I outline my thoughts on why Agile methodologies are critical to delivering value in complex product development.
Ppt 1 TEST MANAGEMENT
This document discusses various topics related to test management. It covers independent and integrated testing, the roles of test leaders and testers, defining the skills test staff need, test plans and estimates, configuration management, risk and testing, and incident management. The document provides information on each of these topics in 1-3 paragraphs per section to outline the key aspects and considerations for test management.
Qualitative research techniques
The document discusses various qualitative research techniques including observation, focus groups, depth interviews, and projective techniques. Qualitative research involves observational techniques or unstructured questioning to understand behaviors, opinions, and motivations. Focus groups involve moderated group discussions with 8-12 screened participants to understand perceptions and generate ideas. Projective techniques use ambiguous stimuli to indirectly reveal respondents' views through activities like word associations, sentence completions, and cartoon interpretations. While qualitative techniques are suitable in theory for Asia-Pacific countries, cultural factors like preference for numbers over opinions and reluctance to discuss sensitive issues pose challenges to their practical use in most Asian markets.
Experiences with Semi-Scripted Exploratory Testing
The document discusses experiences with combining semi-scripted and exploratory testing approaches. It describes a case where short timelines and complex environments typically led to traditional scripted testing. A semi-scripted approach was used, involving feature walkthroughs, brainstorming test ideas, and execution with some predefined setup but freedom for exploratory testing. This transitioned teams to value investigative testing over scripted test cases and numbers, finding more issues and providing better information to stakeholders.
Testing trapeze-2014-april
This document contains summaries of several articles in the April 2014 issue of Testing Trapeze magazine. It discusses common blind spots that can negatively impact software testers' work, including an obsession with functionality over other quality criteria, not taking time to properly plan tests, failing to notice important details, and letting confirmation bias from requirements limit testing. The editor's introduction welcomes readers and contributors to the second issue.
fundamentals of testing (Management)
This document discusses test management and organizing testing efforts. It covers establishing independent testing teams and the benefits of independence. It describes typical roles for test leaders and testers, including their responsibilities in planning, designing, and executing tests. It also outlines important skills for test staff, such as understanding the application domain, technology, and testing practices. Finally, it notes that the types of defects found change over time as testing improves, requiring teams to shift their focus to new risk areas.
Software Testing 2/5
Damian Gordon was a Dutch computer scientist born in 1930 in Rotterdam who received the 1972 Turing Award. He developed several programming language principles including that testing shows presence of bugs but not absence, exhaustive testing is impossible, early testing is important, and defects often cluster in small areas of code. He stressed the importance of risk analysis, test objectives, and regularly updating test cases to find new issues rather than relying on the same cases. Testing approaches must also be tailored to contexts like safety-critical systems versus ecommerce.
Michał Stryjak, Poznaj Context-Driven Testing
Prezentacja z ósmego spotkania z cyklu Quality Meetup.
Autor: Michał Stryjak (QA Manager, PiLab SA)
Przez wiele lat ludzie starali się wskazać niezawodne podejście do testowania. Nasz Gość uczestniczył w wielu dyskusjach dotyczących wyższości jednej metody nad drugą, które zwykle sprowadzały się do poszukiwania odpowiedzi na pytanie, czy jakaś konkretna praktyka zmieni świat testów na zawsze.
Już wiele lat temu Cem Kaner zauważył, że najlepsze praktyki głoszone przez jego kolegów wykładowców nie zawsze sprawdzają się dobrze w rzeczywistości. Często obserwował jak procesy i narzędzia stosowane z powodzeniem, np. w startupach, nie sprawdzają się w bankach lub branży medycznej (i vice versa). Z biegiem lat Cem doszedł do wniosku, że coraz więcej osób ma podobne spostrzeżenia dotyczące najlepszych praktyk. Ludzie podzielający jego poglądy (najbardziej znani to James Bach i Bret Pettichord) twierdzą, że aby móc testować dobrze, najpierw trzeba uwzględnić i przeanalizować kontekst. Ich idee znalazły odwzorowanie w siedmiu zasadach, które dzisiaj stanowią podstawę podejścia Context-Driven Testing (CDT). Na spotkaniu Michał opowie nam o podstawach CDT oraz podzieli się pomysłami, jak można wdrażać wspomniane siedem zasad w życie.
Develop your inner tester
This document provides guidance on developing a tester mindset and strategies for effective testing. It discusses developing an analytical eye for detail and skeptical approach. It emphasizes avoiding confirmation bias by testing to disprove hypotheses rather than just verify them. It also stresses generating new testing ideas by considering different customer models and perspectives. Finally, it discusses prioritizing testing based on risk factors like new features, complexity, critical functions and upstream/downstream dependencies. The overall message is the importance of strategic and logical thinking to structure effective testing.
Similar to Software testing _mod_9 (20)
Rekard Edgren - Curing Our Binary Disease - EuroSTAR 2012
Rekard Edgren - Curing Our Binary Disease - EuroSTAR 2012
Exploratory Testing, A Guide Towards Better Test Coverage.pdf
Exploratory Testing, A Guide Towards Better Test Coverage.pdf
Tech Talk #4 : Tester : Job finds resources - Trần Lệ Khuyên
Tech Talk #4 : Tester : Job finds resources - Trần Lệ Khuyên
Experiences with Semi-Scripted Exploratory Testing
Experiences with Semi-Scripted Exploratory Testing
Recently uploaded
Securing your Kubernetes cluster_ a step-by-step guide to success !
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
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
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
GridMate - End to end testing is a critical piece to ensure quality and avoid...
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
UiPath Test Automation using UiPath Test Suite series, part 5
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.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
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:
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Pushing the limits of ePRTC: 100ns holdover for 100 days
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.
Mind map of terminologies used in context of Generative AI
Mind map of common terms used in context of Generative AI.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentationsLarge Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications.
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Communications Mining Series - Zero to Hero - Session 1
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Recently uploaded (20)
Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
GridMate - End to end testing is a critical piece to ensure quality and avoid...
GridMate - End to end testing is a critical piece to ensure quality and avoid...
UiPath Test Automation using UiPath Test Suite series, part 5
UiPath Test Automation using UiPath Test Suite series, part 5
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Elizabeth Buie - Older adults: Are we really designing for our future selves?
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
Monitoring Java Application Security with JDK Tools and JFR Events
Monitoring Java Application Security with JDK Tools and JFR Events
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
Software testing _mod_9
- 2. What’s Special about a Tester’s Brain?
- 19. Thank You….. Any Questions ???
Editor's Notes
- (from Cambridge International Dictionary of English) conjecture ANTAKELSE / HYPOTESE verb, noun (to form) a guess or judgment, based on the appearance of a situation rather than on proof We'll never know exactly how she died. We can only conjecture. [I] He conjectured that the company would soon be in financial difficulties. [+ that clause] There's been a lot of conjecture in the papers recently about the royal marriage. [U] It's pure conjecture. Nobody knows the facts. [U] conjectural adjective refute “BEVIS” verb [T] FORMAL OR LAW to say or prove that (a person, statement, opinion, etc.) is wrong or false to refute a person/theory/argument The barrister used new evidence to refute the charges and clear the defendant. refutation noun [C/U] FORMAL OR LAW
- (from Cambridge International Dictionary of English) conjecture verb, noun (to form) a guess or judgment, based on the appearance of a situation rather than on proof We'll never know exactly how she died. We can only conjecture. [I] He conjectured that the company would soon be in financial difficulties. [+ that clause] There's been a lot of conjecture in the papers recently about the royal marriage. [U] It's pure conjecture. Nobody knows the facts. [U] conjectural adjective refute verb [T] FORMAL OR LAW to say or prove that (a person, statement, opinion, etc.) is wrong or false to refute a person/theory/argument The barrister used new evidence to refute the charges and clear the defendant. refutation noun [C/U] FORMAL OR LAW
- Testing is done in context Rather than looking for The One True Way to run a test group, we should recognize that the testing group is a service organization and that its work is done in a context. Life cycles, testing group missions, testing techniques must fit within the overall organization. We should look at / for relevant factors (perform a requirements analysis ) to guide our decisions.