To Deploy or Not-to-Deploy - decide using TTA's Trend & Failure Analysis
The key objectives of organizations is to provide / derive value from the products / services they offer. To achieve this, they need to be able to deliver their offerings in the quickest time possible, and of good quality!
In order for these organizations to to understand the quality / health of their products at a quick glance, typically a team of people scramble to collate and collect the information manually needed to get a sense of quality about the products they support. All this is done manually.
So in the fast moving environment, where CI (Continuous Integration) and CD (Continuous Delivery) are now a necessity and not a luxury, how can teams take decisions if the product is ready to be deployed to the next environment or not?
Test Automation across all layers of the Test Pyramid is one of the first building blocks to ensure the team gets quick feedback into the health of the product-under-test.
The next set of questions are:
• How can you collate this information in a meaningful fashion to determine - yes, my code is ready to be promoted from one environment to the next?
• How can you know if the product is ready to go 'live'?
• What is the health of you product portfolio at any point in time?
• Can you identify patterns and do quick analysis of the test results to help in root-cause-analysis for issues that have happened over a period of time in making better decisions to better the quality of your product(s)?
The current set of tools are limited and fail to give the holistic picture of quality and health, across the life-cycle of the products.
The solution - TTA - Test Trend Analyzer
TTA is an open source product that becomes the source of information to give you real-time and visual insights into the health of the product portfolio using the Test Automation results, in form of Trends, Comparative Analysis, Failure Analysis and Functional Performance Benchmarking. This allows teams to take decisions on the product deployment to the next level using actual data points, instead of 'gut-feel' based decisions.
Outline/structure of the Session
- Explain why CI and CD are a necessity, and NOT a luxury.
- Discuss some of the factors that can make CD a reality.
- Discuss the current set of tools that assist in 'health-check' decision making for deploying / releasing the code in new environments.
- Explain the limitations of the above set of tools in the decision making process
- How can TTA bridge that gap (limitations discussed above)?
- Explain the value proposition for TTA
- Demo of TTA features
- Share the set of potential features to be added to TTA
- How can you help?
- Understand the gap in current set of tools from a big-picture perspective
- How can TTA that can bridge the gap?
- Learn the Trend and Failure Analysis capabilities of TTA
- Learn how TTA can become a real-time, central Testing Dashboard for your project / program
- A glimpse into the existing TTA Feature backlog
- Ways you can help evolve TTA
Devops, Developers, Testers, Automation Testers, Managers
schedule Submitted 2 years ago
People who liked this proposal, also liked:
Anand Bagmar - Enabling Continuous Delivery (CD) in Enterprises with TestingAnand BagmarSoftware Quality EvangelistEssence of Testing
schedule 3 years agoSold Out!
The key objectives of any organization is to provide / derive value from the products / services they offer. To achieve this, they need to be able to deliver their offerings in the quickest time possible, and of good quality!
There are various practices that organizations need to implement to enable CD. Changes in requirements (a reality in all projects) needs to be managed better. Along with this, processes and practices need to be tuned based on the team capability, skills and distribution.
Testing (automation) is one of the important practices that needs to be setup correctly for CD to be successful. But, this is tricky and requires a lot of discipline, rigor and hard work by all the team members involved the product delivery.
All the challenges faced in smaller organizations get amplified when it comes to Enterprises. There are various reasons to this - but most common reasons are - scale, complexity of the domain, complexity of the integrations (to internal / external system), involvement of various partners / vendors, long product life-cycles, etc.
In such situations, the Testing complexity and challenges also increase exponentially!
Learn, via a case study of an Enterprise, a large Bank, the Testing approach required to take them on the journey to achieving CD.