Guessing Quality? < Bring predictability through automation and right leadership >

Ramanath heads the Test Center for Digital Service Group at Ericsson India and manages its delivery across Market Areas. He is an advisor to clients, and with his exceptional ability to connect the dots has managed to turn-around several projects, both during pre-sales and execution.

Test Center has seen significant change since he joined Ericsson in Apr 2017 where he has created The Test Leadership Development Program, Test Metrics dashboard, Test Automation standardization, Estimation models for improving response to proposals, etc.

He has comprehensive experience in Strategic Planning, Test Delivery Management, Test Automation, creating innovative & award-winning solutions using open source technologies to solve challenges in the testing landscape, Process Management, Quality Control, Project Management, Market Recognition, Client Relations Management, Cross Functional Coordination, People Management and Team Management.

He has internationally published and presented several Whitepapers, Articles, and Blogs.

We live in a world where change is the only constant – this is even more evident in the technology world where the dynamics are prominent and visible. Today, a positive mindset is the only key we hold to be satisfied and happy in whatever we do and continue to take on new challenges as opportunities in one’s own stride.

As we architect continuous quality in the world of DevOps, why is a positive mindset important for a tester, how to nurture it (especially given that this cannot be achieved overnight) and how do you find your own IKIGAI which will benefit not just you, but everyone around you and also the product you are working on.

Speaker Profile

Rajini leads the engagement, delivery and relationship management for some of QA InfoTech's largest and also manages the organization’s Bangalore center. She is also actively involved in test evangelism and thought leadership for the last several years. Rajini has more than seventeen years of professional experience, primarily in the software quality domain.

Following are the broad level of topics which will be covered in 30 mins through a presentation with Examples.

Agile or agility
Automation or Digitization
Machine-learning or Human Sense
Testing or Auditing
Technology or Domain knowledge for Testers

While most aspects of software engineering development has been improved dramatically over the period of time since a decade, software testing is of such activity that largely unchanged. Quality Testing in software hasn’t changed dramatically because testing requires manual activities, domain expertise, human intervention, and emotions for the end user — all of these requires a human-level intelligence and AI/ML is a way to build such software testing tool that can replicate an human based quality assessment system. In this topic you will get to hear a similar style of AI/ML based tool which would do a software quality testing of an traditional Mobile App running on any OS platform.

Why is Open Source Test Automation the Best? Choosing the right testing tool is a major challenge with automation and AI-powered testing taking over the testing arena. While there’s huge competition in the paid testing tool options, many organizations are shifting towards open source automation testing. Why Not Open Source? Open source automation testing is gaining momentum due to the following benefits they offer to the QA team. Flexible & Extensible One of the major reasons for choosing open source automation testing is the flexibility it offers to the test engineers. These tools are also extensible when there’s a demand. Feasible Vendors charge a huge fee for paid automation testing tools which many organizations, especially the start-ups, cannot afford. Open source is free and hence is more feasible. Large Community Open source automation testing community is a fast-growing one with complete focus on not getting lost in the crowd. Open source testing community is buzzing with talents who are continuously contributing new releases of the various tools they co-create. Share resources with Virtualization With open source automation testing, you can share your resources and reduce the cost. Freedom Vendor tools come with their own restrictions but open source offers much freedom. Security Open source is more secured than vendor tools. Platform Independent Open source automation tools are language and platform independent. They function well across platforms and support multiple languages which is a huge advantage for enterprise solutions. Watch out for these too! While open source offers scores of advantages, it also comes with a bunch of challenges!
• Can get Complex
• Could be buggy
• More effort required
• Compliance issues Ideally, choosing between open source and vendor tools should be strictly depending upon your project’s specific requirements. Every project and every requirement being different, the right tool can alleviate many vendor-related problems. Open source definitely is the preferred choice in most cases due to the flexibility, feasibility and freedom it offers.

The purpose of Test Automation and its impact on Emerging Digital Technologies.

