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:
Test Driven Development of Infrastructure Code in Chef
Chef is a popular Infrastructure Automation framework based in Ruby. It comes with a host of testing tools bundled with it like ChefSpec for unit testing, ServerSpec for system testing and TestKitchen for integration testing. This session is a demo of how to use these frameworks to test drive cookbook development.
Big AgileSriram Narayan
schedule 2 years agoSold Out!
Good engineering practices and fail-fast, iterative, low-ceremony processes help achieve team level agility. They are necessary but not sufficient to scale agility across the IT organization. In this talk, I'll address what else is needed and why. In particular, I'll address:
- Why plan-driven IT projects are a bad idea why we need value-driven projects instead
- Why a matrix org is a bad idea for IT and why we need cross-functional teams instead
- Why IT budgeting needs to change from being project-based to being team-capacity based
Enabling Continuous Delivery (CD) in Enterprises with TestingAnand Bagmar
schedule 2 years agoSold Out!
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 such a fast moving environment, CI (Continuous Integration) and CD (Continuous Delivery) are now a necessity and not a luxury!
There are various practices that Organizations and Enterprises need to implement to enable CD. Testing (automation) is one of the important practices that needs to be setup correctly for CD to be successful.
Testing in Organizations on the CD journey is tricky and requires a lot of discipline, rigor and hard work. In Enterprises, the Testing complexity and challenges increase exponentially.
In this session, I am sharing my vision of the Test Strategy required to make successful the journey of an Enterprise on the path of implementing CD.
First Amongst Equals - Can UX be there?
Traditionally, in software development, user experience (UX) wasn't valued as much as developing of the software itself. But this has changed rather radically. However, creating an enriching user experience in an agile fashion is still challenging. Most of the agile engineering practices in use are around building software but seldom address UX. When building a product in an agile fashion, UX in an incremental fashion becomes important.
In this talk, we will present our experience of creating UX in an incremental fashion for a virtual wallet. We will also talk about the different challenges we faced such as, educating various stakeholders on the value of incremental UX, building collaboration between developers and experience designers and abstracting design components, along with the solutions we devised to tackle these challenges.
Process Agility - the nemesis of business agility?
We've come far in our journey of Agile as a software development methodology. From stand-ups to showcases to sprint planning meetings to burn-ups (or downs), we've got it down pat when it comes to processes to follow to be considered Agile. However this heads-down, process defined agile, often hinders real agility required to meet business needs. Is doing a three hour sprint planning meeting every week the most important thing to do when you have to get a minimal-viable-product out in the market? How much of automated functional testing should you do when you know that your product's beta version is only going to validate assumptions of your business idea? Should you write tests at all? There is no formulaic answer.
In this talk, KK and Krishnan will talk about their experience of how much Agile is too much Agile. We look at how to find the right balance between following agile practices and being responsive to your business. How much agile is too much and how less is too less?
We will do this by looking at:
- A couple of successful agile adoption stories
- Look at why agile was successful in the contexts above
- Discuss why this success will limit us if we are not careful
- Talk about a start-up and how the things that led to success in the first 2 stories limited us in the start-up context
- Look at approaches to understand what agile practices/processes to follow to be business agile
- Close by summarizing the challenges facing agile (as we see it) and how success in process agility will limit us in business agility
Infrastructure As Code - The secret sauce for Continuous Delivery
Developing Infrastructure as Code as a practice is increasingly adopted by organizations that want to have Continuous Delivery. Infrastructure As Code requires treating infrastructure as code, applying the same development techniques that one uses to build application software. This talk discusses the need for having infrastructure as code, the several frameworks available in this space (like Puppet, Chef, Ansible), what they bring to the table and the philosophical differences between them and the testing tools and frameworks available to test infrastructure as code. The concepts would be supported by snippets of infrastructure code written for an open source application.
Get up and running with TeamcityShiwangi Prasad
schedule 2 years agoSold Out!
As a tester in an agile model of software development team, I felt the need to have an automated mechanism of getting fast feedback on my growing application. This talk is to share my learnings on the set up, configuration and various processes followed in this automation. The benefits of having a CI and automated test runs, their set ups will be shown through a demo.
The Practical Pyramid
An Ideal Test Pyramid is an invaluable technique to succeed with agile. However, it is challenging to have this ideal pyramid in practical projects for several conditions in the projects, like legacy code bases. To have a good test pyramid, several best practices of software development need to be followed. This talk discusses the practices that help in implementing test pyramid and the challenges faced by many teams in doing that and suggestions on how to overcome them.