EuroSTAR Software Testing Conference 2013 presentation on Alternative Paths for Self-Education in Software Testing by Markus Gartner . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Vipul Kocher - Software Testing, A Framework Based ApproachTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Software Testing, A Framework Based Approach by Vipul Kocher. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
New Model Testing: A New Test Process and ToolTEST Huddle
Paul Gerrard presented a new test process and tool called Cervaya that combines elements of structured and exploratory testing. The process involves testers surveying features using Cervaya to iteratively build system models and test plans. This shifts testing earlier in the development process. Cervaya logs tester activity, supports real-time collaboration, and could generate documentation. The goal is to make testing more aligned with agile and continuous delivery approaches. Gerrard invited collaboration on further developing Cervaya.
Doron Reuveni - The Mobile App Quality Challenge - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on The Mobile App Quality Challenge by Doron Reuveni. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Practical Test Strategy Using HeuristicsTEST Huddle
Key Takeaways
- See what makes a good test strategy
- Learn how to make a thorough test strategy
- Identify what is the ‘Heuristic Test Strategy Model’ is
- Develop a solid test strategy that fits fast
- Discover how diversification can help you to create a test strategy
Sharing some test heuristics that you can use in different apps your testing!
For more presentation slides related to testing and automation, visit us at qeisthenewqa.com
Exploratory testing is an approach that emphasizes freedom and responsibility of individual testers in a process where continuous learning, test design, and execution occur simultaneously. It is a disciplined, planned, and controlled form of testing that focuses on continuous learning. Research has shown there is no significant difference in results between exploratory testing and preplanned test cases, but exploratory testing requires significantly less effort overall. Effective exploratory testing requires skills like making models, keeping an open mind, and risk-based testing approaches. Both the strengths and potential blind spots of exploratory testing are discussed.
This document provides an overview of exploratory testing techniques. It discusses that exploratory testing involves simultaneous learning, test design, and test execution. Exploratory testing is tester-centric and focuses on problem solving strategies like heuristics rather than scripts. The document dispels some myths about exploratory testing, including that it is unstructured and cannot involve documentation. It provides examples of how documents can be used for reflection, information sharing, and reporting in exploratory testing.
Tips for Writing Better Charters for Exploratory Testing Sessions by Michael...TEST Huddle
We will look at some common pitfalls encountered when chartering your testing for session-based exploratory testing. After a brief overview of the session-based test management process we will jump into specific practices and techniques to help you and the rest of your team achieve better coverage and find better bugs. A presentation for the EuroSTAR Software Testing Community from September 2012.
Vipul Kocher - Software Testing, A Framework Based ApproachTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Software Testing, A Framework Based Approach by Vipul Kocher. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
New Model Testing: A New Test Process and ToolTEST Huddle
Paul Gerrard presented a new test process and tool called Cervaya that combines elements of structured and exploratory testing. The process involves testers surveying features using Cervaya to iteratively build system models and test plans. This shifts testing earlier in the development process. Cervaya logs tester activity, supports real-time collaboration, and could generate documentation. The goal is to make testing more aligned with agile and continuous delivery approaches. Gerrard invited collaboration on further developing Cervaya.
Doron Reuveni - The Mobile App Quality Challenge - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on The Mobile App Quality Challenge by Doron Reuveni. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Practical Test Strategy Using HeuristicsTEST Huddle
Key Takeaways
- See what makes a good test strategy
- Learn how to make a thorough test strategy
- Identify what is the ‘Heuristic Test Strategy Model’ is
- Develop a solid test strategy that fits fast
- Discover how diversification can help you to create a test strategy
Sharing some test heuristics that you can use in different apps your testing!
For more presentation slides related to testing and automation, visit us at qeisthenewqa.com
Exploratory testing is an approach that emphasizes freedom and responsibility of individual testers in a process where continuous learning, test design, and execution occur simultaneously. It is a disciplined, planned, and controlled form of testing that focuses on continuous learning. Research has shown there is no significant difference in results between exploratory testing and preplanned test cases, but exploratory testing requires significantly less effort overall. Effective exploratory testing requires skills like making models, keeping an open mind, and risk-based testing approaches. Both the strengths and potential blind spots of exploratory testing are discussed.
This document provides an overview of exploratory testing techniques. It discusses that exploratory testing involves simultaneous learning, test design, and test execution. Exploratory testing is tester-centric and focuses on problem solving strategies like heuristics rather than scripts. The document dispels some myths about exploratory testing, including that it is unstructured and cannot involve documentation. It provides examples of how documents can be used for reflection, information sharing, and reporting in exploratory testing.
Tips for Writing Better Charters for Exploratory Testing Sessions by Michael...TEST Huddle
We will look at some common pitfalls encountered when chartering your testing for session-based exploratory testing. After a brief overview of the session-based test management process we will jump into specific practices and techniques to help you and the rest of your team achieve better coverage and find better bugs. A presentation for the EuroSTAR Software Testing Community from September 2012.
Geoff Thompson - Why Do We Bother With Test StrategiesTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Why Do We Bother With Test Strategies by Geoff Thompson. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
This document discusses different "flavors" of exploratory testing that were tried by a CMMI level 5 software company. It describes freestyle exploratory testing, session-based exploratory testing, testing tours, bug hunts, and a general functionality and stability test procedure inspired by Microsoft. It also discusses challenges faced in implementing exploratory testing and how the company addressed these challenges by developing a hybrid approach combining elements of different flavors.
The document provides a template for an exploratory test charter. The charter includes sections for introduction, context, execution, and reporting. The context section describes the test environment, coverage area, and tasks. The execution section is for documenting testing notes, output files, issues, and bugs found. The reporting section summarizes the time spent on design, execution, issue investigation, and other phases of the exploratory test.
Growing a Company Test Community: Roles and Paths for TestersTEST Huddle
Over the past three years, our company’s test team has grown from three lonesome testers to a community of nine – with more planned. Since we don’t see testers as “click monkeys”, but as valuable and integrated project members who bring a specific skill set to the table, it’s important for us to choose testers well and to train them in various areas so that they can contribute, grow and see their own career path within testing.
To structure to our internal tester training program, we have been developing role descriptions, education paths and career options for our testers, which I’d like to share with you in this webinar.
View webinar - https://huddle.eurostarsoftwaretesting.com/resource/webinar/growing-company-test-community-roles-paths-testers/
This document provides an overview of exploratory testing. It discusses how exploratory testing involves simultaneous test design, execution, and learning. Exploratory testing is tester-centric and relies on heuristics. The tester explores the product by playing around with different features and inputs, looking for anything unusual. Their testing is guided by mental engagement techniques like alternation and branching. Exploratory testing can involve different levels of documentation and formality. It is focused on revealing new information rather than just confirming existing knowledge.
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. James Bach looks at specific heuristics and techniques of exploratory testing that will help you get the most from this highly productive approach. James focuses on the skills and dynamics of exploratory testing, and how it can be combined with scripted approaches.
My talk at #TestConVilnius 19.10.2017 about what is exploratory testing (ET), how can you make it work and what is there in the future of exploratory testing: test management tool support, testing with tools, AI support, ET as standard way of testing in especially agile and DevOps projects
EuroSTAR Software Testing Conference 2009 presentation on Incremental Scenario Testing by Mattias Ratert. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Fredrik Rydberg - Can Exploratory Testing Save Lives - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Can Exploratory Testing Save Lives by Fredrik Rydberg. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
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.
This document discusses exploratory testing and defines it as "Any testing to the extent that the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests." It describes how all testers do some exploratory testing. Exploratory testers rely on a variety of knowledge, including knowledge of specific domains, risks, and testing techniques. Exploratory testing can differ based on a tester's personality and experiences. Questioning strategies like the Phoenix Checklist can help exploratory testers generate effective questions to test software.
Julian Harty - Alternatives To Testing - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on "Presentation Title" by "Speaker Name". See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Brief introduction to Session-Based Test Management and to how Exploratory Testing is understood and approached under the influence of the Context-Driven Testing movement.
Gustav Olsson - Agile - Common Sense with a New Name Tag revisedTEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Agile - Common Sense with a New Name Tag revised by Gustav Olsson. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
The document discusses software testing objectives, principles, techniques and processes. It covers black-box and white-box testing, unit and integration testing, and challenges of object-oriented testing. Testing aims to find bugs but can never prove their absence. Exhaustive testing is impossible so testing must be planned and systematic. Frameworks like xUnit can help automate unit testing.
The document discusses exploratory testing and Keri Smith. It provides an overview of exploratory testing, noting that it emphasizes personal freedom and responsibility of testers to continually optimize testing. It also discusses Keri Smith's work in conceptual art and guided journals that encourage observing the world like artists and scientists.
Tafline Murnane - The Carrot or The Whip-What Motivates Testers? - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on The Carrot or The Whip-What Motivates Testers? by Tafline Murnane. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
dbg Agile Testing Presentation, demonstrating the use of Test Charters, Exploratory Testing, Session Based Testing and Testing Tours. With thanks to James Bach, Lisa Crispin, Janet Gregory and James Whittaker
Using Functional ,Test Automation to Prevent Defects from Escaping the Develo...TEST Huddle
This document discusses using functional test automation to prevent defects from escaping the development phase. It recommends automating acceptance tests during development to catch bugs early from the user perspective. The process involves preparing for automation by exploring and selecting test candidates, automating the tests as close to development as possible, and repeating the automation across areas, platforms and versions to prevent regression bugs. Continuous integration and handling test errors are also suggested to provide feedback and react to issues identified through automation. The overall goal is to shift testing left in the development cycle through early and frequent automation from a user perspective.
Alternative Paths For Self Education In Software Testing WebinarMarkus Gärtner
This document discusses alternative paths for self-education in software testing, including books, online courses, challenges, dojos, and weekend testing groups. It provides summaries and links for resources on rapid software testing, black-box software testing, buccaneer scholars, testing dojos and challenges, and the Miagi-Do school of software testing. These options allow software testers to continue learning and improving their skills on their own through reading, online materials, collaboration with others, and deliberate practice.
Alternative paths for self-education in Software TestingMarkus Gärtner
You are responsible for your own education in software testing. There are different paths for self-education including blogging, writing articles, learning to program, and participating in communities. Education can come from books, online courses, challenges, and dojos that focus on hypothesis through books and courses, or synthesis through practical experience, collaboration and deliberate practice. The best approach is to apply as many styles as possible to improve testing skills.
Geoff Thompson - Why Do We Bother With Test StrategiesTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Why Do We Bother With Test Strategies by Geoff Thompson. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
This document discusses different "flavors" of exploratory testing that were tried by a CMMI level 5 software company. It describes freestyle exploratory testing, session-based exploratory testing, testing tours, bug hunts, and a general functionality and stability test procedure inspired by Microsoft. It also discusses challenges faced in implementing exploratory testing and how the company addressed these challenges by developing a hybrid approach combining elements of different flavors.
The document provides a template for an exploratory test charter. The charter includes sections for introduction, context, execution, and reporting. The context section describes the test environment, coverage area, and tasks. The execution section is for documenting testing notes, output files, issues, and bugs found. The reporting section summarizes the time spent on design, execution, issue investigation, and other phases of the exploratory test.
Growing a Company Test Community: Roles and Paths for TestersTEST Huddle
Over the past three years, our company’s test team has grown from three lonesome testers to a community of nine – with more planned. Since we don’t see testers as “click monkeys”, but as valuable and integrated project members who bring a specific skill set to the table, it’s important for us to choose testers well and to train them in various areas so that they can contribute, grow and see their own career path within testing.
To structure to our internal tester training program, we have been developing role descriptions, education paths and career options for our testers, which I’d like to share with you in this webinar.
View webinar - https://huddle.eurostarsoftwaretesting.com/resource/webinar/growing-company-test-community-roles-paths-testers/
This document provides an overview of exploratory testing. It discusses how exploratory testing involves simultaneous test design, execution, and learning. Exploratory testing is tester-centric and relies on heuristics. The tester explores the product by playing around with different features and inputs, looking for anything unusual. Their testing is guided by mental engagement techniques like alternation and branching. Exploratory testing can involve different levels of documentation and formality. It is focused on revealing new information rather than just confirming existing knowledge.
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. James Bach looks at specific heuristics and techniques of exploratory testing that will help you get the most from this highly productive approach. James focuses on the skills and dynamics of exploratory testing, and how it can be combined with scripted approaches.
My talk at #TestConVilnius 19.10.2017 about what is exploratory testing (ET), how can you make it work and what is there in the future of exploratory testing: test management tool support, testing with tools, AI support, ET as standard way of testing in especially agile and DevOps projects
EuroSTAR Software Testing Conference 2009 presentation on Incremental Scenario Testing by Mattias Ratert. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Fredrik Rydberg - Can Exploratory Testing Save Lives - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Can Exploratory Testing Save Lives by Fredrik Rydberg. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
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.
This document discusses exploratory testing and defines it as "Any testing to the extent that the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests." It describes how all testers do some exploratory testing. Exploratory testers rely on a variety of knowledge, including knowledge of specific domains, risks, and testing techniques. Exploratory testing can differ based on a tester's personality and experiences. Questioning strategies like the Phoenix Checklist can help exploratory testers generate effective questions to test software.
Julian Harty - Alternatives To Testing - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on "Presentation Title" by "Speaker Name". See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Brief introduction to Session-Based Test Management and to how Exploratory Testing is understood and approached under the influence of the Context-Driven Testing movement.
Gustav Olsson - Agile - Common Sense with a New Name Tag revisedTEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Agile - Common Sense with a New Name Tag revised by Gustav Olsson. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
The document discusses software testing objectives, principles, techniques and processes. It covers black-box and white-box testing, unit and integration testing, and challenges of object-oriented testing. Testing aims to find bugs but can never prove their absence. Exhaustive testing is impossible so testing must be planned and systematic. Frameworks like xUnit can help automate unit testing.
The document discusses exploratory testing and Keri Smith. It provides an overview of exploratory testing, noting that it emphasizes personal freedom and responsibility of testers to continually optimize testing. It also discusses Keri Smith's work in conceptual art and guided journals that encourage observing the world like artists and scientists.
Tafline Murnane - The Carrot or The Whip-What Motivates Testers? - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on The Carrot or The Whip-What Motivates Testers? by Tafline Murnane. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
dbg Agile Testing Presentation, demonstrating the use of Test Charters, Exploratory Testing, Session Based Testing and Testing Tours. With thanks to James Bach, Lisa Crispin, Janet Gregory and James Whittaker
Using Functional ,Test Automation to Prevent Defects from Escaping the Develo...TEST Huddle
This document discusses using functional test automation to prevent defects from escaping the development phase. It recommends automating acceptance tests during development to catch bugs early from the user perspective. The process involves preparing for automation by exploring and selecting test candidates, automating the tests as close to development as possible, and repeating the automation across areas, platforms and versions to prevent regression bugs. Continuous integration and handling test errors are also suggested to provide feedback and react to issues identified through automation. The overall goal is to shift testing left in the development cycle through early and frequent automation from a user perspective.
Alternative Paths For Self Education In Software Testing WebinarMarkus Gärtner
This document discusses alternative paths for self-education in software testing, including books, online courses, challenges, dojos, and weekend testing groups. It provides summaries and links for resources on rapid software testing, black-box software testing, buccaneer scholars, testing dojos and challenges, and the Miagi-Do school of software testing. These options allow software testers to continue learning and improving their skills on their own through reading, online materials, collaboration with others, and deliberate practice.
Alternative paths for self-education in Software TestingMarkus Gärtner
You are responsible for your own education in software testing. There are different paths for self-education including blogging, writing articles, learning to program, and participating in communities. Education can come from books, online courses, challenges, and dojos that focus on hypothesis through books and courses, or synthesis through practical experience, collaboration and deliberate practice. The best approach is to apply as many styles as possible to improve testing skills.
Open Assessments and OERs as Enablers in Competency-Based Education Tom Caswell
Call for Demos for the X International UOC UNESCO Chair Seminar
Title: Open Assessments and OERs as Enablers in Competency-Based Education
Tom Caswell, Helix Education
Brandon Muramatsu, MIT
It has been said that if you are measuring seat time rather than competency then you are measuring the wrong end of the student. Competency-based education has received a great deal of attention as a disruptive innovation that promises to raise quality and lower the cost of higher education. EDUCAUSE defines competency-based education (CBE) as awarding academic credit based on mastery of clearly defined competencies. In traditional higher education time is fixed and learning varies, which is why students receive grades at the end of a quarter or semester. Contrast this with competency-based education, where learning is fixed and time varies for each student. But if time varies then how do students know when they are done? Assessments play a central role in CBE because student performance must be measured against set standards.
While there are vast repositories of OERs, relatively few come with assessments to validate knowledge or check for understanding. In this demo we will show the Open Embedded Assessment (OEA) tool developed by MIT and Open Tapestry. Open Assessment complements existing OER efforts with tools to allow instructors to embed assessments in any OER, thereby providing students with a richer learning experience. Faculty can also create shared collections of assessment items with other faculty. We will demonstrate the current state of Open Embedded Assessments as both a formative and a summative tool. We will discuss the opportunities and challenges of a CBE implementation.
As more institutions explore competency-based education the need for an open infrastructure will grow. Helix Education is developing CBE courses using OERs to show what is possible within the Helix platform. Open Embeddable Assessments allow OERs to be leveraged into richer learning environments. Enhanced with Open Embeddable Assessments, these environments can provide valuable information back to students, faculty, and instructional designers. This data can expose gaps and deficiencies in the course -- areas that should be strengthened. And with open content the opportunity for data-driven improvement can be fully realized because the OERs can be legally modified. Together, Open Embeddable Assessments and OERs create a virtuous cycle of continuous improvement that can serve competency-based education well.
This document provides information for students taking an online course on online course design at Boise State University in fall 2010. It outlines important dates and contact information for the instructor, describes the goals and topics to be covered in the course, lists required textbooks and software, and provides the overall schedule and assignments for the semester. Students will apply principles of instructional design to create their own fully developed online course over the course of the semester. Communication will primarily occur via email and online discussion boards.
The Best of Both Worlds: Transforming OpenCourseWare in an age of InteractivityBrandon Muramatsu
The document discusses transforming open courseware by embedding formative assessments directly into course materials. It presents an approach called OpenAssessments.org that allows questions created using IMS Question & Test Interoperability to be embedded anywhere on the web. As a demonstration, the authors have embedded assessments created in MITx courses directly into MIT OpenCourseWare course pages using this approach. They see opportunities to increase reuse of assessments, add functionality for additional question types, and analyze usage through analytics.
Loosely Coupled Teaching with "Web 2.0" Tools (2008)Jared Stein
Scott Leslie and Jared Stein collaborate to present a number of "Web 2.0" tools that may be leveraged to help teachers engage students and meet critical educational goals, including those categorized as 21st century learning.
The document provides an introduction to developer testing from Will Green. It discusses that the author is not an expert in testing like Kent Beck, Ward Cunningham, Martin Fowler, or Robert C. Martin. It presents testing as design where tests specify and design the code. It advocates for test-driven design using the SOLID principles to manage dependencies and create robust, reusable code. It demonstrates test-driven development with a Fibonacci number generator example and discusses test doubles, refactoring, and test smells.
This document discusses rapid eLearning and provides guidance on creating self-paced eLearning content. It defines rapid eLearning as the rapid creation of courseware by subject matter experts with less experience in course development. It emphasizes using templates, short learning modules, and multimedia like images and video. The biggest challenge of rapid eLearning is engagement. The document provides best practices for self-paced content like incorporating activities that apply learning to real work contexts. It also provides examples of interactive content types like decision trees, scenarios, and assessments. Overall, the document aims to equip readers to efficiently create engaging, interactive self-paced eLearning content.
1. The document discusses the history and current state of computerized language testing tools and technologies. It describes how early tools used DOS and authoring programs to provide drills and practice, while newer tools have expanded to use the internet and web technologies like JavaScript, Java, and multimedia plugins.
2. It provides details on several current authoring tools that make it easy to create online language tests and exercises without advanced programming knowledge. These include WebPractest, Hot Potatoes, and templates from various sources.
3. The document concludes that computerized language testing will continue increasing in volume and scope due to growing demands for standardized testing. Controversies may still arise around issues of computerized testing replacing traditional methods
This document summarizes emerging technologies for language testing and assessment using computers and the internet. It discusses the history of computerized language testing from the 1960s to present. Key points covered include the move to web-based testing using tools like JavaScript, authoring programs for creating online tests, and the future of technologies like speech recognition and adaptive testing. The document concludes with an extensive list of resources for online language testing tools, organizations, sample tests, and more.
How Do You Know that Gal Knows Drupal? Towards an Open Source Curriculum and ...Dominik Lukes
An open source curriculum and community-based certification scheme for Drupal was proposed. The proposal involved developing competencies organized around key areas, with maintainers responsible for updates. Training providers could share compatible materials and assess individuals' competencies through portfolios. Certification would be community-based and representatively democratic. Benefits included easier entry for new members, easier hiring for clients, and ensuring the direction of certification. Challenges and a discussion of practical implementation were discussed. Participants were invited to join further discussion on the topic.
This document provides an agenda and overview for a workshop on basic tech skills for language teachers. The agenda includes introductions, discussing email accounts and features, online tools like Google Docs and Google Reader, online identity management, and resources for continued professional development. Examples are given throughout of how these tools can be used for language teaching, collaboration, and personal development. Participants are encouraged to think of ways to apply what they learn to their own teaching.
This document provides an overview of the content and assignments for Week 5 of an education course. It includes discussions on balancing expediency and perfection in teaching, as well as tutorials on using various software programs like Storybird, iMovie, and MovieMaker to create movies or tutorials. Students are assigned to either embed a project created with one of these programs on their website, or to create a tutorial on using an app or web 2.0 tool of their choice. The document also provides additional optional resources for interactive timelines, online book clubs, word clouds, and video cartoons. The instructor provides contact information and encourages students to reach out if they have any technical problems or questions.
1) In 2001, 17 people met to discuss lightweight software development methods, with only one person having a major interest in testing. This meeting helped establish agile methodologies but did not explicitly mention testing.
2) Early versions of agile testing focused on developers automating unit tests, with the view that testers roles would diminish. However, testers argued for the importance of other testing types like exploratory testing.
3) Over time, agile testing evolved to recognize different testing skills like test design, defect management, and exploratory testing. Automation tools also advanced to support both manual and automated testing by different roles within agile teams.
The document discusses different ways to get involved with WordPress development including fixing bugs, writing documentation, testing, and providing support. It outlines the development process on trac.wordpress.org and emphasizes asking questions on IRC or mailing lists. Testing, documentation, translation, and Google Summer of Code are also mentioned as involvement opportunities.
The document provides an overview of getting started with Selenium and outlines 8 steps to write automated tests:
1. Define a test strategy by determining what to test and which browsers to support
2. Choose a programming language like Java and set up dependencies
3. Learn Selenium fundamentals like locating elements and common actions
4. Write a first test to log in to a sample site
5. Create page objects and a base page to make tests reusable and maintainable
6. Add waits to make tests more resilient when waiting for elements
7. Set up a test harness for centralized setup/teardown, reporting and parallelization
8. Add cross-browser testing by using browser drivers locally or remotely
Assessment: Managing Tests, Projects, and Grade CenterStaci Trekles
A Fall 2015 workshop on how to manage tests, projects, and the Grade Center within BlackBoard. Includes tips on how to develop effective tests that measure what they intend to measure.
Trends in Agile Testing by Lisa CrispinDirecti Group
- The document discusses trends in agile testing and how testing approaches have changed from traditional to agile methods. It focuses on practices like continuous integration, test-driven development, automating regression tests, and exploratory testing.
- Key aspects of agile testing covered include the whole team approach, collaboration between testers and developers, automating tests at different levels, and using feedback to continuously improve.
- The presentation highlights current trends like behavior-driven development, open source testing tools, and more emphasis on examples and collaboration with customers.
The document provides an overview of software testing and black box testing techniques. It discusses various testing methods like white box, black box and grey box testing. It also covers different types of testing like functional testing, acceptance testing, etc. and black box testing techniques like equivalence partitioning, boundary value analysis, state transition testing, and decision table testing. The document lists advantages of black box testing like not requiring knowledge of internal implementation and disadvantages like only a small number of inputs can be tested. It concludes by thanking the audience.
Similar to Markus Gartner - Alternative Paths for Self-Education in Software Testing - EuroSTAR 2010 (20)
Why We Need Diversity in Testing- AccentureTEST Huddle
In this webinar Rasa (Testing capability lead for Denmark) and Matthias (EALA Testing capability lead) will share some of their own experiences why diversity matters, give insights into how Accenture as a global firm is promoting diversity and how we are in the process of changing our attitudes and processes to make all of this sustainable
Keys to continuous testing for faster delivery euro star webinar TEST Huddle
Your business needs to deliver faster. To accommodate, Development needs to introduce fewer changes but in a much more frequent cadence. This creates a challenge for test teams to keep up with the rapid pace of change without compromising on quality. Automation is paramount to the success or failure of Continuous Delivery, and Continuous Testing enables early and frequent quality feedback throughout the CI/CD pipeline.
In this webinar, Eran & Ayal will explore how to implement Continuous Testing to ensure high quality releases in a Continuous Delivery environment; including what to test and when to automate new functionality in order to optimize your efforts.
Why you Shouldnt Automated But You Will Anyway TEST Huddle
The document discusses automation in software testing. It begins by outlining common claims made about the benefits of automation, such as saving time and improving quality, but argues that these claims often don't hold true. Automation does not inherently save time, guarantee quality, or reduce resources needed. It also does not always save money when development, maintenance, and infrastructure costs are considered. The document provides a formula for determining when automation is worthwhile based on how many times a test case would need to be rerun manually. It concludes by acknowledging that, despite these drawbacks, organizations will still automate testing because it is exciting, managers demand it, and it benefits careers.
In this webinar Carsten will explore the role of the tester in a Scrum team. He will examine where the tester play an important role in Scrum and how you can contribute to a teams performance.
Leveraging Visual Testing with Your Functional TestsTEST Huddle
Designing and implementing (or selecting) the right automation strategy, for functional testing, with visual testing, can help your project with greater test coverage while improving test scalability
Big Data: The Magic to Attain New HeightsTEST Huddle
This document discusses how big data and data science can be used to attain new heights, likening it to magic. It provides an overview of Ken Johnston's background and experiences in data science. It then discusses six keys to a "big" magic show with big data: trying multiple times, addressing issues with over-counting, experimentation techniques like A/B testing, infrastructure for big data, tools and skills, and security, privacy and fraud protection. The document emphasizes the importance of an assistant to help the data scientist or data engineer with various tasks.
This talk suggests how we might make sense of the tools landscape of the near future, where the pressure to modernise processes and automate is greatest, and what a new test process supported by tools might look like.
Takeaways:
- We need to take machine learning in testing seriously, but it won’t be taking our jobs just yet
- We don’t need more test automation tools; today we need tools that capture tester knowledge
- Tools that that learn and think can’t work for testers until we solve the knowledge capture challenge.
View On-Demand Webinar: https://youtu.be/EzyUdJFuzlE
The document discusses Test Driven Development (TDD) and Test Driven Design. It uses the analogy of building a lightsaber and later a Death Star to illustrate the TDD process and benefits. Some benefits mentioned are better test coverage, less debugging, and better design. The document provides tips for practicing TDD including planning ahead, defining boundaries, taking small steps to pass each test, and maintaining discipline. It emphasizes trying TDD in a team and considering Behavior Driven Development (BDD) as well.
Scaling Agile with LeSS (Large Scale Scrum)TEST Huddle
In this webinar, Elad will cover the principles that the #LeSS framework has to offer in order to enable bug organisations to become agile.
View webinar recording - https://huddle.eurostarsoftwaretesting.com/resource/agile-testing/scaling-agile-less-large-scale-scrum/
Creating Agile Test Strategies for Larger EnterprisesTEST Huddle
Having difficulty creating an agile test strategy for your company? Let Testing Excellence Award winner, Derk-Jan de Grood, show you how it’s done
View webinar recording here - http://huddle.eurostarsoftwaretesting.com/resource/agile-testing/creating-agile-test-strategies-larger-enterprises/
3 key takeaways
- Do you know the meaning of your organisation, system, product?
- Can you deliver the important risks right away?
- How can you communicate about the (process and product) risks your dealing with?
View Webinar recording: https://huddle.eurostarsoftwaretesting.com/resource/test-management/is-there-a-risk/
Are Your Tests Well-Travelled? Thoughts About Test CoverageTEST Huddle
This document summarizes a presentation on test coverage given by Dorothy Graham. It uses an analogy of travel to different locations to explain what test coverage means and some caveats. Coverage refers to the relationship between tests and the parts of a system being tested, but achieving 100% coverage does not mean everything is tested. There are four caveats discussed: coverage only measures one aspect of testing, a single test can achieve coverage, coverage does not indicate quality, and it only applies to the existing system not missing pieces. The key recommendation is to ask "coverage of what?" when the term is used rather than assuming more coverage is always better.
It’s the same argument again and again. One side says “team members should all be able to do everything, and the programmers should do their testing and all testers should be writing code”. The other side says “No, that can’t possibly work – programmers don’t know how to test, they don’t have the right mindset”. And on and on it goes.
http://huddle.eurostarsoftwaretesting.com/resource/webinar/need-testers-agile-teams/
In this webinar, Dave Haeffner (Elemental Selenium, USA) discusses how to:
- Build an integrated feedback loop to automate test runs and find issues fast
- Setup your own infrastructure or connect to a cloud provider
-Dramatically improve test times with parallelization
https://huddle.eurostarsoftwaretesting.com/resource/webinar/use-selenium-successfully/
Testers & Teams on the Agile Fluency™ Journey TEST Huddle
The document discusses the Agile Fluency model, which aims to help teams and testers improve their agile skills and practices over time. It describes a pathway with increasing levels of fluency that provide more benefits, including delivering value, optimizing value, and innovating. Reaching higher levels requires investments in training, coaching, and changing team structures and roles. The model can help organizations determine what level of fluency they need and what investments are required for testing teams to operate at that level.
Key Takeaways:
- A diagramming method that helps discuss roles
- A one page analysis heuristic for roles
- Why roles matter on projects
https://huddle.eurostarsoftwaretesting.com/resource/people-skills/thinking-through-your-role/
Key Takeaways:
- What will this release contain
- What impact will it have on your test runs
- How can you preserve your existing investment in tests using the Selenium WebDriver APIs, and your even older RC tests
- Looking forward, when will the W3C spec be complete
- What can we expect from Selenium 4
https://huddle.eurostarsoftwaretesting.com/
Five Digital Age Trends That Will Dramatically Impact Testing And Quality Sk...TEST Huddle
Key Takeaways:
- Understand the key digital age trends that will disrupt large enterprises
- Learn what impact and opportunities these trends present for testing and quality engineering skills
- Discover how a comprehensive digital testing strategy integrated with high velocity intelligent automation enables success for the high performers of the future
Can virtualization transform your API lifecycle?TEST Huddle
Key Takeaways:
- API mocking vs. API virtualization – learn the differences
- Learn how API virtualization impacts all stages in your API lifecycle
- Hear how companies of all sizes are doing this in real life!
View on-demand webinar - https://youtu.be/ZxX8i91Hl9k
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Webinar: Designing a schema for a Data WarehouseFederico Razzoli
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
Markus Gartner - Alternative Paths for Self-Education in Software Testing - EuroSTAR 2010
1. Alternative Paths for Self-Education In Software Testing
Markus Gärtner -http://blog.shino.de -Twitter: @mgaertnehttp://commons.wikimedia.org/wiki/File:Education_-_Grad_Hat_-_Jordan.png
2. Education in Software Testing
My story
University studies until October 2005
1st position as a software tester April 2006
1st training course in software testing: October 2007
Appointed a software testing group lead position in September 2007!
3. Who is responsible for your education?
Your employer?
Your superior?
Your teacher back in school?
Maybe your husband/wife?
Your kids?
6. Feedback
Start a personal blog or private journal
Write an article
Contribute to mailing lists
Involve yourself in social media
Twitter
LinkedIn
Software Testing Club
Weekend Testing
7. Learn to program
Scripting languages: Ruby, Python, Groovy
Design Patterns
Technology: TDD, Mocking
Pairing
http://stevelucasmetz.blogspot.com/2008/01/rambo-baby.html
11. Black-box Software Testing
Developed by Cem Kaner and James Bach
Online courses by AST
Videos online available:
http://www.testingeducation.org/BBST/
http://upload.wikimedia.org/wikipedia/commons/1/1b/Peering_Inside_the_Black_Box.jpg
13. Buccaneer-scholar
Book by James Bach
Learning heuristics
SACKED SCOWS
Long Leash Heuristic
Obsess and Forget Heuristic
Procrastinate and Push Heuristic
… are just some of the underlying principles
http://running-wild.net/pics/content/gallery/tattoos/04.jpg
15. Testing Dojos
Similar to Coding Dojos
Collaboration
Save Environment
Deliberate Practice
Content:
Single Testing vs. Paired Testing
Test this, Evaluate Tools, Learn new approaches
http://www.matrix-architekt.de/bilder/desktop/dojo.jpg
16. Weekend Testing
Testing on the weekend online
Typical session:
1 hour Practical testing
1 hour Discussion
Content:
Test this
Evaluate tools
Learn new approaches
Watch out for traps!
17. Miagi-Do School of Software Testing
Founded by Matt Heusser
Non-commercial, zero-profit
Improve testing skill
Through practice
Belt system
http://farm3.static.flickr.com/2074/2200982710_8cf8e0d422.jpg
18. Summary
Education is your repsonsibility
Different styles
Feedback
Hypothesis
Synthesis
You may have preferences for one or the other, but you should apply as much as possible