Worked with big MNC’s like Motorola , Huawei , One Convergence ,Tecnotree & Ericsson with 16 yrs of IT & Telecom experience with an MBA degree (specialized in Strategy & Marketing) from IIM-Rohtak [Delhi].

One of the tenets of making software delivery process go without a hitch is Test predictability and Test predictability means better clarity, and faster response. We will provide a peek into how we bring this @JFrog.

Hemanth Sridhar is a Senior Automation Engineer at JFrog with close to 6 years of experience mentoring and leading testing for organisations like Tesco, General Electric and Dunzo.

Aim:
To teach practical ways of creating robust test automation scripts using layered architecture. How to separate the business side from the code of your test scripts and make your test automation closer to user flows.

Learning Objectives / Outline:

Delegates will learn-
Practical ways of creating robust test automation scripts using layered architecture.
How to separate the business side from the code of your test scripts and make your test automation closer to user flows.
How to implement a layered architecture in a variety of ways, using different tools and approaches
Take back a practical understanding of test automation architecture that you can use with any tool or technology.

Having people with varied expertise in your agile team, a layered approach to your test automation can help you leverage their different skill sets and make test automation a smooth, on-going continuous process. To do so, you need to know and understand the three layers of test automation and how to separate the code from the test. Writing tests in the language of the business allows all stake holders to participate and derive value out of the automation process. Let us discuss the correct separation as well integration of these layers and also see a demo on how to implement this with a case study using Sahi Pro.

Nishi is a corporate trainer, an agile enthusiast and a keen tester at heart! With 11+ years of industry experience in Agile environment, she has worked in various roles as a hands-on tester, automation developer, a freelance consulting trainer and currently works with Sahi Pro as the Evangelist and Trainings Head.
Nishi is passionate about training, organizing testing community events and meetups, and has trained hundreds of professionals and teams on agile, test automation, QA bootcamps and DevOps courses.

She is CP-AAT, CP-SAT, CP-DOF, CP-MAT (certified by ATA), Agile Scrum Master ASM (by EXin) and ISTQB certified (Foundation and Advanced Test Analyst & Test Manager) and has been a speaker at many testing events and conferences.

Nishi is also a writer on technical topics of interest in the industry and has numerous articles published at numerous popular forums and her own blog testwithnishi.com where she writes about the latest topics in Agile and Testing domains.
www.linkedin.com/in/nishi-g-02127aa

Being successful in DevOps testing is not just about automation. It is also about the flexibility and reliability of your test automation. And it all must be able to scale.

In this seminar we would cover test automation scenarios to provide both value and coverage to the business function within your organization. We will also discuss scaling the bursting of platforms, which allows teams to execute tests in parallel and shrink the overall testing cycle while gaining faster feedback.

Participant will:

Learn tips and best practices to properly scope test automation suites
See a live demo of a test suite executed across web VMs and mobile devices
Leave with practical advice on how to scale cross-platform test automation

Guruswamy is a Technical Enablement Manager in Perfecto Partner group. He spent overall 14+ years in IT, with a focus on functional, automation and Performance testing. Guruswamy is a DevOps practitioner and has hands-on experience with multiple industry-leading automation and test management tools. He is an experienced automation architect built organisational automation framework in alignment with product quality, velocity and cost effective solutions for the Agile methodology. Also as a performance test specialist signed off many enterprise grade application by simulating real user environment and network conditions. Guruswamy can be reached at guruswamy.bm@perfectomobile.com

During this talk, I will talk about different types of testing leaders and what skills are required to be an effective Testing leader in the changing world of Agile and DevOps. What are the different opportunities to contribute and what is the path toward Servant leadership in Testing domain.

Over 13 years of diverse techno-functional experience at HSBC, Capgemini (Morgan Stanley) and Fiserv as a Project Manager/Organizational Change Agent at both onsite (US, Costa Rica) and offshore (Pune, Noida) locations. Extensive experience in Software Delivery and consulting, Process Optimizations & Simplification, Agile coaching & implementation, organizational culture change and DevOps tools implementation and management. Proven skills in leading organization wide initiatives to bring cultural and technological transformations to bring agility in deliveries and accelerate time to market. A test evangelist with proven track record of test process optimization, automation ROI and agile scrum coaching.

