Session slides from Future Insights Live, Vegas 2015:
https://futureinsightslive.com/las-vegas-2015/
Most API testing is a joke. We have things that resemble Unit Tests which are really integration tests which really just wrap our personal understanding in just a bit of code. And at the end of the day, we’re still not sure it works. Instead, let’s flip the entire experience around and look at it from the API consumer’s point of view and confirm that we’re solving real problems for real users. In this talk, we’ll dive into some of the benefits of Behavior Driven Development and walk through some examples.
Presentation from RTP AEM / CQ5 Meetup by Sagar Sane. This presentation provides some of the challenges and benefits of applying Test Driven Development principles to Adobe Experience Manager (AEM)/CQ5 based projects and overview of some of the tools and technologies, including Spock & Geb, which can be used for automating test cases & execution.
Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del malePietro Di Bello
In questa presentazione io e Paolo D'Incau condividiamo esperienze reali tratte da progetti dove applichiamo pratiche di Continous Delivery.
Raccontiamo di come si può far evolvere iterativamente una pipeline partendo da semplici task (build e deploy mono-ambiente) fino ad arrivare ad unica pipeline multi-ambiente ispirata allo stato dell'arte e alle lezioni che abbiamo imparato facendoci del male.
Forniamo esempi concreti, focalizzandoci sugli aspetti relativi al codice, all'infrastruttura e rapporto con gli stakeholders.
Autori: Paolo D'Incau, Pietro Di Bello
Presentation from RTP AEM / CQ5 Meetup by Sagar Sane. This presentation provides some of the challenges and benefits of applying Test Driven Development principles to Adobe Experience Manager (AEM)/CQ5 based projects and overview of some of the tools and technologies, including Spock & Geb, which can be used for automating test cases & execution.
Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del malePietro Di Bello
In questa presentazione io e Paolo D'Incau condividiamo esperienze reali tratte da progetti dove applichiamo pratiche di Continous Delivery.
Raccontiamo di come si può far evolvere iterativamente una pipeline partendo da semplici task (build e deploy mono-ambiente) fino ad arrivare ad unica pipeline multi-ambiente ispirata allo stato dell'arte e alle lezioni che abbiamo imparato facendoci del male.
Forniamo esempi concreti, focalizzandoci sugli aspetti relativi al codice, all'infrastruttura e rapporto con gli stakeholders.
Autori: Paolo D'Incau, Pietro Di Bello
This presentation provides an overview of a Test Automation Framework with BDD and Cucumber. It also includes several open-source initiatives that Rhoynar Software Consulting (www.rhoynar.com) has been working on in the fields of QA Automation and DevOps. Lastly, it also includes links to some of the open-source projects that you can use right now for your work.
- Continuous Integration Infra a la OpenStack - https://github.com/Rhoynar/ci-infra
- An Email Verification Library in Java:
https://github.com/Rhoynar/EmailVerify
- Automatic Test Generation using Selenium WebDriver, Java and TestNG
https://github.com/Rhoynar/AutoTestR
- Barebones BDD and Cucumber Framework integrated with Java Maven and TestNG:
https://github.com/Rhoynar/qa-automation
Running Automated Acceptance Tests On RancherBogdan Marian
How can you make sure your product is working as expected before going live? How can your Product Owner really shape your MVP? Acceptance tests let you define the level of expectations the application must satisfy before going live and increase the visibility over what’s working and what’s not. Automating this process leads to more time spent on developing new features instead of spending it on validating them.
This presentation was given during Tech Fest event which took place in Cluj-Napoca, Romania, on November 1st 2017.
One possible solution to ensure that your e-commerce site will not break during high-sales periods such as Black Friday or Christmas, is running JMeter distributed performance tests on Rancher.
This presentation was given during iQuest Keyboards & Mice event which took place in Craiova, Romania, on October 19th 2017.
Behavior Driven Testing - A paradigm shiftAspire Systems
This presentation showcases how BDT as an approach evolved and what are the advantages of implementing the same. It includes one of the case studies to exemplify how Aspire's BDT framework helped a F500 company in successfully implementing BDT.
This power point presentation provides details on syntax of Gherkin language and how it can be used to write accurate user acceptance criteria for user stories.
Automated Acceptance Testing (and tool choice)
Automated acceptance testing has many names: acceptance-test driven development (ATDD), story-test driven development (STDD), agile acceptance testing and, most recently, specification by example. At the heart of all these approaches is to produce business-facing tests which are system tests running end-to-end, picking up regression issues and improving confidence that the code works as required.
In this talk, I will contextualise how each of these approaches share in common a three-tier layering strategy: acceptance criteria, test implementation layer and application driver layer. This is important because applying this approach requires a tool choice and each tool tends to have its own sweet (and blind) spot that is best understood through these layers.
I will first deep dive into sample code across a few tools (Cucumber, Fitnesse, Concordion) to illustrate this layering. I use an example that shows how to decouple the GUI from tests (window driver pattern).
Finally, I will look at some typical client scenarios to examine which tools might best suited because tool choice is not simply a host operating system question (.Net, Java, Ruby).
DevQA: make your testers happier with Groovy, Spock and Geb (Greach 2014)Alvaro Sanchez-Mariscal
Writing functional tests using Geb in a Grails application is fine for a development team. But when you have QA automation engineers, giving them access to the Grails app might not be the best solution (specially when they belong to a different team).
So the same way DevOps allow developers and sysadmins collaborate together, let’s talk about DevQA, and make them happy using a framework stack powered by Groovy.
Besides above considerations, in this talk I will show a live example on how to setup an independent project for functional tests using Gradle, Groovy, Spock and Geb.
Sharing (less) Pain of using Protractor & WebDriverAnand Bagmar
Slides from my talk in Selenium Conference London 2016 about "Sharing (Less) Pain with Protractor & Selenium WebDriver"
See blog for more information - http://essenceoftesting.blogspot.com/2016/11/shared-relatively-less-pain-of-using.html
My blog: https://essenceoftesting.blogspot.com
The wild wild west of Selenium CapabilitiesAdi Ofri
Not all desired capabilities where born equal:
– Some were born in the world of open source, while others were born as vendor proprietary properties.
– Some are mandatory, and some are optional.
– Some are clear and deterministic, others are vague and require reading and experimentation.
– Some make it easy to change vendors without breaking a sweat, while some will lock you into a specific implementation.
This presentation provides an overview of a Test Automation Framework with BDD and Cucumber. It also includes several open-source initiatives that Rhoynar Software Consulting (www.rhoynar.com) has been working on in the fields of QA Automation and DevOps. Lastly, it also includes links to some of the open-source projects that you can use right now for your work.
- Continuous Integration Infra a la OpenStack - https://github.com/Rhoynar/ci-infra
- An Email Verification Library in Java:
https://github.com/Rhoynar/EmailVerify
- Automatic Test Generation using Selenium WebDriver, Java and TestNG
https://github.com/Rhoynar/AutoTestR
- Barebones BDD and Cucumber Framework integrated with Java Maven and TestNG:
https://github.com/Rhoynar/qa-automation
Running Automated Acceptance Tests On RancherBogdan Marian
How can you make sure your product is working as expected before going live? How can your Product Owner really shape your MVP? Acceptance tests let you define the level of expectations the application must satisfy before going live and increase the visibility over what’s working and what’s not. Automating this process leads to more time spent on developing new features instead of spending it on validating them.
This presentation was given during Tech Fest event which took place in Cluj-Napoca, Romania, on November 1st 2017.
One possible solution to ensure that your e-commerce site will not break during high-sales periods such as Black Friday or Christmas, is running JMeter distributed performance tests on Rancher.
This presentation was given during iQuest Keyboards & Mice event which took place in Craiova, Romania, on October 19th 2017.
Behavior Driven Testing - A paradigm shiftAspire Systems
This presentation showcases how BDT as an approach evolved and what are the advantages of implementing the same. It includes one of the case studies to exemplify how Aspire's BDT framework helped a F500 company in successfully implementing BDT.
This power point presentation provides details on syntax of Gherkin language and how it can be used to write accurate user acceptance criteria for user stories.
Automated Acceptance Testing (and tool choice)
Automated acceptance testing has many names: acceptance-test driven development (ATDD), story-test driven development (STDD), agile acceptance testing and, most recently, specification by example. At the heart of all these approaches is to produce business-facing tests which are system tests running end-to-end, picking up regression issues and improving confidence that the code works as required.
In this talk, I will contextualise how each of these approaches share in common a three-tier layering strategy: acceptance criteria, test implementation layer and application driver layer. This is important because applying this approach requires a tool choice and each tool tends to have its own sweet (and blind) spot that is best understood through these layers.
I will first deep dive into sample code across a few tools (Cucumber, Fitnesse, Concordion) to illustrate this layering. I use an example that shows how to decouple the GUI from tests (window driver pattern).
Finally, I will look at some typical client scenarios to examine which tools might best suited because tool choice is not simply a host operating system question (.Net, Java, Ruby).
DevQA: make your testers happier with Groovy, Spock and Geb (Greach 2014)Alvaro Sanchez-Mariscal
Writing functional tests using Geb in a Grails application is fine for a development team. But when you have QA automation engineers, giving them access to the Grails app might not be the best solution (specially when they belong to a different team).
So the same way DevOps allow developers and sysadmins collaborate together, let’s talk about DevQA, and make them happy using a framework stack powered by Groovy.
Besides above considerations, in this talk I will show a live example on how to setup an independent project for functional tests using Gradle, Groovy, Spock and Geb.
Sharing (less) Pain of using Protractor & WebDriverAnand Bagmar
Slides from my talk in Selenium Conference London 2016 about "Sharing (Less) Pain with Protractor & Selenium WebDriver"
See blog for more information - http://essenceoftesting.blogspot.com/2016/11/shared-relatively-less-pain-of-using.html
My blog: https://essenceoftesting.blogspot.com
The wild wild west of Selenium CapabilitiesAdi Ofri
Not all desired capabilities where born equal:
– Some were born in the world of open source, while others were born as vendor proprietary properties.
– Some are mandatory, and some are optional.
– Some are clear and deterministic, others are vague and require reading and experimentation.
– Some make it easy to change vendors without breaking a sweat, while some will lock you into a specific implementation.
Adobe Air Application case study - nycoders.org 0509Andrew Hunt
The slides from the presentation I gave with Joe Ferrari on May 9, 2012 at nycoders.org.
We did a case study of an Adobe AIR app we built for iPad and discussed the troubles we encountered (many!) and our solutions.
CyberArk Impact 2017 - REST for the Rest of UsJoe Garcia
Are you a Vault Admin drowning in work? Unfortunately, the great minds at CyberArk haven’t figured out a way to clone you… yet. In the meantime, there’s the REST API to help you along the way!
Come POST up in a chair and GET your paper and pencils ready…our REST expert is about to PUT knowledge in your brain and DELETE your old way of thinking! After this session, you’ll leave with a better understanding of our REST API, how to easily combine multiple methods to create simple scripts, and tips on how to use Postman to your benefit.
Creating a World-Class RESTful Web Services APIDavid Keener
Companies like Amazon, Google and Yahoo have published web services API's that empower developers to create mash-ups, add-ons and full-scale applications. The creation of such API's, however, is not exclusively the domain of large, multi-national corporations. Learn how to architect, build and field a well-designed and scalable RESTful web services API that will allow your business to leverage the capabilities of the developer community. This presentation includes real-life examples from the Grab Networks RESTful API, which provides access to information about the hundreds of thousands of news videos available through Grab Networks' distribution network.
Dominik Veselý - Vše co jste kdy chtěli vědět o CI a báli jste se zeptatmdevtalk
Continuous Integration je velice důležité, leč často opomíjené téma. Většina lidí má tento termín zažitý jako něco co je složité a patří to do velkých společností. Opak je pravdou, CI můžete využívat i jako freelancer nebo malá společnost velice jednoduše. Ať už ho chcete používat k testování, nasazování, doručování buildu nebo notifikacím, ušetří Vám to hodně času a peněz. Dominik se věnuje problematice CI pro mobilní vývoj již více jak 2 roky a se svými kolegy vyrobil CI pipeline pro iOS, Android i backend, která šetří stovky minut denně celému týmu. Ve svém talku se zaměří, jak na mobilní platformy, tak na backendy a frontendy, aby si na své přišel opravdu každý.
On April 10, 2013, Eric Mattison gave a talk on Tastypie: Easy APIs to Make Your Work Easier.
"Have you ever dealt with any of these problems:
- Unwieldy, Scary-to-Change Applications?
- Long Development Cycles?
- Replicated Code?
- Scope Creep?
- Restless Leg Syndrome?
Tastypie can help you solve these problems and more!”
The case for writing API-first applications.
Good developers try to make their jobs as easy as possible. We know our application will evolve, so we try to make future changes as simple as possible by layering and decoupling our architecture up front. That's great, but can we do more?
In this session, I try to convince you that an API should be the most important part of your application. By focusing on the API first, you'll reap huge benefits in support and bug fixing, and you'll open your application up to nearly limitless new features with minimal effort.
I look at some applications that expose great APIs, and what benefits they've seen as a result. I examine the practicalities of an API-first design, and how to avoid some of the common pitfalls. Finally, I put it all into practice and write a short demo app - API first.
Don't hate, automate. lessons learned from implementing continuous deliverySolano Labs
This presentation on Continuous Delivery is from the November 2013 Automated Testing San Francisco meetup that took place at Constant Contact. The author/presenter is Matt Wilson, CTO of Lab Zero. Matt has advised clients at various industries including consumer brands, non-profits, start-ups, and financial services on Agile development, web application development, and other technology leadership challenges. This overview on Continuous Delivery highlights some of the best practices that Lab Zero has distilled, based on their many client engagements.
---
About Matt Wilson:
Matt is an enthused agile developer, architect, and consultant. He enjoys building elegant web services in Ruby. He believes that high-fives are underrated and measures the success of his day by how many he's seen.
Prior to joining Lab Zero, Matt's work history includes: Co-founder/Architect at Earfl.com, Architect at Kodak Gallery, Developer at Westwave Communications, Engineer at Motorola, and Developer at Coldwell Banker.
About Lab Zero:
Lab Zero Innovations, Inc. provides web application development and technology leadership consulting. Our client relationships include staff augmentation, pure software development, project management, system integration, advisor/leadership roles. Contact us about your next project.
A Universal Theory of Everything, Christopher MurphyFuture Insights
Taken from the Future of Web Design, New York 2015 Conference. https://futureofwebdesign.com/nyc-2015/
Drawing on over two decades of experience designing and developing digital products, Christopher will walk you through everything he's learned along the way. He'll break apart the creative process, exploring how an understanding of that process, leads you to become a better designer. In this session, he'll explore how the best designers: firstly 'prime the brain' by ensuring it is constantly nourished with new material; then explore that material from multiple perspectives to gain a deep understanding of it; before, finally, putting those pieces back together again to create exciting new ideas that stand the test of time. In short, he'll ensure you leave the session fully creativity-hardened and never short of ideas again.
Horizon Interactive Awards, Mike Sauce & Jeff JahnFuture Insights
Taken from the Future of Web Design, San Francisco 2015 Conference. https://futureofwebdesign.com/san-francisco-2015/
Mike Sauce, Founder and President of the Horizon Interactive Awards will present an award to the Most Awarded Developer in the 13th annual competition to DynamiX Web Design. Jeff Jahn, owner and founder of DynamiX, will discuss design trends, processes and technologies that led his company to achieve such a high honor in the Horizon Interactive Awards competition.
Reading Your Users’ Minds: Empiricism, Design, and Human Behavior, Shane F. B...Future Insights
Taken from the Future of Web Design, New York 2015 Conference. https://futureofwebdesign.com/nyc-2015/
How do you decide what your users really need? The difficult truth is that the best web design comes from finding out for yourself. Luckily for anyone passionate about improving web-based human interaction, the field of psychology can shed light on common motivations, needs, and biases that are powerful influences on human behavior. In this session, you’ll learn about how these psychological forces—such as prospect theory, metacognitive fluency, and the introspection illusion—can shed light on UX, design, and conversion.
Structuring Data from Unstructured Things. Sean LorenzFuture Insights
From FOWA Boston 2015
Structuring Data from Unstructured Things. Sean Lorenz
Data coming from Internet of Things (IoT) product sensors can be hard to manage or know what to do with. In this talk Sean will discuss ways to tame IoT data sources by organizing and pruning that information effectively. He will also discuss the importance of time series when culminating sensor, metadata and other data sources together, making it vastly easier to query or perform analytics on your newly structured data.
Taken from the Future of Web Design, New York 2015 Conference. https://futureofwebdesign.com/nyc-2015/
The process behind making a blockbuster film is similar to creating a meaningful website or app. Through the lens of cinema, we’ll walk through practical ways that UX design teams can work together to deliver an award-winning final product. Whether you’re making a low-budget indie for a non-profit or the next summer smash for a Fortune 500, we can learn a thing or two from film.
Taken from the Future of Web Design, San Francisco 2015 Conference. https://futureofwebdesign.com/san-francisco-2015/
In the last few years, we’ve seen an emergence of a modular way of thinking about code and design. We’ve seen the rise of SMACSS, BEM, and Atomic Design. This talk will look at those modular concepts and how they can streamline development for large and long-running projects. We’ll also look at how these approaches can ease responsive design and development. Lastly, we will look at where the modular approach is going in the future as Web Components slowly make their way into browsers and application frameworks.
Designing an Enterprise CSS Framework is Hard, Stephanie RewisFuture Insights
Taken from the Future of Web Design, San Francisco 2015 Conference. https://futureofwebdesign.com/san-francisco-2015/
It seems that not a week goes by without a shiny new framework of some type — be it CSS or JS. But no matter how awesome they are, each have shortcomings and idiosyncrasies that invariably make you ask, 'Why?' Now imagine someone gave you the ability to start from scratch to create your own framework. No strings. No preconceptions — well, except that it has to be enterprise scale, platform agnostic, and work in a whole host of disparate situations. In this session, Stephanie will talk about some of the challenges, hurdles, tradeoffs, and unique decisions Salesforce UX made on the way to building an enterprise framework.
Accessibility Is More Than What Lies In The Code, Jennison AsuncionFuture Insights
Taken from the Future of Web Design, San Francisco 2015 Conference. https://futureofwebdesign.com/san-francisco-2015/
Many associate making a digital product accessible with the guidelines and specifications that address themselves at the code-level. In short, the developers/engineers will take care of it. While the thoughtful implementation of accessible code during the development phase is unquestionable, the truth is accessibility depends heavily on choices made by designers and others involved in determining the user experience, and typically before development begins. Join Jennison as he illustrates this by identifying some of the user interactions and design-related decisions that can pose accessibility challenges. He will also share practical advice for those seeking to scale accessibility and make it a shared responsibility.
Sunny with a Chance of Innovation: A How-To for Product Managers and Designer...Future Insights
Taken from the Future of Web Design, San Francisco 2015 Conference. https://futureofwebdesign.com/san-francisco-2015/
Growth stage companies need to continue to be as innovative as they were as smaller startups - but how do you actually do it? How can product leaders and designers de-risk valuable new ideas and get the support required to actually execute? From the perspective of a product owner and a designer respectively, Audrey and Alexa will walk through how they ran an innovation team on a recent project. They'll discuss how they rallied a broader group of stakeholders around big and risky ideas, testing the limits of experimentation, and turning small-scale experimental code into real life features. Thinking big and executing in layers is the future of innovation. You will walk away with some easy methods to start launching experiments at your company, regardless of whether you come from a three-person startup or a huge corporation.
Taken from the Future of Web Design, New York 2015 Conference. https://futureofwebdesign.com/nyc-2015/
The future must be universally approachable. In this talk, Andrew looks at designing for dyslexic users. Learn how to create designs that are more universal; designs that not only better fit dyslexics, but are a better fit for everyone regardless of race, religion, national origin, language or ability.
Taken from the Future of Web Design, San Francisco 2015 Conference. https://futureofwebdesign.com/san-francisco-2015/
Site analytics. The quantified self. Big data. Human activity is creating more and more measurable data. But is more data really helping designers make better decisions? Human problems often require illogical approaches. In order to meet real human needs, we need to approach the data we collect with empathy and find the story in the facts.
Taken from the Future of Web Design, San Francisco 2015 Conference. https://futureofwebdesign.com/san-francisco-2015/
We need to create processes that get us away from nice looking design files to actually shipping our projects into the real world.
FOWA London 2015
In recent years there have been incredible advances in artificial intelligence and deep learning. As a result, powerful technology which used to be rare and expensive has very quickly become easily available and cheap. This will have both positive and negative consequences for web developers. In this talk I will look at how AI will change the development field, and provide techniques that will help designers and developers to work with AI to improve their skills and make better sites and applications for end users.
Digital Manuscripts Toolkit, using IIIF and JavaScript. Monica Messaggi KayaFuture Insights
FOWA London 2015
Monica is part of the DMT project at the Bodleian Libraries (University of Oxford) that aims to create a toolkit using IIIF standard (http://iiif.io) for images, a server solution (to store images of manuscripts and metadata), and a client solution using JavaScript to build an authoring tool that allows editing the manuscript manifest and its metadata. Working specifically on the authoring tool, and on the challenges that different types of manifests presents for the developer. You will have a glimpse of the whole picture and then she taps into the libraries used, choices made, collaboration experiences and lessons learned so far.
7. Assumption:
You have a technical background
APIs are an important part of your job
Use them on a regular basis
Potentially build them too
Sometimes public, sometimes private
15. Behavior Driven Development
Standard Definition:
BDD is a synthesis and refinement of practices stemming
from TDD and ATDD.
Dan North’s Definition (circa 2009):
BDD is a second-generation, outside-in, pull-based,
multiple-stakeholder, multiple-scale, high-automation, agile
methodology. It describes a cycle of interactions with well-
defined outputs, resulting in the delivery of working, tested
software that matters.
16. Get your head out of the system!
What it really means..
17. What it looks like
As a [role] I want [feature] so that [benefit]
18. Well to be more precise
It’s English, but in the Gherkin syntax so this:
As a [role] I want [feature] so that [benefit]
becomes a feature called:
Given [condition] when I [action] then [result]
22. For Clarify.io
The first thing that anyone does:
Creates a bundle (audio or video package)
We need a file (audio in this case)
We need an API key
We need to submit it (POST)
We need to check the results (201 Created)
35. And then…?
Write the feature
Refactor to reuse when possible
Add the left over bits
GOAL: You should be writing less and less code!
36. Our Status
We validate the Helper Libraries with this too
Feature tests for the API using:
Using the PHP library
Using the Python library
Using the Ruby library (newest)
(publicly launching our tests this month here: https://github.com/Clarify )