The document describes a presentation on keyword-driven test automation given by Hans Buwalda of LogiGear Corporation. The presentation introduces keyword-driven testing and compares it to other automation techniques. It provides recommendations for successfully applying keyword-driven testing to test design, automation, and organization. The presentation also covers topics like data-driven testing, non-UI testing, and test automation best practices.
Introducing Keyword-driven Test AutomationTechWell
The document introduces a tutorial on keyword-driven test automation presented by Hans Buwalda of LogiGear, providing background on Buwalda and LogiGear, an agenda for the tutorial covering keyword-driven testing and recommendations for successful implementation, and examples of how keyword-driven testing can be applied.
Oplægget blev holdt ved et seminar i InfinIT-interessegruppen Softwaretest den 28. september 2010.
Læs mere om interessegruppen på http://www.infinit.dk/dk/interessegrupper/softwaretest/softwaretest.htm
Keyword-driven testing is a software testing methodology that uses predefined keywords to describe test cases instead of natural language. Keywords represent common testing actions and are associated with code that implements those actions. This allows testers to write automated test cases without extensive programming knowledge. The document discusses how to implement keyword-driven testing using the Maveryx test automation tool, including identifying keywords, writing test cases with keywords, implementing keyword code, and executing automated tests.
These are the slides we presented at the 2009 Montreal CodeCamp for our FluentSelenium test DSL. FluentSelenium demonstrates how it is possible to make test code cleaner by introducing appropriate test abstractions.
see http://fluentselenium.codeplex.com/
Test-driven development (TDD) is a software development technique where unit tests are written before code to define desired functionality. Writing tests first helps produce code with better design, lower maintenance costs, and fewer bugs. Key principles of TDD include writing code only to pass failing tests and eliminating duplication. Benefits include better test coverage, easier refactoring, and preventing regressions. TDD helps developers act as users to define behavior through interactions between system components.
Engaging IV&V Testing Services for Agile ProjectsRavi Kumar
This document discusses agile testing and the role of testers in agile development. It covers topics like the value testers provide, Brian Marick's test categories, challenges with agile testing and strategies to address them, and the role of automation and continuous integration. Key points emphasized are that testers are not obsolete in agile and need to adapt to new ways of testing, defining acceptance criteria, collaborating with developers, automating tests, and providing frequent feedback to the team.
Testing Experience - Evolution of Test Automation FrameworksŁukasz Morawski
Implementing automated tests is something that everybody wants to do. If you ask
any tester, test automation is their aim. And while it may be the golden target, very
few testers take pains to assess the required knowledge, under the illusion that a
programming language or expensive tool will suffice to cope with all problems likely
to arise. This is not true. Writing good automated tests is much harder than that,
requiring knowledge this article will make clear
The document discusses a test automation framework (TAF) that helps perform automated testing effectively. It has several key features including being keyword-driven, product-independent, tool-independent, and compatible with continuous integration frameworks. The TAF workflow involves initialization, development, usage, and maintenance phases. The TAF architecture consists of test scenarios that run via the TAF core and output results to various formats.
Introducing Keyword-driven Test AutomationTechWell
The document introduces a tutorial on keyword-driven test automation presented by Hans Buwalda of LogiGear, providing background on Buwalda and LogiGear, an agenda for the tutorial covering keyword-driven testing and recommendations for successful implementation, and examples of how keyword-driven testing can be applied.
Oplægget blev holdt ved et seminar i InfinIT-interessegruppen Softwaretest den 28. september 2010.
Læs mere om interessegruppen på http://www.infinit.dk/dk/interessegrupper/softwaretest/softwaretest.htm
Keyword-driven testing is a software testing methodology that uses predefined keywords to describe test cases instead of natural language. Keywords represent common testing actions and are associated with code that implements those actions. This allows testers to write automated test cases without extensive programming knowledge. The document discusses how to implement keyword-driven testing using the Maveryx test automation tool, including identifying keywords, writing test cases with keywords, implementing keyword code, and executing automated tests.
These are the slides we presented at the 2009 Montreal CodeCamp for our FluentSelenium test DSL. FluentSelenium demonstrates how it is possible to make test code cleaner by introducing appropriate test abstractions.
see http://fluentselenium.codeplex.com/
Test-driven development (TDD) is a software development technique where unit tests are written before code to define desired functionality. Writing tests first helps produce code with better design, lower maintenance costs, and fewer bugs. Key principles of TDD include writing code only to pass failing tests and eliminating duplication. Benefits include better test coverage, easier refactoring, and preventing regressions. TDD helps developers act as users to define behavior through interactions between system components.
Engaging IV&V Testing Services for Agile ProjectsRavi Kumar
This document discusses agile testing and the role of testers in agile development. It covers topics like the value testers provide, Brian Marick's test categories, challenges with agile testing and strategies to address them, and the role of automation and continuous integration. Key points emphasized are that testers are not obsolete in agile and need to adapt to new ways of testing, defining acceptance criteria, collaborating with developers, automating tests, and providing frequent feedback to the team.
Testing Experience - Evolution of Test Automation FrameworksŁukasz Morawski
Implementing automated tests is something that everybody wants to do. If you ask
any tester, test automation is their aim. And while it may be the golden target, very
few testers take pains to assess the required knowledge, under the illusion that a
programming language or expensive tool will suffice to cope with all problems likely
to arise. This is not true. Writing good automated tests is much harder than that,
requiring knowledge this article will make clear
The document discusses a test automation framework (TAF) that helps perform automated testing effectively. It has several key features including being keyword-driven, product-independent, tool-independent, and compatible with continuous integration frameworks. The TAF workflow involves initialization, development, usage, and maintenance phases. The TAF architecture consists of test scenarios that run via the TAF core and output results to various formats.
'Software Automation Testing Secrets Revealed' book written by Narayanan Palani and available across Amazon.
Who this book is written for:
If you are a software testing professional, a developer, or a student looking forward to get a job in software industry, this book will help in creating automation test scripts for your web applications, this is the right guide for you! As a prerequisite, a basic knowledge in programming languages are expected, although any previous knowledge of testing tools are not necessary.
What you will learn from this book:
Learn for software testing job opportunities on how automation frameworks designed and understand how to overcome limitations of not knowing such testing tools in the past
Setup and use automation tools for twelve different automation frameworks such as Selenium, HP UFT (formerly QTP),Ranorex, RFT and other famous automation testing tools
Learn how to deal with the advanced features of automation tools which will be helpful for software testing job opportunities!
Understand how the most wanted automation technologies can be designed such as excel automation frameworks which will help for testing projects of leading clients across US,UK.
Practice the sample projects using clear instructions from each chapter and apply for relevant software testing jobs in your desired location!
Codeception Testing Framework -- English #phpkansaiFlorent Batard
The document discusses introducing Codeception, a PHP testing framework. It begins with an agenda that includes a presentation on Codeception, different test types, a demonstration, and best practices. It then introduces the speaker, Florent Batard, who is a security engineer and web developer from France. He explains why testing is important for reducing assumptions and validating that code runs as expected. The bulk of the document then focuses on Codeception, explaining what it is, how it works, the different types of tests it supports including acceptance, functional, and unit tests, and how to install and use it. Code examples are provided and it concludes with referencing materials and opening the floor for questions.
The document contains interview questions from various companies like HCL, Emids, Manhattan, 3PLM, Zolipe Solutions, Synchronoss, and Cognizant for positions ranging from 2-3 years of experience in Selenium testing. The questions cover a wide range of topics including Selenium, manual testing, Java, SQL, algorithms, data structures and design patterns. Common questions asked relate to frameworks, test automation lifecycles, handling dynamic elements, test case design techniques, and debugging skills.
Selenium Automation Testing Interview Questions And AnswersAjit Jadhav
This document contains 30 interview questions and answers related to Selenium testing. Some of the key questions covered include how to start the Selenium server from code, how to handle multiple browser windows, locate elements and verify text, connect to databases, and use Selenium Grid for parallel testing across different machines. The answers provide technical details on using Selenium commands, locators, and programming techniques.
Automation testing involves automating manual testing processes using software tools to execute test scripts and compare expected and actual results. There are different types of automation frameworks including data-driven, keyword-driven, modular, and hybrid frameworks. Implementing an automation framework involves 10 steps: identifying the testing scope and needs, evaluating tools, designing the framework, developing and populating test data, and configuring schedulers.
Test-Driven Development is about approaching software development from a test perspective and knowing how to use the tools (e.g. JUnit, Mockito) to effectively write tests.
Source code examples @...
https://github.com/codeprimate-software/test-driven-development
Test driven development (TDD), a software development method, helps build high quality applications faster. Life-cycle, usefulness, limitations and similar techniques of TDD have been presented in this slide deck.
Lightening Talk I gave at Inaka in April 2014.
I was in charge of investigating test-driven development for our iOS mobile team. Since I realized it was such a big concept, after having gathered enough information and having played with it enough, I decided to introduce my fellows on the topic by presenting it in a formal talk with slides. The aim was teaching them a different way of developing, which, for us, at that moment, was completely new and controversial.
Test Automation Frameworks Using Selenium | EdurekaEdureka!
YouTube: https://youtu.be/2idCKxbhXOk
** Test Automation Engineer Masters Program: https://www.edureka.co/masters-program/automation-testing-engineer-training **
This Edureka Live PPT on ‘Test Automation Framework’ will help you learn about what testing frameworks are and how to build one using Selenium. Below topics are covered in this PPT:
Introduction to Automation Testing
Approaches to Test Automation
Test Automation Frameworks
Types of Test Automation Frameworks
Demo: How to build a test automation framework using selenium.
Security Testing Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Hybrid Automation Framework Development introductionGanuka Yashantha
The document discusses hybrid test automation frameworks. A hybrid framework combines aspects of data-driven and keyword-driven frameworks to eliminate their individual disadvantages. It allows testers to write tests using keywords without coding, while supporting bulk data changes and flexible execution like data-driven frameworks. The document proposes a sample hybrid framework where test data, page objects, and keywords are defined in an Excel file, eliminating the need for code. This provides reusability, maintainability and a low learning curve while maintaining flexibility.
This document discusses test-driven development (TDD), behavior-driven development (BDD), and acceptance test-driven development (ATDD). It explains that while they have different names, they all share the same core idea of using examples from business requirements to create automated tests. The document provides examples of how to write tests before having a user interface, and recommends abstracting from the GUI to focus on business logic. It also lists some popular tools that can be used for ATDD, BDD, and TDD.
Not long ago, testing Ajax components meant play-testing a page by hand. Today, there are a growing number of tools we can use to simplify and automate Ajax testing.
In this session we will cover when to test, what to test and how to test Ajax components. You learn how to create automatic tests with various tools, including YUI Test, and OpenQA Selenium, and how to use Ajax testing tools with IDEs and Continuous Integration systems.
In this session, you will learn:
* When, where and how to test Ajax components;
* How to create automatic tests with various tools;
* How to use Ajax testing tools with IDEs and Continuous Integration systems.
Software testing tools (free and open source)Wael Mansour
This document discusses various tools used for test automation including Cobertura, Selenium, JMeter, Bugzilla, and Testia Tarantula. Cobertura is a code coverage tool that calculates test coverage percentages. Selenium is described as a tool for automating web application testing across browsers. JMeter is introduced as a load testing tool focused on analyzing performance of web applications. Bugzilla and Tarantula are mentioned as tools for bug tracking and project/test management respectively in agile software development. The document also discusses integrating these various tools together for a complete test automation framework.
This document provides an overview of test automation using Cucumber and Calabash. It discusses using Cucumber to write automated test specifications in plain language and Calabash to execute those tests on Android apps. It outlines the environments, tools, and basic steps needed to get started, including installing Ruby and DevKit, creating Cucumber feature files, and using Calabash APIs to automate user interactions like tapping, entering text, and scrolling. The document also explains how to run tests on an Android app and generate an HTML report of the results.
Selenium Tutorial for Beginners | Automation framework BasicsTechcanvass
In this presentation, you will learn about the basics of Testing Automation framework. You will learn about the types of automation frameworks, details of these frameworks as well as pros and cons of these frameworks.
Java Selenium 3.0 Training
--------------------------------------
http://techcanvass.com/Courses/selenium-training-course.aspx
Python Selenium 3.0 Training
---------------------------------------------
http://techcanvass.com/Courses/selenium-training-with-python.aspx
Techcanvass is a software development and training organization. We provide IT certifications training for mid-level professionals.
We specialize in the following areas:
a) Selenium v3.0 training with Java and Python
b) IIBA Business Analysis certifications (all levels)
c) Certified Agile Business Analyst Training
d) Data Science Training ( R, Python and Big Data) and Tableau
Website: http://techcanvass.com
Facebook Page: https://www.facebbook.com/Techcanvass
Twitter Handle: @techcanvass
This document provides an overview of test-driven development (TDD). It defines TDD as a technique for building software where tests are written before code to guide development. The key aspects of TDD covered are:
- Writing tests first before code, which helps improve design and ensures tests are written.
- The TDD mantra of Red-Green-Refactor, where tests initially fail (Red), code is written to pass tests (Green), then code is refactored to improve design.
- An example case study of a large Java project developed using TDD that has over 20,000 lines of unit tests providing over 90% test coverage.
How to Survive the Coming Test Automation Zombie ApocalypseTechWell
Test automation is software development. To automate tests well, you have to have brains. Unfortunately, the very brains that make you good at your job also make you highly attractive to zombies. Like all zombies, test automation zombies are brainless, insatiable, and relentless. Unlike human zombies, test automation zombies can be difficult to recognize. They don’t look like people at all. Some look like org charts. Some look like best practices. Some you can’t see at all—bad habits that “seemed like a good idea at the time.” Dale Emery has survived numerous test automation zombie attacks with almost no permanent damage. Dale knows zombies, and teaches you to recognize them. Automating only at the end of a sprint? Zombie. Sprinkling fixed delays through your tests to accommodate unresponsive web pages? Zombie. Automating only by record and playback? Zombie. Make no mistake—the test automation zombies are coming. Learn how to spot them before they eat your brains.
The document summarizes a presentation by Sanjiv Augustine on timeless lean management solutions. It discusses three key solutions: 1) Organizing around a network of small, self-organizing teams. 2) Driving lean innovation through techniques like lean startup methodology. 3) Practicing wise leadership through empowering teams, flattening hierarchies, and trusting the team. The presentation provides examples of how companies like Ericsson have successfully implemented these lean-agile principles at scale.
'Software Automation Testing Secrets Revealed' book written by Narayanan Palani and available across Amazon.
Who this book is written for:
If you are a software testing professional, a developer, or a student looking forward to get a job in software industry, this book will help in creating automation test scripts for your web applications, this is the right guide for you! As a prerequisite, a basic knowledge in programming languages are expected, although any previous knowledge of testing tools are not necessary.
What you will learn from this book:
Learn for software testing job opportunities on how automation frameworks designed and understand how to overcome limitations of not knowing such testing tools in the past
Setup and use automation tools for twelve different automation frameworks such as Selenium, HP UFT (formerly QTP),Ranorex, RFT and other famous automation testing tools
Learn how to deal with the advanced features of automation tools which will be helpful for software testing job opportunities!
Understand how the most wanted automation technologies can be designed such as excel automation frameworks which will help for testing projects of leading clients across US,UK.
Practice the sample projects using clear instructions from each chapter and apply for relevant software testing jobs in your desired location!
Codeception Testing Framework -- English #phpkansaiFlorent Batard
The document discusses introducing Codeception, a PHP testing framework. It begins with an agenda that includes a presentation on Codeception, different test types, a demonstration, and best practices. It then introduces the speaker, Florent Batard, who is a security engineer and web developer from France. He explains why testing is important for reducing assumptions and validating that code runs as expected. The bulk of the document then focuses on Codeception, explaining what it is, how it works, the different types of tests it supports including acceptance, functional, and unit tests, and how to install and use it. Code examples are provided and it concludes with referencing materials and opening the floor for questions.
The document contains interview questions from various companies like HCL, Emids, Manhattan, 3PLM, Zolipe Solutions, Synchronoss, and Cognizant for positions ranging from 2-3 years of experience in Selenium testing. The questions cover a wide range of topics including Selenium, manual testing, Java, SQL, algorithms, data structures and design patterns. Common questions asked relate to frameworks, test automation lifecycles, handling dynamic elements, test case design techniques, and debugging skills.
Selenium Automation Testing Interview Questions And AnswersAjit Jadhav
This document contains 30 interview questions and answers related to Selenium testing. Some of the key questions covered include how to start the Selenium server from code, how to handle multiple browser windows, locate elements and verify text, connect to databases, and use Selenium Grid for parallel testing across different machines. The answers provide technical details on using Selenium commands, locators, and programming techniques.
Automation testing involves automating manual testing processes using software tools to execute test scripts and compare expected and actual results. There are different types of automation frameworks including data-driven, keyword-driven, modular, and hybrid frameworks. Implementing an automation framework involves 10 steps: identifying the testing scope and needs, evaluating tools, designing the framework, developing and populating test data, and configuring schedulers.
Test-Driven Development is about approaching software development from a test perspective and knowing how to use the tools (e.g. JUnit, Mockito) to effectively write tests.
Source code examples @...
https://github.com/codeprimate-software/test-driven-development
Test driven development (TDD), a software development method, helps build high quality applications faster. Life-cycle, usefulness, limitations and similar techniques of TDD have been presented in this slide deck.
Lightening Talk I gave at Inaka in April 2014.
I was in charge of investigating test-driven development for our iOS mobile team. Since I realized it was such a big concept, after having gathered enough information and having played with it enough, I decided to introduce my fellows on the topic by presenting it in a formal talk with slides. The aim was teaching them a different way of developing, which, for us, at that moment, was completely new and controversial.
Test Automation Frameworks Using Selenium | EdurekaEdureka!
YouTube: https://youtu.be/2idCKxbhXOk
** Test Automation Engineer Masters Program: https://www.edureka.co/masters-program/automation-testing-engineer-training **
This Edureka Live PPT on ‘Test Automation Framework’ will help you learn about what testing frameworks are and how to build one using Selenium. Below topics are covered in this PPT:
Introduction to Automation Testing
Approaches to Test Automation
Test Automation Frameworks
Types of Test Automation Frameworks
Demo: How to build a test automation framework using selenium.
Security Testing Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Hybrid Automation Framework Development introductionGanuka Yashantha
The document discusses hybrid test automation frameworks. A hybrid framework combines aspects of data-driven and keyword-driven frameworks to eliminate their individual disadvantages. It allows testers to write tests using keywords without coding, while supporting bulk data changes and flexible execution like data-driven frameworks. The document proposes a sample hybrid framework where test data, page objects, and keywords are defined in an Excel file, eliminating the need for code. This provides reusability, maintainability and a low learning curve while maintaining flexibility.
This document discusses test-driven development (TDD), behavior-driven development (BDD), and acceptance test-driven development (ATDD). It explains that while they have different names, they all share the same core idea of using examples from business requirements to create automated tests. The document provides examples of how to write tests before having a user interface, and recommends abstracting from the GUI to focus on business logic. It also lists some popular tools that can be used for ATDD, BDD, and TDD.
Not long ago, testing Ajax components meant play-testing a page by hand. Today, there are a growing number of tools we can use to simplify and automate Ajax testing.
In this session we will cover when to test, what to test and how to test Ajax components. You learn how to create automatic tests with various tools, including YUI Test, and OpenQA Selenium, and how to use Ajax testing tools with IDEs and Continuous Integration systems.
In this session, you will learn:
* When, where and how to test Ajax components;
* How to create automatic tests with various tools;
* How to use Ajax testing tools with IDEs and Continuous Integration systems.
Software testing tools (free and open source)Wael Mansour
This document discusses various tools used for test automation including Cobertura, Selenium, JMeter, Bugzilla, and Testia Tarantula. Cobertura is a code coverage tool that calculates test coverage percentages. Selenium is described as a tool for automating web application testing across browsers. JMeter is introduced as a load testing tool focused on analyzing performance of web applications. Bugzilla and Tarantula are mentioned as tools for bug tracking and project/test management respectively in agile software development. The document also discusses integrating these various tools together for a complete test automation framework.
This document provides an overview of test automation using Cucumber and Calabash. It discusses using Cucumber to write automated test specifications in plain language and Calabash to execute those tests on Android apps. It outlines the environments, tools, and basic steps needed to get started, including installing Ruby and DevKit, creating Cucumber feature files, and using Calabash APIs to automate user interactions like tapping, entering text, and scrolling. The document also explains how to run tests on an Android app and generate an HTML report of the results.
Selenium Tutorial for Beginners | Automation framework BasicsTechcanvass
In this presentation, you will learn about the basics of Testing Automation framework. You will learn about the types of automation frameworks, details of these frameworks as well as pros and cons of these frameworks.
Java Selenium 3.0 Training
--------------------------------------
http://techcanvass.com/Courses/selenium-training-course.aspx
Python Selenium 3.0 Training
---------------------------------------------
http://techcanvass.com/Courses/selenium-training-with-python.aspx
Techcanvass is a software development and training organization. We provide IT certifications training for mid-level professionals.
We specialize in the following areas:
a) Selenium v3.0 training with Java and Python
b) IIBA Business Analysis certifications (all levels)
c) Certified Agile Business Analyst Training
d) Data Science Training ( R, Python and Big Data) and Tableau
Website: http://techcanvass.com
Facebook Page: https://www.facebbook.com/Techcanvass
Twitter Handle: @techcanvass
This document provides an overview of test-driven development (TDD). It defines TDD as a technique for building software where tests are written before code to guide development. The key aspects of TDD covered are:
- Writing tests first before code, which helps improve design and ensures tests are written.
- The TDD mantra of Red-Green-Refactor, where tests initially fail (Red), code is written to pass tests (Green), then code is refactored to improve design.
- An example case study of a large Java project developed using TDD that has over 20,000 lines of unit tests providing over 90% test coverage.
How to Survive the Coming Test Automation Zombie ApocalypseTechWell
Test automation is software development. To automate tests well, you have to have brains. Unfortunately, the very brains that make you good at your job also make you highly attractive to zombies. Like all zombies, test automation zombies are brainless, insatiable, and relentless. Unlike human zombies, test automation zombies can be difficult to recognize. They don’t look like people at all. Some look like org charts. Some look like best practices. Some you can’t see at all—bad habits that “seemed like a good idea at the time.” Dale Emery has survived numerous test automation zombie attacks with almost no permanent damage. Dale knows zombies, and teaches you to recognize them. Automating only at the end of a sprint? Zombie. Sprinkling fixed delays through your tests to accommodate unresponsive web pages? Zombie. Automating only by record and playback? Zombie. Make no mistake—the test automation zombies are coming. Learn how to spot them before they eat your brains.
The document summarizes a presentation by Sanjiv Augustine on timeless lean management solutions. It discusses three key solutions: 1) Organizing around a network of small, self-organizing teams. 2) Driving lean innovation through techniques like lean startup methodology. 3) Practicing wise leadership through empowering teams, flattening hierarchies, and trusting the team. The presentation provides examples of how companies like Ericsson have successfully implemented these lean-agile principles at scale.
Keynote: Surviving or Thriving: Top Ten Lessons for the Professional TesterTechWell
As testers and test managers we often find ourselves struggling just to survive within our organization—sometimes with the possibility of job loss due to outsourcing looming. Often, we are told to become more “effective,” “efficient,” and do “more with less.” However, most testers and test managers are unsure of what those mandates actually mean. Today, it is not sufficient to just survive; we must take initiatives to thrive. Lloyd Roden shares ten valuable lessons on how you can become better at testing and thrive in your career. Lloyd's lessons include the importance of using modern technology in testing, using test design techniques when reviewing documentation, testing the testers with techniques such as bug seeding, reporting project waste, providing management with feedback on decisions that they made, becoming a pioneer or explorer rather than a settler or outlaw in your organization, and more. Lloyd’s advice is practical—and challenging—for all testers, test leads, and test managers.
Yin and Yang: Metrics within Agile and Traditional LifecyclesTechWell
Metrics are powerful tools when used to effect positive change in a project or organization. However, the value and benefits of metrics are often dependent on the context. While certain metrics provide information and insight to drive decision making for a traditional development approach, they may not be useful in an agile landscape—and vice versa. QA and agile experts Shaun Bradshaw and Bob Galen delve into the value, pitfalls, pros, and cons of various metrics in agile and waterfall development environments. Hear their experiences as they discuss and explore a variety of project-level, software development, and software testing metrics through the lens of both traditional and agile development contexts. Although Bob and Shaun respect each other’s knowledge and skill, they don’t often agree on metrics. And in this showdown, you’ll see why! Be prepared to learn, be entertained, and be ready to get in on the action as these two metrics titans go head-to-head.
To be most effective, test managers must develop and use metrics to help direct the testing effort and make informed recommendations about the software’s release readiness and associated risks. Because one important testing activity is to “measure” the quality of the software, test managers must measure the results of both the development and testing processes. Collecting, analyzing, and using metrics is complicated because many developers and testers are concerned that the metrics will be used against them. Join Rick Craig as he addresses common metrics—measures of product quality, defect removal efficiency, defect density, defect arrival rate, and testing status. Learn the guidelines for developing a test measurement program, rules of thumb for collecting data, and ways to avoid “metrics dysfunction.” Rick identifies several metrics paradigms and discusses the pros and cons of each. Delegates are urged to bring their metrics problems and issues for use as discussion points.
An Introduction to SAFe: The Scaled Agile FrameworkTechWell
Many organizations have achieved agility at the team level only to be unable to achieve it across teams. The Scaled Agile Framework (SAFe) provides both a vision and method for how to achieve this. SAFe is the first documented framework that can be used to scale agile throughout an organization. It is a combination of lean, kanban, and Scrum—lean to provide a context for an organization, kanban to manage the flow of projects, and Scrum to provide agile at the team level. Beginning with an introduction to lean and kanban, Ken Pugh explains why they are required for agile at scale. Ken then describes the framework of SAFe—specifically how it creates a structure to manifest the behaviors required for agile at scale. In particular, learn how to coordinate your organization’s portfolio, programs, and projects. Ken concludes by discussing when it is advisable to use the framework and when a more emergent method is preferable.
On traditional projects, testers usually join the project after coding has started, or even later when coding is almost finished. Testers have no role in advising the project team early regarding quality issues but focus only on finding defects. They become accustomed to this style of working and adjust their mental processes accordingly. In agile, testers must collaborate closely with customers and programmers throughout the development lifecycle, where their focus changes from finding defects to preventing them. Janet Gregory shares ways to change the tester’s mindset from “How can I break the software?” to “How can I help deliver excellent software?”—a critical mental shift on agile projects. Another facet of the mind-set change is learning how to test early and incrementally. Janet uses interactive exercises and examples to help you understand how effective this mindset change is—and how you can apply it on your agile projects.
Stakeholders always want to release when they think we’ve “finished testing”. They believe we have revealed “all of the important problems” and “verified all of the fixes,” and now it’s time to reap the rewards. However, as testers we still can assist in improving software by learning about problems after code has rolled “live-to-site”—especially if it’s a website. At eBay we have a post-ship “site quality” mindset in which testers continue to learn from A/B testing, operational issues, customer sentiment analysis, discussion forums, and customer call patterns—just to name a few. Jon Bach explains how and what eBay’s Live Site Quality team learns every day about what they just released to production. Take away some ideas on what you can do to test and improve value—even after you’ve shipped.
ADC-BSC EAST 2013 Keynote: Worse Is Better—For Better or for WorseTechWell
More than two decades ago, Richard P. Gabriel proposed the idea that “Worse Is Better” to explain why some things that are designed to be pure and perfect are eclipsed by solutions that are compromised and imperfect. This is not simply an observation that things should be better but are not, or that flawed and ill-considered solutions sometimes win out over those created with intention. Rather, many solutions that are narrow and incomplete work out better than those seen as comprehensive and complete. Whether programming languages, operating systems, or development practices, we find many examples in software development, some more provocative and surprising than others—Unix, Linux, C, COM, the web, the Wiki, incremental development, and TDD, to name but a few. The Worse Is Better philosophy pre-dates and anticipates agile development, but some of its finer points are still overlooked by agile and fragile projects everywhere. As Kevlin Henney revisits the original premise and question, he shares examples that can teach us new and surprising things.
Leveraging Core Values for Healthier, More Productive TeamsTechWell
Although all teams require a healthy level of interaction, high-performing teams' interactions are all based on trust, respect, and shared goals. Such teams find ways to overcome the fear of conflict, and quickly identify and resolve issues that are getting in the way. Scott Ross shares how, when the Omnyx software R&D department determined their culture was hindering performance, they crafted a core values statement that has served them well for the past three years. Scott describes the ways they proactively and intentionally use their value statement to drive the culture they seek and discusses the results they have achieved. Take back the list of resources that Scott uses daily to help himself and others see how their actions add to and take away from their core values. Return to the office prepared to use this same process with your team and start on the road to a high-performing team whose members love to come to work every day.
Patters for Team Collaboration: Toward Whole Team QualityTechWell
The half-day tutorial covered patterns for team collaboration toward whole-team quality, presented by Janet Gregory and Matt Barcomb. The presentation defined patterns as models or reliable traits and discussed various collaboration patterns including generalizing specialists, pairing, shared vision using tools like business model canvases and impact mapping, specification techniques like user story mapping and acceptance test-driven development, and paired development practices like continuous testing, test-driven development, and configuration management. The goal was to provide teams with collaborative techniques to improve quality.
Agile Development in a Regulated EnvironmentTechWell
There is no doubt that agile is an accepted development methodology. However, if you work in a regulated industry like health care where you have to comply with its standard operating procedures, heaps of paperwork, and frequent audits, don’t these conflict with agile’s core tenets? Chris Ampenberger describes his operating environment and the applicable regulations that define the constraints for the software development process he can use. He shares how they overcame the incongruity between agile and regulatory requirements. With real-world examples, Chris demonstrates how you can produce the required documentation as a byproduct of the scrum team’s everyday work and illustrates how his teams succeeded in an agile way, achieving significant increases in productivity. Chris points out common pitfalls, details the hurdles they had to overcome, and discusses how to obtain buy-in from stakeholders at all levels of the organization. If you are working in a regulated environment, this session is for you.
Test Automation on Large Agile Projects: It's Not a CakewalkTechWell
1) The document discusses test automation on large agile projects. It describes how test automation grew and responsibilities were divided across multiple teams over 2.5 years on one project.
2) Key reasons for test automation included keeping development on track, capturing knowledge, and automating repetitive work. Issues that arose included accumulating test debt and tools contributing to segmented responsibilities.
3) The presentation provides lessons learned around defining "Done", managing test debt, and organizing testing responsibilities across teams as projects increase in size and complexity. Setting expectations for test code quality and having integrated discussions on story size were emphasized.
Many believe that regression testing an application with minimal data is sufficient. With big data applications, the data testing methodology becomes far more complex. Testing can now be done within the data fabrication process as well as in the data delivery process. Today, comprehensive testing is often mandated by regulatory agencies—and more importantly by customers. Finding issues before deployment and saving your company’s reputation—and in some cases preventing litigation—are critical. Jason Rauen presents an overview of the architecture, processes, techniques, and lessons learned by an original big data company. Detecting defects up-front is vital. Learn how to test thousands, millions, and in some cases billions—yes, billions—of records directly, rendering sampling procedures obsolete. Save time and money for your organization with better data test coverage than ever before.
In her book Agile Testing: A Practical Guide for Testers and Agile Teams, Janet Gregory recommends using the automation pyramid as a model for test coverage. In the pyramid model, most automated tests are unit tests written and maintained by the programmers,and tests that execute below the user interface—API-level tests that can be developed and maintained collaboratively by programmers and testers. However, as agile becomes mainstream, some circumstances may challenge this model. Many applications are transferring logic back to the client side by using programming languages such as JavaScript. Legacy systems, using languages such as COBOL, don’t have access to unit testing frameworks. Janet shows how to adapt the model to your needs and addresses some of these automation issues. During the session, delegates are encouraged to share their challenges and success stories.
The document announces a presentation titled "Test Estimation for Managers" to be given by Julie Gardiner of The Test People. Julie Gardiner has over 20 years of experience in IT in roles including analyst programmer, Oracle DBA, project manager, test analyst, test team leader, test consultant, and test manager. She is now head of agile, talent and transition management with The Test People and specializes in risk-based testing, agile testing, test management, and people issues.
Introducing Keyword-driven Test AutomationTechWell
In both agile and traditional projects, keyword-driven testing—when done correctly—has proven to be a powerful way to attain a high level of automation. Many testing organizations use keyword-driven testing but aren't realizing the full benefits of scalability and maintainability that are essential to keep up with the demands of testing today's software. Hans Buwalda describes the keyword approach, and how you use it to can meet the very aggressive goal that he calls the "5 percent challenge"―automate 95 percent of your tests with no more than 5 percent of your total testing effort. Hans also discusses how the keyword approach relates to other automation techniques like scripting and data-driven testing, and in what way keywords can be used for specific situations like graphics, multimedia, and mobile. Use the information and the real-world examples that Hans presents to attain a very high level of maintainable automation with the lowest possible effort.
Introducing Keyword-Driven Test AutomationTechWell
In both agile and traditional projects, keyword-driven testing—when done correctly—has proven to be a powerful way to attain a high level of automation. Many testing organizations use keyword-driven testing but aren't realizing the full benefits of scalability and maintainability that are essential to keep up with the demands of testing today's software. Hans Buwalda describes the keyword approach, and how you use it to can meet the very aggressive goal that he calls the "5 percent challenge"―automate 95 percent of your tests with no more than 5 percent of your total testing effort. Hans also discusses how the keyword approach relates to other automation techniques like scripting and data-driven testing, and the ways keywords can be used for specific situations like graphics, multimedia, and mobile. Use the information and the real-world examples that Hans presents to attain a very high level of maintainable automation with the lowest possible effort.
Introducing Keyword-driven Test AutomationTechWell
This document provides an overview of a tutorial presentation on keyword-driven test automation. The tutorial will cover an introduction to keyword-driven testing, comparisons to other automation techniques, and recommendations for successful implementation, including test design, automation, and organization. Specific topics that will be discussed include data-driven testing, non-UI testing, multi-media testing, protocol testing, and using keywords for test management, development, and both automated and manual testing. The keyword-driven approach called Action Based Testing (ABT) emphasizes test design and uses test modules to organize test cases.
The Challenges of BIG Testing: Automation, Virtualization, Outsourcing, and MoreTechWell
Large-scale testing projects can severely stress many of the testing practices we have gotten used to over the year. This can result in less than optimal outcomes. A number of innovative ideas and concepts have emerged to support industrial-strength testing of large and complex projects. Hans Buwalda shares his experiences and the strategies he's developed and used for large testing on large projects. Learn how to design tests specifically for automation and how to successfully incorporate keyword testing. The automation discussion will include virtualization and cloud options, how to deal with numerous versions and configurations common to large projects, and how to handle the complexity added by mobile devices. Hans also outlines the possibilities and pitfalls of outsourcing test automation. The information presented is based on his nineteen years of worldwide experience with testing and test automation involving large projects with test cases executing continuously for many weeks on multiple machines.
View webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-72-big-testing
Large-scale testing projects can stress many of the testing practices we have gotten used to over the years. This can result in less than optimal outcomes. A number of ideas and concepts have therefore emerged to support industrial-strength testing of big and complex projects. In this excerpt from a larger workshop Hans Buwalda shares experiences and the strategies he and his colleagues have used for testing on large projects, both in Europe and the US. Learn how to design tests specifically for automation and how to successfully incorporate keyword testing. See how to obtain more stable automation, what benefits and issues are of virtualization, and what to expect of global outsourcing. The information presented is based on nineteen years of experience with testing and test automation including projects that have tests executing continuously for many weeks on dozens of machines.
The Challenges of BIG Testing: Automation, Virtualization, Outsourcing, and MoreTechWell
Large-scale testing projects severely stress “normal” testing practices. This can result in a number of less than optimal results. A number of innovative ideas and concepts have emerged to support industrial-strength testing of large and complex projects—some successful and others not so successful. Hans Buwalda shares his experiences and the strategies he's developed over the years for large testing on large projects. He describes the possibilities and pitfalls of outsourcing test automation. Learn how to design tests specifically for automation, and how to successfully incorporate keyword testing. The automation discussion will include virtualization and cloud options, how to deal with numerous versions and configurations common to large projects, and how to handle the complexity added by mobile devices. Hans’ information is based on his nineteen years of worldwide experience with testing and test automation involving large projects with test cases executing continuously for many weeks on multiple machines.
The Challenges of BIG Testing: Automation, Virtualization, Outsourcing, and MoreTechWell
Large-scale and complex testing projects can stress the testing and automation practices we have learned through the years, resulting in less than optimal outcomes. However, a number of innovative ideas and concepts are emerging to better support industrial-strength testing for big projects. Hans Buwalda shares his experiences and presents strategies for organizing and managing testing on large projects. Learn how to design tests specifically for automation, including how to incorporate keyword testing and other techniques. Learn what roles virtualization and the cloud can play—and the potential pitfalls of such options. Take away tips and tricks to make automation more stable, and to deal with the numerous versions and configurations common in large projects. Hans also describes the main challenges with global teams including time zones and cultural differences, and offers seven common problem "patterns" in globalization and what you can do to address them.
Better Test Designs to Drive Test Automation ExcellenceTechWell
Test execution automation is often seen as a technical challenge-a matter of applying the right technology, tools, and smart programming talent. However, such efforts and projects often fail to meet expectations with results that are difficult to manage and maintain-especially for large and complex systems. Hans Buwalda describes how the choices you make for designing tests can make-or break-a test automation project. Join Hans to discover why good automated tests are not the same as the automation of good manual tests and how to break down tests into modules-building blocks-in which each has a clear scope and purpose. See how to design test cases within each module to reflect that module's scope and nothing more. Hans explains how to tie modules together with a keyword-based test automation framework that separates the automation details from the test itself to enhance maintainability and improve ROI.
Model-based testing can be a powerful alternative to just writing test cases. However, modeling tools are specialized and not suitable for everyone. On the other hand, keyword-driven test automation has gained wide acceptance as a powerful way to create maintainable automated tests, and, unlike models, keywords are simple to use. Hans Buwalda demonstrates different ways that keyword testing and models can be combined to make model-based testing more readily accessible. Learn how you can use keywords to create the models directly. The results of this "poor man's approach" to model-based testing are clean, concise test cases that are interpreted dynamically. In other words, the model executes the tests rather than generating the tests for execution by another tool. This allows the model to actively respond to changing conditions in the application under test. See this demonstrated with a simple state-transition model, written with keywords, that plays a game until all relevant situations have been visited.
The document discusses augmenting automated testing with an action-based testing methodology. It describes creating modular, reusable tests at a higher level of abstraction than traditional coded UI tests. Tests are composed of keywords and actions that can be maintained independently of the application under test. This allows quickly creating many tests and maintaining them when the application changes. It also improves reusability, scalability, and team collaboration on testing.
When you're responsible for testing, it's almost a given that you will find yourself in a situation in which you feel alone and out in the cold. Management’s commitment for testing might be lacking, your colleagues in the project might be ignoring you, your team members might lack motivation, or the automated testing you had planned is more complicated and difficult than you anticipated. You feel you can't test enough, and you will be blamed for post-release quality problems. Hans Buwalda shares a number of chilly situations and offers suggestions for overcoming them, based on his experiences worldwide in large projects. Specifically, Hans focuses on management commitment, politics, project dependencies, managing expectations, motivating team members, testing and automation difficulties, and dealing with overwhelming numbers of day-to-day problems. Take away more than forty-five tips and approaches to use when temperatures drop on you.
Test Design Essentials for Great Test Automation - HansSauce Labs
Whether you work on a traditional or a modern Agile/DevOps project, many test automation practitioners find that automated tests can be cumbersome and costly to manage and maintain. An often overlooked factor is the lack of test design. Most organizations are unaware the critical role that test design can play in making automation scalable and maintainable.
In this joint webinar, Hans Buwalda, CTO of LogiGear and Titus Fortner of Sauce Labs discuss how one can use best practices to create well-organized tests that are easy to read and can be automated in an efficient and maintainable way.
The Challenges of BIG Testing: Automation, Virtualization, Outsourcing, and MoreTechWell
Large-scale and complex testing projects can stress the testing and automation practices we have learned through the years, resulting in less than optimal outcomes. However, a number of innovative ideas and concepts are emerging to better support industrial-strength testing for big projects. Hans Buwalda shares his experiences and strategies he's developed for organizing and managing testing on large projects. Learn how to design tests specifically for automation, including how to incorporate keyword testing and other techniques. Learn what roles virtualization and the cloud can play, and the potential pitfalls of such options. Take away tips and tricks to make automation more stable, and to deal with the numerous versions and configurations common in large projects. Hans also describes the main challenges with global teams including time zones and cultural differences, and offers seven common problem "patterns," and what you can do to address them.
Test design automation automates the testing process to improve efficiency and customer satisfaction. It is becoming more important as development speeds increase. While manual testing and HPE ALM are still common, the market is shifting toward more automated and model-based testing using techniques like AI and machine learning. Vendors must focus on automation and integration with various tools and environments.
Patterns—proven, repeatable solutions to common situations that occur again and again—are commonly used in development and to a lesser extent in testing. In addition to patterns, various anti-patterns have been discovered. These are common responses to recurring problems that, while promising, are actually counterproductive. Hans Buwalda describes a set of such anti-patterns that he commonly sees in automated test design and that he feels inhibit scalability and maintainability. Hans discusses anti-patterns including Enter Enter Click Click, Interaction Heavy, Lifeless, Lame, Clueless and a number of others. Knowing these anti-patterns will help you spot potential bottlenecks that could make your own tests unnecessarily difficult to automate. Hans presents thirteen distinct patterns that you can look for in your tests. Feel free to bring in your own anti-patterns and situations you have experienced that you feel are counterproductive toward achieving manageable and maintainable automation.
Improving ROI with Scriptless Test AutomationMindfire LLC
This is where scriptless test automation comes into the picture. Businesses today may utilize Scriptless Test Automation to automate test cases without having to worry about the complexities of coding. It speeds up the time to learn and build code, resulting in a shorter time to market, a greater return on investment, and increased coverage with little maintenance.
What Everyone on the Team Needs to Know about Test AutomationTechWell
Test automation should be an activity that involves the entire project team—not just the testing group. Test automation is a technical testing task, and the test team benefits from the assistance of others in the organization. Jim Trentadue outlines the various testing activities with the corresponding contributions and benefits of each team member. Project managers can coordinate the effort and schedule. Business analysts can manage technical test requirements. User acceptance testers can provide proper steps and screenshots for IT personnel. Developers can write code with testability in mind. Database administrators can manage the data used in the tests and check for database effects and impacts. Jim reviews automated testing nuances and what to account for, discussing the differences between a manual and automated testing setup. With the contributions of all, the benefits of test automation will be shared by the entire project team—not just the testers.
Seven Keys to Navigating Your Agile Testing TransitionTechWell
So you’ve “gone agile” and have been relatively successful for a year or so. But how do you know how well you’re really doing? And how do you continuously improve your practices? And when things get rocky, how do you handle the challenges without reverting to old habits? You realize that the path to high-performance agile testing isn’t easy or quick. It also helps to have a guide. So consider this workshop your guide to ongoing, improved, and sustained high-performance. Join seasoned agile testing coach Bob Galen as he share lessons from his most successful agile testing transitions. You’ll explore actual team case studies for building team skills, embracing agile requirements, fostering customer interaction, building agile automation, driving business value, and testing at-scale stories of agile testing excellence. You’ll examine the mistakes, adjustments, and the successes—so you’ll learn how to react to real-world contexts. Leave with a better view of your team’s strengths, weaknesses, and where you need to focus to improve.
Saksham Sarode - Innovation Through Introspection - EuroSTAR 2012TEST Huddle
EuroSTAR Software Testing Conference 2012 presentation on Innovation Through Introspection by Saksham Sarode. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Quality Assurance & Testing in a glimpseTahmid Munaz
This presentation slide has been made in respect of our local market, demand, practice and scope for the beginners in Bangladesh.
There are many things which are need to be discussed widely, cause the points mentioned here are not covering all the stuff as it shown and in some places it depends on context and contradictory thoughts may arise unless you feel free to discuss. I just wanted to give a glimpse giving an Option to everyone to participate the presentation...
Similar to Introducing Keyword-Driven Test Automation (20)
Isabel Evans stopped drawing and painting after being told she was not very good at it, which led to a loss of confidence in her creative and professional abilities. However, she realized that attempting creative activities is important for cognitive and emotional development, and that making mistakes and learning from failures allows for growth. By reengaging with failure through art and with support from others, Isabel was able to regain confidence in her abilities and reboot her career. The document discusses different perspectives on failure and the importance of learning from mistakes.
Instill a DevOps Testing Culture in Your Team and Organization TechWell
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build ArchitectureTechWell
This document summarizes a half-day tutorial on test design for fully automated build architectures presented by Melissa Benua of mParticle at STAREAST 2018. The tutorial covered guiding principles for test design including prioritizing important and reliable tests, structuring automated pipelines around components, packages, and releases, and monitoring test results through code coverage, flaky test handling, and logging versus counters. It also included exercises mapping test cases to functional boundaries and categories of tests to pipeline stages.
System-Level Test Automation: Ensuring a Good StartTechWell
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test StrategyTechWell
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for SuccessTechWell
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your SanityTechWell
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps StrategyTechWell
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOpsTechWell
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—LeadershipTechWell
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile TeamsTechWell
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile GameTechWell
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile TeamsTechWell
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery ProcessTechWell
The document summarizes a presentation about including databases in a continuous integration/delivery process. It discusses treating database code like application code by placing it under version control and integrating databases into the DevOps software development pipeline. This allows databases to be built, tested, and released like other software through continuous integration, delivery, and deployment.
Mobile Testing: What—and What Not—to AutomateTechWell
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for SuccessTechWell
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile TransformationTechWell
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
Building RAG with self-deployed Milvus vector database and Snowpark Container...Zilliz
This talk will give hands-on advice on building RAG applications with an open-source Milvus database deployed as a docker container. We will also introduce the integration of Milvus with Snowpark Container Services.
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/albumentations
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
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.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
“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.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
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.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
1. TO
PM Tutorial
10/1/2013 1:00:00 PM
"Introducing Keyword-Driven
Test Automation"
Presented by:
Hans Buwalda
LogiGear Corporation
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073
888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
2. Hans Buwalda
LogiGear
An internationally recognized expert in testing, Hans Buwalda is a pioneer of keyword-driven
test automation, an approach now widely adopted throughout the testing industry. Originally
from the Netherlands, Hans is the CTO of LogiGear, directing the development of the successful
Action Based Testing™ methodology for keyword-driven test automation and its supporting
TestArchitect™ toolset. Prior to joining LogiGear, Hans served as project director at CMG (now
CFI).