Curious about behavior driven development? Hearing lots of talk about “BDD tests”, “Cucumber”, “given, whens, and thens”, and trying to make sense of it all? If so, then this session is for you. In this session we will learn about BDD from its origins to the present, introduce the tools and vocabulary of BDD, and demonstrate its usage to automate the web applications.

What will you learn?
The origin story of BDD as a practice
The vocabulary of BDD and the tools designed for it
An opinionated architecture for a BDD suite
A live demonstration of BDD in action to automate the web applications

Arunkumar C is QA Consultant at Thoughtworks. He is contributed to automating many web, mobile and desktop applications, he is also mentoring the people who need to develop their career as QA's. He is from Bangalore, India passionate to learn and teach new technologies

1

about generic case study of how the implementation has helped, why it is important etc?

20+ yrs of IT experience with rich knowledge of software development, testing, people management and project management areas.
4+ yrs of experience in POSH implementation and training. worked with many corporate and startups to implement POSH policy and I have trained their ICC and employees for the same. I also serve as an external member of ICC team and participate in handling incident enquiries as an external member.
Seasoned Engineering leader with experience in building & leading teams in startup environments as well as large organizations; Combination of technical depth, business acumen and understanding of markets
Rich experience in the areas of Strategy Planning, Service Delivery, Talent Leadership & Development & Client Relationship Management
Experienced in the areas of
*Virtualization
*Storage resource management
*Business Process Management
*Enterprise Application Integration
*Telecom
*Cloud computing

Blockchain has a lot of use cases and applications that could bring about a shift on the current landscape. None of these are more fundamental than identity which plays a central role in our digital and physical selves. We talk about the general role and use case of the blockchain and then move on to how identity on the blockchain can overcome a lot of the shortcomings that we might have today.

Shivhari Shankar is currently heading products at Springworks. Shiv's responsibility is to execute on the company vision and handle product roadmaps, product vision and think of features and focuses on how to engage with the users.

Shivhari has also been passionate about blockchain technology and has given over 20+ talks on various aspects of the blockchain ecosystem. He mainly talks about the real world application of blockchain and how it can bring about a paradigm shift.

Shivhari started his career in Cisco Systems. After which he was as the Product Architect at Guru-G Learning Labs, a ed-tech startup based in Bangalore. Shivhari did his under-graduation in Computer Science from MIT, Manipal, India.

Introduction to build cross-platform (Web, Desktop, Mobile) SPAs faster with less code using SPA.js with its built-in support for api-mock, form-validation, i18n and more. In this session we will get to know why SPA.js? and it’s key features. The author will do live code demo on how to get started to build cross-platform SPA using simple HTML, CSS and Javascript.

Key Take-away:

Know-how of building Single Page Applications in a simplest way.
Build rapid working clickable prototypes with less code without back-end APIs.
Useful tool to build Rapid POCs with mock/live data

Microservices Architecture focuses on helping the developers/architects to understand the key Architecture paradigms with a hands-on section available in the 1-day workshop. The objective of this session is to help the developers from Monolithic App mindset to a Microservices based App development. It also helps the developers with hands-on development experience with key Microservices infrastructure technologies like Eureka, Ribbon, Zuul, Kafka etc., and key Architecture styles like Hexagonal Architecture and Design styles like Domain Driven Design, Event Sourcing, and CQRS, Functional Reactive Programming, Microservice messaging. Apart from the Infrastructure and Software Architecture, the awareness session also focuses on Scalability and Testing aspects of Microservices.

Course Design

1. Microservices Architecture Styles
2. Scalability
3. Design Styles
4. Design: Event Storming
5. Distributed Transaction Management
Transactions: Case Studies

