Reaching for Your Quality Stretch Goals: Testing at Realtor.comKlaus Salchner
A/B Testing
If you are not familiar yet, an introduction to A/B testing and how you can leverage this approach to truly measure customer impact before and after a change. It's a practice highly leveraged in the e-commerce and cloud space to truly measure the impact of a change and be able to iterate through it till you see the desired outcome.
Where in your stack to invest in test automation
This short talk will explain in which layer to invest in test automation and the pros and cons. Too many teams still invest heavily in automated UI testing which then results in large test automation suites once the platform grows while still not being able to catch critical quality issues before they reach customers.
Testing for reliability, resilience and recovery
Your customer experience is also impacted by how reliable your application is. How do you test for reliability. But also how do you build and test for resilience, as guaranteed reliability is unachievable and the closer you get the costlier it becomes. Lastly how do you test for recovery, so once an outage or partial outage happened how to you recover, and how do you prepare for that recovery.
Learn how you can use the Test Pyramid from Mike Cohn to guide how to scale your QA test automation while keeping it effective and fast. As your product and team scales it is really important to have a solid framework in place which allows your test automation to scale for the various layers of your product and your teams.
The document discusses test automation architecture and strategies for building an effective test automation pyramid. It recommends starting with unit tests at the base to test individual classes in isolation using mocks and stubs. Integration and API tests should be the next focus to test application logic through service calls. GUI tests should be limited to a fixed number of end-to-end tests while avoiding fragile tests. Cross-functional involvement from different teams is also important for maintaining tests. The goal is to have a stable, well-designed test automation strategy that finds bugs efficiently without wasting resources on fragile tests.
This document discusses continuous delivery of software. It defines continuous delivery as building, testing, and releasing software faster and more frequently while ensuring the software can be reliably released at any time to reduce costs and risks. Continuous delivery is compared to continuous deployment. Several large companies that practice continuous deployment, releasing software many times per day, are listed. The key aspects of continuous delivery workflows are described, including integration testing, a testing pyramid, feature toggles/branching, production-like environments, deployment pipelines for visibility, feedback and continual deployments without downtime, rollback capabilities, and close team collaboration. Advantages are highlighted such as reduced deployment risks, believable progress improving customer satisfaction, user feedback building better products, and improved quality.
• Build better apps for any platform, including iOS, Android, Java, Linux or Windows with DevOps.
• Accelerate your application delivery lifecycle with DevOps.
• Let teams share code, track work, and ship software—for any language, all in a single package. It is the perfect complement to your IDE.
AUTOMATION FRAMEWORK USING SELENIUM & TESTNG ALONG WITH MAVENSHASHI JAISWAL
We are creating an automation framework with the help of Selenium andTestNG software in which we are testing Facebook basic functionalities like:-
1 automatic login-logout
2 Friend list check
3 Invalid login
This document discusses how to reduce the costs of integrating OpenStack and NFV platforms through OPNFV. It proposes:
1. Simplifying the integration process to reduce learning costs and make installer selection faster through a single command deployment option for both virtual and bare-metal environments.
2. Focusing on NFV scenario value rather than integration complexity to improve user experience and success rates.
3. Providing templates for common configurations that are supported by different installers to standardize deployments and minimize development work.
This document introduces performance testing. It discusses what performance testing is, why it is needed, and when to perform tests. It also outlines the performance testing process and different types of performance tests, including capacity/volume testing, spike testing, stress testing, and load testing. The goal of performance testing is to determine a software program's speed, effectiveness, responsiveness, reliability, throughput, and scalability under different workloads.
Reaching for Your Quality Stretch Goals: Testing at Realtor.comKlaus Salchner
A/B Testing
If you are not familiar yet, an introduction to A/B testing and how you can leverage this approach to truly measure customer impact before and after a change. It's a practice highly leveraged in the e-commerce and cloud space to truly measure the impact of a change and be able to iterate through it till you see the desired outcome.
Where in your stack to invest in test automation
This short talk will explain in which layer to invest in test automation and the pros and cons. Too many teams still invest heavily in automated UI testing which then results in large test automation suites once the platform grows while still not being able to catch critical quality issues before they reach customers.
Testing for reliability, resilience and recovery
Your customer experience is also impacted by how reliable your application is. How do you test for reliability. But also how do you build and test for resilience, as guaranteed reliability is unachievable and the closer you get the costlier it becomes. Lastly how do you test for recovery, so once an outage or partial outage happened how to you recover, and how do you prepare for that recovery.
Learn how you can use the Test Pyramid from Mike Cohn to guide how to scale your QA test automation while keeping it effective and fast. As your product and team scales it is really important to have a solid framework in place which allows your test automation to scale for the various layers of your product and your teams.
The document discusses test automation architecture and strategies for building an effective test automation pyramid. It recommends starting with unit tests at the base to test individual classes in isolation using mocks and stubs. Integration and API tests should be the next focus to test application logic through service calls. GUI tests should be limited to a fixed number of end-to-end tests while avoiding fragile tests. Cross-functional involvement from different teams is also important for maintaining tests. The goal is to have a stable, well-designed test automation strategy that finds bugs efficiently without wasting resources on fragile tests.
This document discusses continuous delivery of software. It defines continuous delivery as building, testing, and releasing software faster and more frequently while ensuring the software can be reliably released at any time to reduce costs and risks. Continuous delivery is compared to continuous deployment. Several large companies that practice continuous deployment, releasing software many times per day, are listed. The key aspects of continuous delivery workflows are described, including integration testing, a testing pyramid, feature toggles/branching, production-like environments, deployment pipelines for visibility, feedback and continual deployments without downtime, rollback capabilities, and close team collaboration. Advantages are highlighted such as reduced deployment risks, believable progress improving customer satisfaction, user feedback building better products, and improved quality.
• Build better apps for any platform, including iOS, Android, Java, Linux or Windows with DevOps.
• Accelerate your application delivery lifecycle with DevOps.
• Let teams share code, track work, and ship software—for any language, all in a single package. It is the perfect complement to your IDE.
AUTOMATION FRAMEWORK USING SELENIUM & TESTNG ALONG WITH MAVENSHASHI JAISWAL
We are creating an automation framework with the help of Selenium andTestNG software in which we are testing Facebook basic functionalities like:-
1 automatic login-logout
2 Friend list check
3 Invalid login
This document discusses how to reduce the costs of integrating OpenStack and NFV platforms through OPNFV. It proposes:
1. Simplifying the integration process to reduce learning costs and make installer selection faster through a single command deployment option for both virtual and bare-metal environments.
2. Focusing on NFV scenario value rather than integration complexity to improve user experience and success rates.
3. Providing templates for common configurations that are supported by different installers to standardize deployments and minimize development work.
This document introduces performance testing. It discusses what performance testing is, why it is needed, and when to perform tests. It also outlines the performance testing process and different types of performance tests, including capacity/volume testing, spike testing, stress testing, and load testing. The goal of performance testing is to determine a software program's speed, effectiveness, responsiveness, reliability, throughput, and scalability under different workloads.
How to make a Load Testing with Visual Studio 2012Chen-Tien Tsai
About Load Testing
Performance testing
Stress testing
Load testing
Create Visual Studio Load Testing Solution
Add Web Perfomance Testing
Create by Wizard(record action)
Create by Code
Add Load Testing
Configure Scenario setting
Configuration Run setting
Open Load Testing Report
Tips for setting
One more thing about Load Testing
This document discusses key factors for ensuring the success of a test automation framework (TAF). It outlines various elements that should be considered when setting up a TAF, including supporting different application types like web, mobile, and APIs. Important TAF features that are described include being keyword/data-driven, handling test flows and errors, and generating execution and historical reports. The document also provides recommendations for integrating the TAF with continuous integration systems for scheduling tests, notifications, load balancing and distributed execution to save time.
QualiTest provides load and performance testing services to determine a system's behavior under normal and peak load conditions. Their testing process identifies maximum operating capacity and elements that cause degradation. They ensure applications can handle predicted traffic volumes. QualiTest uses various load testing tools and methodologies to simulate real-world usage and stress test systems. Their testing delivers reports on defects, tool evaluations, and ongoing support for quality improvement.
How to Cover All Your Backend Testing Needs with API and UI TestsBlazeMeter
The document discusses API and UI testing and provides guidance on when each type of test should be used. It defines API testing as testing the backend functionality and performance by analyzing hits/second versus response times, while UI testing verifies user scenarios and response times using Selenium. The document recommends using API tests as part of continuous integration builds, before adding new services, and for staging performance tests, while recommending UI tests before major releases and events. It also provides an overview of how testing can integrate into the application lifecycle from unit testing to production load testing.
This document discusses test automation within a Scrum process. It begins by providing background on the author and defining test automation. It then discusses how to start with automation, including using frameworks and learning programming skills. It describes how to plan test automation in a Scrum process, including when to automate, criteria for choosing what to automate, and how to plan the automation work. The document then discusses automating test cases, executing automation scripts, and delivering the automation work in a Scrum process. Finally, it briefly discusses some newer trends in test automation.
5 Considerations When Adopting Automated TestingBhupesh Dahal
Most organizations have realized the benefits of and need for test automation—but is your investment being wisely utilized? Are you unknowingly building a test automation suite that will end up costing more than your actual product? Are you building a legacy test automation framework that may be ready to retire before you reap the benefits?
This presentation will discuss five points of consideration that will help your organization answer these questions and mitigate risks that they bring into light.
This document discusses modular training for IBM software. It proposes creating self-contained training modules that can be combined as needed by global training partners. Each module should start with students unable to perform a task and end with them able to do so. Examples of potential modules for Apache HTTP Server are provided, along with suggestions for using virtual machines and lab exercises across modules. The challenges of product enhancements and maintaining narrative structure with modular content are also addressed.
The only way to know if your systems can handle the number of users is to load test, however load testing is hard and the infrastructure expensive. Come and see Martin demontrate the tools and techniqies that are required to test your software under load, even in Production.
This document summarizes a presentation on building a login form in WP7 using MVVM patterns. It includes sections on form validation, asynchronous web service calls, the login view, view model and using Caliburn Micro. It also discusses unit testing the login form and provides links for more information.
How We Build Confidence with Continuous Integration and Automated TestingGareth Marland
Continuous integration and automated front end testing provide a small development team confidence in their work without a dedicated testing team. The solution involves running unit tests and automated front end tests on every code check-in through a continuous integration process managed across three servers for building, testing, and staging. This allows any new features to be constantly tested as they are added, catching issues early and providing confidence that changes did not break existing functionality.
Performance testing with VSTs on- and off-premisesJeff Bramwell
Many of us have been there before... You deploy your brand new web site to production, you know, the one that's going to make your company rich and you famous, and just as you're about to hit a thousand users, the site comes crashing down! If you haven?t experienced this, chances are you know someone who has.If you're building web apps and services for your organization you know how important it is to ensure those services are always up and running. While many of us go through great lengths to ensure we are testing the functionality of our systems we do not always take performance or system load into account.Visual Studio Team Services (VSTS) provides multiple options and avenues for enabling performance and load testing for your systems. For example, did you know that VSTS also supports JMeter tests? With VSTS you can even run performance tests using on-premises servers in your own data center. This talk will give you an overview of the performance and load testing capabilities of VSTS. If you haven't looked at the load testing features of VSTS lately, you should definitely check out this talk!
Governance for AEM/CMS Projects
Document a best practice project framework
Demonstrate a successful implementation
List key lessons learned and gotchas
Help answer questions to avoid pitfalls and reduce learning curve
Bring together a community of professionals
Develop a better understanding in running projects efficiently
Enable Collaborative Development Process
How to establish ways of working that allows shifting-left of the automation ...Max Barrass
Why Automate?
Your application will grow, you will not have enough hands
You are blocked by development
Hidden factory costs of bug-fix cycle
Why Shift-Left?
More people to negate massive inspections
Define measurable success early, work on good parts.
Reduce occurrence of defects
What is this got to do with Ways of working?
Unlock capacity
Make people smile
Is not
a Department
extra cost
a final oversight or a massive inspection
someone else’s job
Is
Everyone’s responsibility
Build into the ways of working
Everyone’s job
This document summarizes a webinar about new features and the roadmap for Provar, an automated testing tool for Salesforce. Key highlights include new features like support for Lightning components, mobile testing capabilities, and a new test builder. The roadmap discusses upcoming features like a managed package and REST API support. The webinar also covers tips and how Provar helps with issues like maintaining test cases across environments and testing advanced Salesforce features.
The world of a software house is a constant search for compromise between quality and costs. In many cases, the cost-cutting starts from the test automation. Then you start to talk about ROI but recognize that numbers are not on your side. We were there and what we have found out is that only a complete change in our approach allows us to find common ground with our clients. I will reveal one detail from the presentation - we are not talking about test automation with clients anymore - as a result we do it more and more.
Are you surprised that success automatically generates new challenges which we further translate into opportunities? We had to reconsider our approach to the test automation environment, internal frameworks and the way we share them between projects, including code ownership, … And again, one simple but unobvious solution allows us to both deliver what we promise and to earn more on our projects.
As we have been reshaping our approach to the test automation, we had to change the way of delivery too. One of the main decisions was skip out the role of test automation engineer (or software developer in test). We decided to go with the whole team approach which is consistent with the way we sell it.
Find it interesting? Join me and listen to our story about how we have transformed test automation.
This document outlines sessions for a DevOps training that provides an overview of enabling business agility through DevOps practices. The sessions cover topics such as DevOps for the enterprise, building a continuous integration environment, automating deployments, automated testing and monitoring, and continuous deployment. The goals are to educate attendees on how DevOps can increase development organization agility while lowering costs. Live demos of tools like CloudFormation are included to help organizations implement similar practices.
The document discusses testing approaches in Agile development. It outlines Agile core values like prioritizing working software over documentation. It compares the Agile Testing Pyramid model which emphasizes more lightweight unit and integration testing over manual UI testing to the traditional Testing Ice Cream Cone model. It also discusses the Agile Test Quadrants framework and how test automation fits into Agile at different levels including unit, integration/service, and UI testing while maintaining a balance between development and testing. The document provides recommendations for test automation in Agile like starting small and incrementally, balancing automation costs and ROI, and keeping feedback cycles quick.
The document discusses priorities for continuous delivery including individuals and interactions over processes and tools, working software over documentation, and customer collaboration over contract negotiation. It emphasizes building, integrating, and maintaining speed through iterations. While tests and tools are mentioned, responding to change and communication are prioritized. The document concludes by returning to practicing continuous integration and delivery using tools like PaaS platforms and Kanban boards.
This document provides an overview of Microsoft Test Manager (MTM) 2013 and how to use it for test planning, test case management, test runs, exploratory testing, and lab management. Key capabilities covered include creating test plans and test suites, managing manual and automated test cases, running tests and recording results, performing exploratory testing sessions, and setting up and using lab environments to collect diagnostic data during testing. The document demonstrates these capabilities through examples and screenshots.
Ahmed Omar is a software quality team lead with over 9 years of experience in manual and automated testing using tools like Selenium, JMeter, and Microsoft Test Manager. He has worked as a senior QA engineering and testing team lead for multiple companies, leading teams and managing the full SDLC, including test planning, case design, defect tracking, and ensuring coverage of functional, performance, stress, and other testing types. Omar has a bachelor's degree in computer science and certifications in software testing and SQL administration.
How to make a Load Testing with Visual Studio 2012Chen-Tien Tsai
About Load Testing
Performance testing
Stress testing
Load testing
Create Visual Studio Load Testing Solution
Add Web Perfomance Testing
Create by Wizard(record action)
Create by Code
Add Load Testing
Configure Scenario setting
Configuration Run setting
Open Load Testing Report
Tips for setting
One more thing about Load Testing
This document discusses key factors for ensuring the success of a test automation framework (TAF). It outlines various elements that should be considered when setting up a TAF, including supporting different application types like web, mobile, and APIs. Important TAF features that are described include being keyword/data-driven, handling test flows and errors, and generating execution and historical reports. The document also provides recommendations for integrating the TAF with continuous integration systems for scheduling tests, notifications, load balancing and distributed execution to save time.
QualiTest provides load and performance testing services to determine a system's behavior under normal and peak load conditions. Their testing process identifies maximum operating capacity and elements that cause degradation. They ensure applications can handle predicted traffic volumes. QualiTest uses various load testing tools and methodologies to simulate real-world usage and stress test systems. Their testing delivers reports on defects, tool evaluations, and ongoing support for quality improvement.
How to Cover All Your Backend Testing Needs with API and UI TestsBlazeMeter
The document discusses API and UI testing and provides guidance on when each type of test should be used. It defines API testing as testing the backend functionality and performance by analyzing hits/second versus response times, while UI testing verifies user scenarios and response times using Selenium. The document recommends using API tests as part of continuous integration builds, before adding new services, and for staging performance tests, while recommending UI tests before major releases and events. It also provides an overview of how testing can integrate into the application lifecycle from unit testing to production load testing.
This document discusses test automation within a Scrum process. It begins by providing background on the author and defining test automation. It then discusses how to start with automation, including using frameworks and learning programming skills. It describes how to plan test automation in a Scrum process, including when to automate, criteria for choosing what to automate, and how to plan the automation work. The document then discusses automating test cases, executing automation scripts, and delivering the automation work in a Scrum process. Finally, it briefly discusses some newer trends in test automation.
5 Considerations When Adopting Automated TestingBhupesh Dahal
Most organizations have realized the benefits of and need for test automation—but is your investment being wisely utilized? Are you unknowingly building a test automation suite that will end up costing more than your actual product? Are you building a legacy test automation framework that may be ready to retire before you reap the benefits?
This presentation will discuss five points of consideration that will help your organization answer these questions and mitigate risks that they bring into light.
This document discusses modular training for IBM software. It proposes creating self-contained training modules that can be combined as needed by global training partners. Each module should start with students unable to perform a task and end with them able to do so. Examples of potential modules for Apache HTTP Server are provided, along with suggestions for using virtual machines and lab exercises across modules. The challenges of product enhancements and maintaining narrative structure with modular content are also addressed.
The only way to know if your systems can handle the number of users is to load test, however load testing is hard and the infrastructure expensive. Come and see Martin demontrate the tools and techniqies that are required to test your software under load, even in Production.
This document summarizes a presentation on building a login form in WP7 using MVVM patterns. It includes sections on form validation, asynchronous web service calls, the login view, view model and using Caliburn Micro. It also discusses unit testing the login form and provides links for more information.
How We Build Confidence with Continuous Integration and Automated TestingGareth Marland
Continuous integration and automated front end testing provide a small development team confidence in their work without a dedicated testing team. The solution involves running unit tests and automated front end tests on every code check-in through a continuous integration process managed across three servers for building, testing, and staging. This allows any new features to be constantly tested as they are added, catching issues early and providing confidence that changes did not break existing functionality.
Performance testing with VSTs on- and off-premisesJeff Bramwell
Many of us have been there before... You deploy your brand new web site to production, you know, the one that's going to make your company rich and you famous, and just as you're about to hit a thousand users, the site comes crashing down! If you haven?t experienced this, chances are you know someone who has.If you're building web apps and services for your organization you know how important it is to ensure those services are always up and running. While many of us go through great lengths to ensure we are testing the functionality of our systems we do not always take performance or system load into account.Visual Studio Team Services (VSTS) provides multiple options and avenues for enabling performance and load testing for your systems. For example, did you know that VSTS also supports JMeter tests? With VSTS you can even run performance tests using on-premises servers in your own data center. This talk will give you an overview of the performance and load testing capabilities of VSTS. If you haven't looked at the load testing features of VSTS lately, you should definitely check out this talk!
Governance for AEM/CMS Projects
Document a best practice project framework
Demonstrate a successful implementation
List key lessons learned and gotchas
Help answer questions to avoid pitfalls and reduce learning curve
Bring together a community of professionals
Develop a better understanding in running projects efficiently
Enable Collaborative Development Process
How to establish ways of working that allows shifting-left of the automation ...Max Barrass
Why Automate?
Your application will grow, you will not have enough hands
You are blocked by development
Hidden factory costs of bug-fix cycle
Why Shift-Left?
More people to negate massive inspections
Define measurable success early, work on good parts.
Reduce occurrence of defects
What is this got to do with Ways of working?
Unlock capacity
Make people smile
Is not
a Department
extra cost
a final oversight or a massive inspection
someone else’s job
Is
Everyone’s responsibility
Build into the ways of working
Everyone’s job
This document summarizes a webinar about new features and the roadmap for Provar, an automated testing tool for Salesforce. Key highlights include new features like support for Lightning components, mobile testing capabilities, and a new test builder. The roadmap discusses upcoming features like a managed package and REST API support. The webinar also covers tips and how Provar helps with issues like maintaining test cases across environments and testing advanced Salesforce features.
The world of a software house is a constant search for compromise between quality and costs. In many cases, the cost-cutting starts from the test automation. Then you start to talk about ROI but recognize that numbers are not on your side. We were there and what we have found out is that only a complete change in our approach allows us to find common ground with our clients. I will reveal one detail from the presentation - we are not talking about test automation with clients anymore - as a result we do it more and more.
Are you surprised that success automatically generates new challenges which we further translate into opportunities? We had to reconsider our approach to the test automation environment, internal frameworks and the way we share them between projects, including code ownership, … And again, one simple but unobvious solution allows us to both deliver what we promise and to earn more on our projects.
As we have been reshaping our approach to the test automation, we had to change the way of delivery too. One of the main decisions was skip out the role of test automation engineer (or software developer in test). We decided to go with the whole team approach which is consistent with the way we sell it.
Find it interesting? Join me and listen to our story about how we have transformed test automation.
This document outlines sessions for a DevOps training that provides an overview of enabling business agility through DevOps practices. The sessions cover topics such as DevOps for the enterprise, building a continuous integration environment, automating deployments, automated testing and monitoring, and continuous deployment. The goals are to educate attendees on how DevOps can increase development organization agility while lowering costs. Live demos of tools like CloudFormation are included to help organizations implement similar practices.
The document discusses testing approaches in Agile development. It outlines Agile core values like prioritizing working software over documentation. It compares the Agile Testing Pyramid model which emphasizes more lightweight unit and integration testing over manual UI testing to the traditional Testing Ice Cream Cone model. It also discusses the Agile Test Quadrants framework and how test automation fits into Agile at different levels including unit, integration/service, and UI testing while maintaining a balance between development and testing. The document provides recommendations for test automation in Agile like starting small and incrementally, balancing automation costs and ROI, and keeping feedback cycles quick.
The document discusses priorities for continuous delivery including individuals and interactions over processes and tools, working software over documentation, and customer collaboration over contract negotiation. It emphasizes building, integrating, and maintaining speed through iterations. While tests and tools are mentioned, responding to change and communication are prioritized. The document concludes by returning to practicing continuous integration and delivery using tools like PaaS platforms and Kanban boards.
This document provides an overview of Microsoft Test Manager (MTM) 2013 and how to use it for test planning, test case management, test runs, exploratory testing, and lab management. Key capabilities covered include creating test plans and test suites, managing manual and automated test cases, running tests and recording results, performing exploratory testing sessions, and setting up and using lab environments to collect diagnostic data during testing. The document demonstrates these capabilities through examples and screenshots.
Ahmed Omar is a software quality team lead with over 9 years of experience in manual and automated testing using tools like Selenium, JMeter, and Microsoft Test Manager. He has worked as a senior QA engineering and testing team lead for multiple companies, leading teams and managing the full SDLC, including test planning, case design, defect tracking, and ensuring coverage of functional, performance, stress, and other testing types. Omar has a bachelor's degree in computer science and certifications in software testing and SQL administration.
FUNTASY is a state of the art Test Automation Management tool with capabilities of running GUI and non-GUI test automation. FUNTASY is based on the Keyword Driven Testing (KDT) approach and promotes cross-organization test design by bridging the gap between the test automation team and the subject matters experts.
With FUNTASY, you can improve product quality while reducing test script development, maintenance and execution time.
http://www.qualitestgroup.com
Microsoft Test Manager 2013 is a test management tool that allows users to:
- Create and manage test plans, test suites, test cases, and test runs
- Support different types of testing like manual, automated, and exploratory testing
- Integrate with Visual Studio, TFS, and lab environments to facilitate testing activities
- Provide reporting features to track test progress and results
Enabling Agile Testing Through Continuous Integration Agile2009sstolberg
A Continuous Integration system is often considered one of the key elements involved in supporting an agile software development and testing environment. As a traditional software tester transitioning to an agile development environment it became clear to me that I would need to put this essential infrastructure in place and promote improved development practices in order to make the transition to agile testing possible. This experience report discusses a continuous integration implementation I led last year. The initial motivations for implementing continuous integration are discussed and a pre and post-assessment using Martin Fowler's "Practices of Continuous Integration" is provided along with the technical specifics of the implementation. The report concludes with a retrospective of my experiences implementing and promoting continuous integration within the context of agile testing.
Optimizely NYC Developer Meetup - Experimentation at Blue ApronOptimizely
For a company like Blue Apron that is radically transforming the way we buy, prepare and eat meals, experimentation is mission critical for delivering a great customer experience. Blue Apron doesn’t just think about experimenting to improve short term conversion, they focus on ways to impact longer term metrics like retention, referrals, and lifetime value.
John will take us through the journey of how Blue Apron built their experimentation program on top of Optimizely’s Full Stack platform.
Presented at Optimizely NYC Developer Meetup by John Cline, Engineering Lead, Growth at Blue Apron on November 7, 2017
For a beginner, this is a good quality pictorial representation of DevOps and DevOps Center of Excellence.
Opex Software focuses on consulting, implementation and development of DevOps tools and platforms. Have helped small and large data centers! This presentation talks about Continuous Integration, Continuous Delivery at a high level. For detailed presentations and flows, please ping us.
Thanks again, Enjoy!
Continuous Deployment pipeline demonstration spiced with Robot Framework and ...Antti Pohjonen
This document provides an agenda for a workshop on continuous deployment and acceptance test driven development. It introduces the presenters and their company, which focuses on agile testing and test automation services. It then defines continuous deployment and explains how it builds on continuous integration by adding more layers of testing and validation. The workshop example demonstrates roles like product owner and developers, and walks through a sample story of new feature development using ATDD and continuous integration/deployment practices. The workshop exercise invites participants to work in small groups to implement tests for a sample application using tools like Robot Framework, Git, and Jenkins.
[DevDay2019] Power of Test Automation and DevOps combination - One click savi...DevDay.org
Test Automation is becomming a MUST in software development life cycle now. DevOps has been an emerging trend, and it's no longer new. Remebering the old days, when you have to stand-up the test servers, get the builds from developers, deploy it, start-up agent machines, run your tests, collect reports, shutdown all resources you have just started, and spend days to analyze the failures. Now it's time to bring DevOps into this game and let it streamline all of these processes then you can save your days for other greater jobs of software testing.
- The document outlines Polarion's test management software capabilities including creating and managing test cases, defects, requirements and specifications with Polarion LiveDocs. It allows defining and running test runs with the Polarion Testing Framework.
- It discusses how Polarion can help integrate requirements, testing and defect management and manage activities with all stakeholders.
- The presentation then demonstrates Polarion's abilities like requirements and test traceability, test planning and execution, impact analysis and reporting across projects.
This document provides details about a software quality assurance professional with over 10 years of experience in software testing and automation. They have experience leading testing teams and currently hold a New Zealand Work Permit Visa. Their experience includes test automation using tools like Selenium, performance testing with JMeter, and testing in agile environments. They have worked with various companies and clients across different domains.
The document discusses how testing tools have evolved along with the testing lifecycle to bring more structure and efficiency. It provides several examples of projects that transitioned from disorganized testing methods like spreadsheets to more integrated testing tools. This allowed them to better manage requirements, automate test execution, and provide reporting. While no single tool is perfect, selecting one suited to the project's needs and ensuring users are trained can formalize the testing process and improve outcomes.
This document discusses Viewpoint's approach to web API performance testing. It outlines three key checkpoints: (1) ensuring performance during agile sprints through design reviews and trend monitoring, (2) integrating and testing components from different teams, and (3) performing full regression testing before release. It also defines different types of performance testing and describes the tools and processes used, including load testing with Visual Studio, tracking performance metrics, and using dashboards to socialize goals.
IT Agility Model - Supercharge your development and test activities with Micr...InCycle Software
Presentation that introduces Microsoft Azure for development and test to drive greater responsiveness and agility. With Microsoft Cloud, access to additional infrastructure quickly and simply for web and application servers, databases, virtual machines, etc. Discover how IT, Development and QA teams can work together to deploy environments and release applications faster, with more flexibility and efficiency.
Learn how to bring more IT agility with DevOps and Cloud computing practices. Organizations facing big IT challenges, such as growing workload and business pressure can take advantage of this new model for development, QA and IT teams.
The document provides an overview of model layer development in Coldbox, including creating model CFCs, using Wirebox for dependency injection, and unit testing models with MXUnit. Key points covered include:
- Using a service layer approach and creating a "recommendationService" and "recommendationGateway"
- Leveraging Wirebox to inject dependencies into CFCs
- Unit testing model CFCs with MXUnit to validate functionality and catch errors
- Demonstrating the creation of a basic "recommendationGateway" CFC with CRUD methods and associated MXUnit tests to validate behavior
The Importance of Performance Testing Theory and Practice - QueBIT Consulting...QueBIT Consulting
Why is good testing so hard to do? Not Enough Time. Not Enough Testers. Inconsistent or Incomplete Test Scripts. Lack of Performance Metrics. Difficult to Summarize Results
Visual Studio ALM and DevOps Tools WalkthroughAngela Dugan
If you're considering moving to Team Foundation Server or Visual Studio Team Services, this deck will walk you through the highlights, of which there are a TON!
Testing with Microsoft Technologies - Kick Off SessionMoataz Nabil
The document provides an overview and agenda for a session on Microsoft testing tools. The session will cover manual testing and test case management using Microsoft Test Manager 2012, automated testing using coded UI tests in Visual Studio 2012, web performance testing in Visual Studio 2012, cloud-based load testing in Visual Studio 2013, application lifecycle management using Visual Studio Online 2013, and working with Team Foundation Server 2012.
The document outlines 10 tips for business model innovation, presented by Daniel Burm. It discusses how embracing uncertainty and challenging your status quo is important in today's uncertain business environment. Some of the 10 tips include making use of data, starting with the customer, organizing creativity, validating assumptions, investing in change, and maintaining an outside-in perspective. The overall message is that businesses need to disrupt their own models or risk being disrupted by others.
The document describes how to conduct an agile team scan to assess agile practices. It recommends that the scan be done together with the team, such as during a retrospective. It provides instructions for creating an online survey to score agile practices on a scale from 1 to 5. Once completed, the survey results can be downloaded and reviewed with an agile coach.
The document discusses judo strategy principles that can be applied to business, including movement, balance, and leverage. Specifically, it advises defining the competitive space, pulling when pushed by competitors, and leveraging sunk costs and partnerships. The overall strategy is to avoid direct attacks and contests of strength and instead redirect an opponent's momentum.
This document provides information on Scrumban, which is a hybrid agile approach that combines elements of Scrum and Kanban. It discusses why Scrumban works by starting with the current process and respecting existing roles while enabling gradual change. It also lists some of the top reasons why agile adoptions fail, such as not having a clear reason for changing or forcing top-down changes. The document then explores Kanban principles and practices and how they can be applied in a Scrum context. It provides examples of when and how Scrumban can be useful for teams.
The document discusses discovering customer needs and market segments. It emphasizes understanding the problem a customer is trying to solve rather than focusing on features. It provides tips for researching different types of customers, including current customers, competitors' customers, and potential customers not currently looking for a solution. The document also discusses how to prioritize needs and whether a new product or market segment is worth pursuing based on factors like strategic fit, the competitive landscape, and potential customer impact.
The document describes how to create a videoscribe in 7 steps: (1) record a voiceover, (2) create sketchnotes, (3) make a concept video, (4) color and outline the sketchnotes, (5) export the file as SVG format, (6) animate the sketchnotes to match the voiceover, and (7) edit and finalize the video. It provides examples of videoscribes created for Dan Pink and PGGM to illustrate what a videoscribe is. The document is authored by Laurens Bonnema, an Agile management consultant.
Sketchnote je Product Backlog Items & Sprint RetrospectivesXebia Nederland BV
This document discusses using sketchnoting techniques for agile product backlogs and sprint retrospectives. It provides examples of how sketchnoting can be used to visually document product backlog items and capture ideas and discussions from sprint retrospectives. The document also gives brief instructions on how to create sketchnotes, highlighting that sketchnoting uses images, calligraphy and text to communicate ideas quickly.
Becoming an agile enterprise, focus on the test ingredientXebia Nederland BV
1. The document discusses becoming an agile enterprise and focuses on improving testing practices.
2. It describes shifting testing earlier in the process, making it faster and more frequent through practices like automation, and ensuring it is measurable and traceable.
3. The goals are to reduce bugs by 50%, increase productivity by 15%, and lower release costs by 25% through improved testing that provides continuous feedback.
How DUO started with Continuous Delivery and changed their way of TestingXebia Nederland BV
This document discusses how DUO changed their software development process to focus on continuous delivery and testing. It describes how DUO adopted practices like behavior-driven development (BDD) using Cucumber and Serenity to change their testing mindset and involve the whole team in quality. The document notes that while technical implementations are easy, changing people's mindsets is more difficult, and that BDD helps break down barriers between teams.
This case illustrates how KPN Online transformed their organization into Agile Feature Teams alongside implementation of Continuous Delivery and a Private Cloud. This helped KPN Online to reduce release cycles from months to 2 weeks, reduce operations by 50%, significantly speeding up innovation. This presentation will highlight how KPN completed this journey, which impediments they encountered and how they were solved, illustrated with several key learning lessons.
Dennis Eijkelenboom, Chief product owner KPN Digital infrastructure solutions
Bastiaan Bakker, Continuous Delivery Architect, Xebia Nederland
Sponsored by Xebia Nederland
Building a Docker powered feature driven delivery pipeline at hoyhoy.nlXebia Nederland BV
Docker combined with a select set of delivery tools powers the Continuous Delivery Pipeline at Hoyhoy. The pipeline enables fully automated build, deployment and validation of individual features with dynamic feature specific test environments. During this talk, the approach, technical implementation and best practices are covered.
Tim Noordhoek, CTO at hoyhoy.nl
Thomas Kruitbosch, CD Consultant at Xebia
TestWorks Conf The magic of models for 1000% test automation - Machiel van de...Xebia Nederland BV
The magic of models for 100% test automation.
In this talk we’ll quickly get you up to speed with the concepts ofmodel-based testing and then dive into hands-on modeling and testing. The subject of our scrutiny will be a common service, and we’ll show how to extensively cover its happy and non-happy flow, data and timing constraints. We’ll write zero test cases yet achieve unparalleled test coverage. You’ll see the magic in action but also get to peek behind the curtain...
TestWorks Conf Serenity BDD in action - John Ferguson SmartXebia Nederland BV
Serenity BDD in Action
Every test tells a story, but some tell a better story than others. Every test illustrates a specific path through the system to achieve a specific goal, but some paths are clearer than others. Valuable tests are the ones that tell a compelling story.
Come on a journey of discovery to learn how to write such tests, and witness a demonstration of these principles in action, with live coding of Serenity BDD automated tests.
TestWorks Conf Scalable QA with docker - Maarten van den Ende and Adé MochtarXebia Nederland BV
Scalable QA with Docker
Are you tired of maintaining all your Jenkins jobs running Selenium WebDriver tests connecting to several Jenkins slaves and the inconsistency of the setup? We need to become aware that it's inefficient to keep all the environments, browsers and selenium web drivers up to date manually.
During this session the attendees will be introduced to setting up scalable and solid Selenium Grids. We’ll also teach you how to write maintainable and scalable Selenium / WebDriver tests.
TestWorks Conf Robot framework - the unsung hero of test automation - Michael...Xebia Nederland BV
The Robot Framework is a generic test automation framework for acceptance test-driven development, that appears to be largely neglected.
Undeservedly so, as it facilitates powerful and yet simple test automation against a variety of interfaces.
It features some distinct advantages when compared to seemingly similar frameworks such as Cucumber or Fitnesse.
This workshop is meant to show you what makes the Robot Framework special and what is has to offer you.
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
UI5con 2024 - Bring Your Own Design SystemPeter Muessig
How do you combine the OpenUI5/SAPUI5 programming model with a design system that makes its controls available as Web Components? Since OpenUI5/SAPUI5 1.120, the framework supports the integration of any Web Components. This makes it possible, for example, to natively embed own Web Components of your design system which are created with Stencil. The integration embeds the Web Components in a way that they can be used naturally in XMLViews, like with standard UI5 controls, and can be bound with data binding. Learn how you can also make use of the Web Components base class in OpenUI5/SAPUI5 to also integrate your Web Components and get inspired by the solution to generate a custom UI5 library providing the Web Components control wrappers for the native ones.
How Can Hiring A Mobile App Development Company Help Your Business Grow?ToXSL Technologies
ToXSL Technologies is an award-winning Mobile App Development Company in Dubai that helps businesses reshape their digital possibilities with custom app services. As a top app development company in Dubai, we offer highly engaging iOS & Android app solutions. https://rb.gy/necdnt
Mobile app Development Services | Drona InfotechDrona Infotech
Drona Infotech is one of the Best Mobile App Development Company In Noida Maintenance and ongoing support. mobile app development Services can help you maintain and support your app after it has been launched. This includes fixing bugs, adding new features, and keeping your app up-to-date with the latest
Visit Us For :
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
Transform Your Communication with Cloud-Based IVR SolutionsTheSMSPoint
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Drona Infotech is a premier mobile app development company in Noida, providing cutting-edge solutions for businesses.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
2. Agenda
Introduction
Positioning test automation as part of
continuous delivery
- Practice at bol.com
History of testing and test automation at
bol.com
Wrap up
Webinar: bol.com's testing and continuous delivery journey
2
3. Introduction
Viktor Clerc
- Heads Xebia’s Test Automation
team
- Traversed through all phases
and activities of the software
delivery lifecycle
- Supported major organizations
in implementing a test
automation mindset and strategy
Webinar: bol.com's testing and continuous delivery journey
3
4. Introducing bol.com
4
Started by
Bertelsman
Online 2015
bol.com
becomes
separate (and
only) entity
1999
6
employees
#1 online retailer in the
Netherlands and Belgium
> 900 employees
2008
Started with
Scrum
• 5 million customers
• 9 million products
> 35 scrumteams
2001
Webinar: bol.com's testing and continuous delivery journey
5. Introducing Xebia
Xebia explores and creates new frontiers in
IT
- Provide innovative products and services
- Stay one step ahead of our customers’ needs
- Turn new technology trends into business
advantages
Customers choose Xebia for our innovative
solutions, technological depth and
craftsmanship
Webinar: bol.com's testing and continuous delivery journey
5
6. First Principle Agile Manifesto
Webinar: bol.com's testing and continuous delivery journey
6
“Our highest priority is to satisfy the
customer through early and continuous
delivery of valuable software”
7. Continuous Delivery
The three base principles
Base principle 1: Rigorous Automation
Base principle 2: Extreme Feedback
Base principle 3: Continuous Change
Webinar: bol.com's testing and continuous delivery journey
7
8. Transformation to Test Automation
8
SPECIFY DESIGN BUILD TEST INTEGRATE REGRESSION
USER
ACCEPTANCE
RELEASE
“I directly support the
definition of acceptance
criteria”
“The setup and quality of
the tests should be right
to allow for smooth
automation”
Acceptance
Driven Testing
Development = Test
Test = Development
Automate ALL
“Testing becomes a skill
rather than a separate
phase or role…”
User Acceptance
Test
effort
INTEGRATE REGRESSION
USER
ACCEPTANCE
9. CD & TA @ bol.com
Focus on test automation
- Special team with focus on improvements for all Scrum
teams
- Teams do TA themselves
Running tests as often as possible
- Not only once a day, but also after deployments (to test)
- Focus on fast test Fast feedback Earlier insight in
regression
Development of MayFly (will be open sourced!)
- User story-based
- Creates separate dev and test environments per
application
9
Webinar: bol.com's testing and continuous delivery journey
10. History of testing @ bol.com
All testing done manually until 2010
2010
- started automating with QFTest
2012
- evaluated other tooling and started working with
- around that time also developed in-house tool for
testing databases
10
Where did we come from?
Webinar: bol.com's testing and continuous delivery journey
11. History of testing @ bol.com
FitNesse is mostly used
- It is Java based and we are a Java company
- The wiki format makes easy reading for business
New tools are introduced
11
Spock
Where are we now?
Webinar: bol.com's testing and continuous delivery journey
12. FitNesse implementation
Started with 1 project containing all tests
- Sharing knowledge
- Structured the same as our use cases, i.e.
WebshopSuite.BusinessAccountSuite.UseCase1500
Nightly runs from the beginning
- Indication by labels (nightly)
- First sequential per application
WebshopSuite
- Later parallel by split running of suites on the lowest
level (a.k.a. suites with only tests)
WebshopSuite.BusinessAccountSuite.UseCase1500
12
Webinar: bol.com's testing and continuous delivery journey
13. Running & Reporting
Maven is used to bootstrap FitNesse
- In combination with a JUnit runner
Specialized Jenkins job for parallel execution
- Knows the structure of FitNesse and fires
corresponding jobs
The tests are executed by Jenkins slaves
- Specialized Linux and Windows hosts with browsers
- Chrome, Firefox, IE8 and IE11
Suites are run and results are sent to the
reporting tool
- Data stored in MySQL database
- Reports generated by BIRT
13
Nightly structure
Webinar: bol.com's testing and continuous delivery journey
15. Wrap Up
Best practices
- Focus on optimization of test automation:
feedback, feedback, feedback
- Make testing a team effort, with adequate overall
guidance
And…
- Design test automation at scale
- Without test automation no continuous delivery
- May require novel TA solutions
Webinar: bol.com's testing and continuous delivery journey
15