Araf Karsh has with over 25 years of experience leading the design and development of mission-critical, object-oriented and web-based applications for premier organizations including Bank of America, CIBC, Johnson & Johnson, Kaiser Permanente, the U.S. Department of State, and the U.S. Dept of Energy. Karsh has an established track record leading production software organizations and bringing new products to market using leading-edge technology.
He has extensive knowledge of Microservices, Containers (Docker), Blockchain, SOA, Angular platform and key foundational technologies. He is well versed in building highly scalable and high performance distributed applications using Java technologies.

The IT frameworks are getting changed drastically. Software Industry has already in transition from Monolithic frameworks to Microservices frameworks. In this Microservices transformation, Is the traditional way of testing is still valid? How do we test the Microservices? Mr. Vamsi Mohan is going to speak more on "Testing for Microservices". At the event, he will discuss on several examples of Microservices testing strategies, best practices and the open source tools for Microservices testing.

Mr. Vamsi Mohan is IIM Ahmedabad Alumnus and research scholar in Computer Science from the University of Delhi. He is currently working as a Principal Solution Architect at Tech Mahindra, catering digital transformative solutions to the Fortune 100 telecom clients. A Technology acumen across a range of digital technologies, including RPA, AI/ML Blockchain and cognitive engineering. He has end to end life cycle experience, architecting from the traditional monolithic frameworks to Microservices frameworks. He is keen in strategizing the testing practices for the modern frameworks including web and mobile. Prior to his current role at TechM, Vamsi served in various senior leadership roles managing Technology CoEs, Digital Innovation Centers in EMEA and APAC regions. His experience spans various technology solutions focusing on future-proofing business through digital transformations and the delivering of customer fit solutions. He is a conference speaker, published author, guide and reviewer for several technical books, magazines and international journals in technology, and management.

1.Mobile assurance Testing
2.Types of Devices used for testing
3.Types of mobile apps
4.Types of mobile app testing
5. Automating mobile assur ance
6. Mobile cloud testing-Integration with CI and CD
7.Cutting Edge Technology in Mobile automation Industry (Next Gen/Futuristic Technology)
8.Demo
9.Q/A

We all know how important test automation is. There is no need to put more emphasis on the topic. However, test automation is not easy and more than 50% of the ambitious test automation projects fail. Why is that? There are many reasons for it. On the highest level, we can say the lack of planning contributes to 80% of the failures. Let’s see the underlying reasons. This data is collated from different live projects from a diversified customer base.
Takeaway for the participants
While most of the technology services companies talk on the holistic automation, when it comes to a test automation project on-the-ground the focus shifts to tool, productivity, faster automation execution. The before said focuses are good, however, very less planning and strategizing goes to achieve this. In this presentation the participants will be made aware :
important aspects of test automation strategizing
the blind spots in test automation and how to avoid
how to carry out a typical discussion with your customer on test automation
items to be made sure before a test automation project starts

As the industry is moving towards Agile-DevOps, it is often quoted that, “we don’t need testing/testers”. However, the fact is whatever the model project team adopts, the basic activities like Req. analysis, Design, Coding, Testing etc., remains the same. We need the people with required skills to perform all these activities, however, the way we do these activities may change. This paper talks about challenges and the role of automation, to ensure the quality.

Prabhu Kogunde Matt is an Electronics and Communication Engineering graduate with more than two decades of Industry experience. Presently, is part of Ericsson India Global Services and managing the testing practice for Service Line IT&ADM. Prior to Ericsson, he was part of HCL and Wipro. He worked with many customers across the globe and helped them in addressing their testing challenges. In his current role, he is enabling his team to deliver testing services to various Telco operators to ensure customers get error free bills and no revenue loss to operators.

We've spent a lot of time talking about waterfall and Agile methodologies and best practices for both. One thing that I wanted to highlight is the process and challenges that are arising when transitioning a team or an individual from one to the other. We've been using Agile for so many years and we see every individual is facing lot of challenges to get transformed. Resist to change will be the major obstacle stopping an individual to transform. They think it's just a process, but they don't realize the magnitude of change they have to undergo.

The transition will take time and happen incrementally. Despite these benefits, many organizations underestimate the obstacles they must overcome to achieve greater agility, from skill shortages to cultural backlash. Many professionals likely are accustomed to one way of working and shifting to agile practices without any type of guidance is likely to result in failure. In Agile - planning, communication and coordination is necessary.

Guiding the team with right Agile Practices will make every individual to work as team. These sessions will help team members understand their roles in the system and ensure that their expectations match Agile values. This also helps the team and individuals to welcome changes at any point of time and open for any interactions with others. Agile teams progressively plan at each level. Agile methods can help teams better manage complex projects by embracing uncertainty and incorporate continuous learning into the process.

This study deals about, how to make the teams the self-motivated and work individually and independently by following the best practices in work and adopts a systematic review methodology to identify the key challenges in the migration process from traditional software development paradigms to agile methodologies.

Venkatesh has passionate of working in Agile and want to research more on the transformation challenges from Waterfall to Agile and find a better solution to implement in the work life. Venkatesh has completed Bachelor of Engineering in Electrical and Electronics Engineering and Master of Business of Business Administration in Human Resources. He has been trained as a Quality Analyst and working in Agile methodology since 2015 with different roles and responsibilities. He is also a Certified Scrum master and helping professionals to learn Agile and get into Agile Mindset.

In today's industry standard, when we talk about automation coverage we always stick to how many lines of application code is traversed while executing automation script/code. No of lines traversed through application code can't translate into acutal feature coverage. In this talk, let us discuss with one working model where automation flows can justifiy what is the feature coverage by automation code/script.

With agility initiatives becoming common, organizations have reemphasized these as strategic initiatives to separate the services at Enterprise level, microservices at application level and ensuring the hybrid infrastructure requirements through an on-demand basis. DevOps adds the real culture to improve the delivery and integration into this complex landscape.

Vikram Balakrishna is a senior enterprise architect at Capgemini with over 15 years of industry experience, helping businesses to best leverage the ever-growing technology disruptions, identifying the bits that are here to stay, and harnessing them to deliver true commercial value. His focus is on incubating new technologies and ideas, such as cognitive computing, digital infrastructure, and automation – a complex new battleground that has the potential to give businesses at the leading edge a significant competitive advantage.

Reduce manual efforts by 70% provides ROI and quicker feedback by test automation of Accessibility workflows with integration of Selenium & HTML code sniffer Enhancing customer base by enabling applications accessible to leads including differently-abled/ having special needs and abide by WCAG

• I would like to concentrate on 4 principles mainly ( POUR - perceivable, operable, understandable, Robust) and 12 guidelines of Text alternatives by providing alt attributes, Time based media by proving captions, Adaptable by all assistive technologies like screen readers/magnifiers, Distinguishable, Keyboard accessible

• This paper describes manual testing by reviewing HTML code and automated Accessibility techniques using evaluation tools like Voice over, AXE, HTML code sniffer, WAVE, A checker, W3c Mobile ok analyser, colour contrast analyser useful for developers and QA within their automated scripts

On comparing a normal web or mobile application automation to a Gaming Application Automation the Testing of Gaming Application is a Challenging task because of Technologies being used, the Graphics & UI, the multiplayer interactions, consistency of experience & the Role of AI.

There should be a targeted approach towards the Parts of the game to be Automated to extract the maximum benefits of the Automation. Also there are multiple areas to consider for Game Automation - Client, Server Side, Data Pipelines & Tools Integrated leading to Automation at multi-levels. Thus achieving the same through different frameworks using Java/ Python with Selenium or Java with Rest Assured.

With years of strong technical experience across Testing, Release Management and Solution Engineering I have been a key contributor in many transformational journeys across multiple facets of engineering. I currently play the role of Head of QA at Junglee Games. My areas of specialisation ranges across Testing CoE Test Automation, Accessibility Testing, Security Testing, Agile Testing Cloud Testing etc. I also collaborated on a seamless offshore transition strategy for clients that require zero down-time.

With the advent of microservices , containers and on demand computing and the rate at which code is getting churned out every single day we need to automate or perish. DevOps or Build at Scale and how to have a hands free approach like autonomous cars is what companies need the most today. It is no longer OK to say we build it someone will test it and certify it , it needs to happen in realtime and all at once the Build, Automate and Test in a continous pipeline. How can companies stay on top by effectively making use of Automation shall be looked at in this talk.

Enterprise Architect( Togaf Certified), CSM(Certified Scrum Master) Leader in Technology, Technology Manager and sound product development experience coupled with thought leadership in large enterprises and grounds up development. Proven product, project,program and people management experience in core banking,mobile payments,product development with ability to harness fit for purpose agile practices.Some of the products and solutions worked figure in the top leaders quadrant consistently of Gartner and Forester. Areas of work :

1. Enterprise Architecture and Solution Architecture Best Practices.
2. IT Strategy and Product Evangelizing.
3. Lean IT Principles and how to apply to Organizational Context.
4. Product Management and Product Development.
5. Productizing a Concept and Go to market Strategies.
6. Using Enterprise best practices for better delivery.
7. Articulating Vision and Formulating Organization Strategy ( IT and Non IT Organizations).
8. Set up your business unit around a strong and robust cost center model.

While containers have become ubiquitous in the world of software development, it is also becoming very challenging to maintain the security of the product from a process perspective due to security not being built-in. This talk will run through various case studies where container security was compromised due to process negligence and what steps can built into the process to avoid such expensive mistakes.

Ramakrishnan (Ramki) Seshagiri is an accomplished technology professional with over two decades of experience in building software products across multiple industries (Security / Healthcare / Finance to name a few) in multiple leadership roles in India and North America. He has spent close to 8 years building niche enterprise software across network and web security space and more recently, have gained considerable expertise in the blockchain and distributed ledger technology space and has been certified by international bodies like Blockchain Training Alliance and Blockchain Council. A certified Project Management Professional (PMP) and also a member of leading cybersecurity bodies, ISACA & Data Security Council of India (DSCI)

S Selenium automation needs configuration underneath eg selenium grid configuration but configuring selenim grid is very messy and cumbersome, this is where zalenium comes to rescue with lot of built in features and with docker and kubernetes it is super easy to set it up and running for consumption for UI automation engineers to write test code.

Separate Test and App Repositories
A truly Agile team will have developer and QA team members work together during the current sprint to both develop and test a feature. - It’s no longer separate teams - We are a Team Approach Though we work in Agile still there is a psychological boundary between Devs & QAs. There is a separate Repo only for QA code, a separate set of QA pipelines which run only tests. (Organizational structure reflected in systems - Conway's law) Problems with this approach
Onboarding ( QAs and also devs - Devs should know about QA code )
Documentation
Code clean-up
Versioning
Devs/team tend not to acknowledge test pipeline failures ( QA pipelines are less apparent)

The main issue is Versioning
Is the QA code testing the intended version of application code? As the QA pipelines are running independently of the app code there can be versioning problems. This is prone to errors as QA code is intended to test X version of the app but it is testing the X+1 version of it and the QA pipelines miss to give the feedback and it might also block the deployments.
QA code and App code should always be in sync to avoid this.
These issues are likely to happen on when the Hotfix branches are cut for the deployment and also App upgrade testing
There can also be issues when multiple versions of code are live (AB testing, Mobile app versions, product versions etc) Keeping multiple versions of QA code in sync with multiple versions of App code will become a nightmare. ( Ensuring all tests are green on release/hotfix branches is a must for confidence in releasing)
Testing the backward compatibility and distributed QA teams will add to the complexity
MonoRepo to the rescue
A monolithic repository is a software development strategy where code for many projects are stored in the same repository
App and Test code are just different packages in the same repo
As it is same repo there is no versioning problem (Single commit SHA identifies test and respective app code)
Single pipeline for the application - No separation of dev/test

Advantages with Monorepo
Tests can’t independently exist without the application code
Single code base makes the onboarding, documentation much easier as there is a single source of truth.
More visibility to the team
Disadvantages with Monorepo
Doesn’t compile only test code. When a commit is pushed Build, Unit tests and other jobs run before running the test code -
Not quick feedback
Build broken
Test and App should be of the same tech stack

Conclusions
Breaking Conway's law is good
The build is not good, why to test?
Who gets blocked doesn’t matter. Many a time, QA teams get blocked (env issues, data issues etc). This is more of ‘We are a Team Approach’ and the whole team is blocked.
Treat the whole pipeline as one and there is no longer test only pipelines.
Test code should be treated along with build - fix FT like unit tests - Else pipeline will be red
FT is not an afterthought (being agile) Treat exactly same as build break should be fixed on priority

Other comments
Trunk based/Git flow with Monorepo
Monorepo, in general, will reduce redundant testing (Use case with my current client)
Advantages of Monorepo
Ease of code reuse –
Simplified dependency management –
Atomic commits –
Large-scale code refactoring –
Collaboration across teams
Lerna versioning tool
Examples - Babel, Wdio, Jest and other open-source projects
Monorepo migration tools - Fastlane, Lerna
Which commit broke the build if regression runs once in a day

Modern UI testing tools always increase our expectations on maintaining code, reducing flakiness in tests and producing reliable test suite. Are you one among those having problems solving flaky tests and maintaining test code while testing modern web applications? Come learn about Taiko and Gauge, modern browser automation tooling from ThoughtWorks.

With Gauge you can create automated user journey tests written in simple Markdown with cross platform and multiple languages support like Javascript, Java, Python, Ruby and C#. Also Gauge works with a variety of IDE’s and CI/CD, making your automation tool easy to implement.

Taiko is a browser automation tool with a powerful REPL that allows you to script user-facing tests dynamically using a simple domain-specific language. You can eliminate flakiness by testing your application as a black box relying only on the visible elements on the web page and not on placement of screen elements or CSS classes or ID’s

In this interactive 45 minute session, get ready to learn exciting ways to record code as you execute, reducing flakiness in the tests, craft resilient code and developing reliable, readable and maintainable tests.
Takeaways:

1. Introduction to Gauge and Taiko

2. Using the “Implicit Wait” feature to reduce flaky tests

3. Using “Proximity Selectors” feature to code maintainable tests

4. Using the Taiko REPL to create your tests step by step

5. Integrating JavaScript test framework like Mocha and Chai with Taiko

6. Using screenshots to analyse Test Failure

She is a Consultant for Quality aspects and people know her for her interests in learning and advocating Quality as a mindset to the team. She is contributing to automate test suites for multiple applications and a proactive implementer of new technologies or tools. She is also a People person and is involved in being a buddy/mentor to her fellow teammates. She is from Coimbatore, India and a passionate artist.

Key takeaways from the session:

1. Testing uncertainty and challenged in today’s world?
2. Approach to pace with QA transformation in the digital world?
3. How AI will impact the testing approach?

Rajni has worked in nearly every software development role - dev, test, DevOps, security, performance and program management in her career. Proficient in developing automation framework with high-quality services, performance engineering and developing strategy for emerging technologies like blockchain, conversational AI, IoT, AR/VR. She is passionate not only about maximizing efficiency in her technical skills and in her strategies, but also, about sharing best practices among colleagues and the tech world at large.

*what is privilege account
*Who are privilege users
*Types of privilege accounts
*Issues/problems
*Safe guards
*Best practices

Cloud Migration is a thoughtful process. There are things to consider like the Migration Strategy, Selection of the 1st Application to migrate, Infrastructure Provisioning, CI/CD, How to cut-off the traffic from On-Premise to Cloud, and many more things. Some of the enterprises have well established patterns for the afore mentioned areas but there are few who are doing it for the 1st time and need help at every stage. This talk will focus on the end to end migration of Workloads to Cloud in General and sharing my experience of migrating few applications to Cloud with AWS as the Cloud Provider.

This talk is about the role of service mesh in general and how Istio in particular works.

It discusses common design and deployment challenges and limitations when someone deploys applications in a container-based platform such as kubernetes.
A lot of these challenges are met by smart use of a service mesh.
A service mesh, like Istio (with Envoy) sits on the top of Kubernetes.
High-level architecture of Istio is explained along with its data-plane and control plane components.
This talk discusses the creation of CRD objects, injection of Envoy containers in pods, the pod creation workflow and how these are leveraged to provide features such as Traffic management, Telemetry, Security and control.

I would be speaking on How to leverage some of the i4Design Thinking tools for Agiler Testing?

The delegates would have an experiential learning in understanding some of the Design Thinking tools for Agile testing.

Sreenath is the Founder & CEO at i4DigitalValue which offers Customized and Specialized Advisory, Strategy and Consulting Services using Design Thinking & Customer Experience for Digital Business Transformation, Robotics Process & Intelligent Automation, Blockchain, Agile Innovations and SAP Enterprise.

Sreenath has 26+ years of experience, including 18+ years in the IT industry, across Digital Business Transformation, Robotics Process Automation, Customer Experience Management, Blockchain consulting, Application Development, Application Consulting/Advisory, Sales, Business Development, Application Management, Application Testing & Quality assurance, Application Transformations, SAP Consulting, SAP Application Management, Solutioning, ITSM/CMMI Consulting, Project Management, Program Management, Delivery Management and SAP Practice Management with strong experience in various Industry verticals like Banking, Financial Services/Insurance, Manufacturing ,Automotive , Telecom ,Healthcare and Travel/Transportation.

Sreenath has acquired exceptional skills on Design Thinking and Customer experience with MIT Sloan School of Management on Innovation of Products and Services: MIT’s Approach to Design Thinking and Problem Framing with Design Sprint and Design Thinking Bootcamp from QGLUE

Aim:
To teach practical ways of creating robust test automation scripts using layered architecture. How to separate the business side from the code of your test scripts and make your test automation closer to user flows.

Learning Objectives / Outline:

Delegates will learn-
Practical ways of creating robust test automation scripts using layered architecture.
How to separate the business side from the code of your test scripts and make your test automation closer to user flows.
How to implement a layered architecture in a variety of ways, using different tools and approaches
Take back a practical understanding of test automation architecture that you can use with any tool or technology.

Having people with varied expertise in your agile team, a layered approach to your test automation can help you leverage their different skill sets and make test automation a smooth, on-going continuous process. To do so, you need to know and understand the three layers of test automation and how to separate the code from the test. Writing tests in the language of the business allows all stake holders to participate and derive value out of the automation process. Let us discuss the correct separation as well integration of these layers and also see a demo on how to implement this with a case study using Sahi Pro.

Nishi is a corporate trainer, an agile enthusiast and a keen tester at heart! With 11+ years of industry experience in Agile environment, she has worked in various roles as a hands-on tester, automation developer, a freelance consulting trainer and currently works with Sahi Pro as the Evangelist and Trainings Head.
Nishi is passionate about training, organizing testing community events and meetups, and has trained hundreds of professionals and teams on agile, test automation, QA bootcamps and DevOps courses.

She is CP-AAT, CP-SAT, CP-DOF, CP-MAT (certified by ATA), Agile Scrum Master ASM (by EXin) and ISTQB certified (Foundation and Advanced Test Analyst & Test Manager) and has been a speaker at many testing events and conferences.

Nishi is also a writer on technical topics of interest in the industry and has numerous articles published at numerous popular forums and her own blog testwithnishi.com where she writes about the latest topics in Agile and Testing domains.
www.linkedin.com/in/nishi-g-02127aa