ABOUT THE CONFERENCE

Dr. Shankar Ramamoorthy, Customer Success Officer, Harman

Topic Abstract

The author tries to bring the tester of 80s and 90 s marching towards the world of AI , ML and Analytics.The tester is all set to work with the machine , amicably

The tester is ready to meet the machine and the machine is eagerly waiting too, to meet the tester to see how it can learn more from tester.

In a recent Wall Street Journal article, Ken Goldberg, professor of engineering at UC Berkeley, addressed (subscription required) the latter question, introducing the concept of multiplicity to describe how AI will influence future workforces. The common fear that robots will take over the workforce, replacing humans altogether, is an example of singularity, or a single-entity (robots in this case) workforce. Multiplicity, on the other hand, describes a hybrid workforce comprised of a diverse group of robots and humans working together to achieve superior results compared to what either group could accomplish working alone.

This is something we’re already seeing in the real world -- not just in games of Go -- though Goldberg does cite the benefits of human-machine collaboration during recent games. He offers the more accessible and familiar example of multiplicity, as seen in AI-driven recommendations technologies that take input from users (often in the form of clicks, preferences, etc.), then compare that input to statistical models in order to predict and present the content, products or other results a user is most likely to gravitate toward (think Google searches, Amazon recommendations and Facebook content).

This example demonstrates what it looks like for humans to give information to machines, fueling their ability to analyze and take action on information on their own. In most -- if not all -- cases, AI solutions will continue to rely on humans for their initial data sets, but as artificial intelligence applications evolve and become better at gathering and growing their own data, they will become less dependent on humans for ongoing knowledge transfers. But this doesn’t mean they will no longer need humans.

Instead, what’s likely to happen is the emergence of a more symbiotic form of multiplicity, where both robots and machines are dependent on and beneficial to each other to produce the best possible end results. This model acknowledges the fact that there are things that humans simply know and do better than robots. And vice versa.

Ram Shanmugam, Co-founder, CEO & President, AutonomIQ

Topic Abstract

Rahul Verma, Founder & Chief Consultant, Test Mile

Topic Abstract

The talk introduces recent advancements in the core technologies e.g, client side scripting, micro services, protocols, information exchange formats and their role in the coming years (near future). The talk would also take these as basis and some of the pointers raised by AI and ML’s involvement to discuss further evolution of some of the said technologies. The talk indicates how bell bottoms are back in technology areas

The talk is not about general impact of AI. The talk also avoids discussion on fear of AI singularity & AI apocalypse (I leave that to AI experts and bigshots).

This talk is more pragmatic and grounded in the context of software industry. It focuses on impact of the ongoing technology changes on software development and role of developers & testers.

Santhosh S Tuppad, Software Tester & Founder, Test Insane

Topic Abstract

Everyone likes their home to be secure and keep thieves or burglars away. Nowadays, the web has become our home whether you like it or not and it's amazing. However, we have terribly failed to make it secure as we do for our physical home. There are data breaches every day in the news and such news is only increasing day by day. In the Software Industry, we have the demand for more ethical hackers and less supply. If we have to fight the black-hat world, then we got to learn better and practice better with a thinking mindset shift. The bigger question is, "Are we ready to fight?"

In this Keynote, Santhosh Tuppad is going to focus on how black-hat hackers are awesome at what they do and how most of the white-hat hackers in the industry lack the bigger picture of what's going on in the black-hat world in terms of mindset, thought process and thinking patterns. In short, most of us may be barking up the wrong tree instead of doing the things which keep our software secure from the audience such as malicious hackers, blackhat hackers, or anyone with the evil mindset of exploiting the software vulnerabilities.

Key Takeaways:

1. Learn about the things we are missing in the Software Industry in terms of Security
2. How can we start bridging the gap in terms of mindset between blackhat and whitehat hackers?
3. What every software tester can do to contribute to the security of their application being developed?
4. Kickstarting some of the simple attacks and then know about the learning path to take it higher.
5. Fun and Excitement to start the journey in Ethical Hacking World or Security Testing.

Diwakar Menon

LAST MILE CONSULTANTS

Dr. Shankar Ramamoorthy

Harman Connected Services

Ajay Balamurugadas

     Qapitol QA

Santhosh S Tuppad

           Test Insane

Rahul Verma

              Test Mile

Venkata Goday, Technology CoE Lead - Quality Engineering, Capgemini

Karthik Iyer, Senior Manager - Performance Testing, Capgemini

Topic Abstract

With the increased adoption of DevOps there is significant change in the overall testing approach and especially performance testing, traditionally executed last in a waterfall model is now required for every iterative cycle of development. In this presentation we want to want to uncover how performance engineering practices need to cope up with the increased demand by adopting right set of tools, processes, resources and technologies for enabling continuous performance delivery.

Track 2

Dr. Pavan Soni, Founder and Innovation Evangelist, Inflexion Point Consulting

Topic Abstract

One of the key imperatives of successful new product development is concept validation at an early stage. This can not only avoid escalation of commitment in an undesirable direction but also off useful insight on tweaking the product early on. The presentation talks about a host of practices on how quick and dirty prototyping and validation along with customer can be achieved in both B2B and B2C scenarios. Some of these methods are also non-tech in nature and can be performed in rather ordinary situations.

Track 2

Vipin Jain, Tech Lead, Metacube

Topic Abstract

We all know that agile has become one of the most widely accepted and implemented software development methodologies However, still today we hear stories of attempts to implement agile practices fail within just a few months.

The failures can be attributed to many reasons, but one reason that has attracted attention is Work Silos. It has fast become a very common stumbling block for Agile teams.

Having Silos in teams is like a virus which attacks and disrupts the major organ of Agile systems i.e Communication. Agile owes its success to smooth communication. Its like a backbone for the Agile systems that has provided great success for teams around the world. Smooth communication has dissolved geographical boundaries and has contributed the most in its success. Having Silos in teams disrupts the communication and often leads to Agile failures.

In my presentation, I will focus on how Silos enter the Agile systems. I will talk on following factors:

1. Creating teams by functional expertise like DevOps Engineers, Developers, SRE teams, QAs etc
2. Seperation of duties within teams, like product owners define product, then it is turn of developers and then QA comes in picture. In the end, DevOps performs its roles
3. Defined roles bring conflict as they just focus on throwing task to other team over the wall.
4. Async communication between teams often results in taking no responsibility for followups. We depend on notifications from tools and hence develop our own silos.

With this, I will now explain solutions for each of the problems explained above , with focus on how to break existing silos within teams and how to prevent silos to enter teams in future. I will explain how to achieve:

1. Smooth communication
2. Team collaboration
3. Eroding barriers
4. Product integrations

Subheadline: Despite our best efforts, Silos slowly sneak in the agile teams and establish themselves. If not taken care at early stage, they may throw Agile process off the track and disrupt the entire process. To have Agile deliver value, we ensure teams do not develop Silos. Check should be kept from the start. Preventive actions should be taken on the first hints of silos getting inside Agile.

Key Learnings:
a) How to ensure Silos can be stopped entering the Agile Team
b) How to ensure defined roles work without having their own Silos

Track 2

Atul Sharma, Founder, Svatah

Topic Abstract

Behaviour driven development which can trace its roots to Test Driven Development process has been around us for quite some time. In philosophy, it tries to create a synergy between different aspects of the software product development process. It describes a cycle of interactions with well-defined outputs, resulting in the delivery of working, tested software that matters. Testing and test automation are one of key stakeholders of this approach, and rightly so. For any behaviour based approach requires a constant feedback for its continuous improvement. It becomes rather imperative that we should design our test softwares and frameworks which can keep up with this demanding approach.

For such approach, behaviour becomes one of the fundamental unit and we can construct the entire test lifecycle by properly framing and chaining these behavioural units together. If we are able to introduce automation to this process, then it becomes a long term reaping reward where we get benefited not just by having a robust user level documentation which all the stakeholders understand, a validated product with clearly defined user perspective also a regression suite which will help in other functional integrations. Furthermore, this behaviour based scripts could be treated as source of truth for all future developments and/or improvements as they have been vetted by different stakeholders!

Track 2

TBC

Unicom

About Unicom

Dr. Shankar Ramamoorthy, Customer Success Officer, Harman

Topic Abstract

Testers and Engineers work together in SDET model, They can be in same house, joint family like Saas and Bahu together. The author provides 7 effective habits of SDET s..

I am talking of full-stack testers and if they know all this below.. In my opinion, an SDET should have at least the following skills and attributes. He picked up below skills and became SDET ( Software Development Engineer in Test)

• Has a tester mindset, is curious and can come up with interesting test scenarios
• Has a solid understanding of testing principles and methodologies
• Knows that all testing is exploratory in nature and appreciates the difference between testing and checking.
• Can apply appropriate test methods for a given scenario
• knows the difference between testing and QA
• Can code in at least one scripting or programming language (Java and Javascript happen to be the most popular)
• Understands HTTP and how modern web applications are built
• Can write UI as well as API automated tests. One or the other is not good enough!
• Knows Git, Pull Requests, Branching, etc…
• Is agile in nature and knows how testing fits in the agile model
• Can write performance test scripts (Gatling and/or JMeter)
• Thinks about security and is aware of OWASP
• Understands CI/CD and Build pipelines
• Knows the services offered by cloud platform providers such as AWS, Azure and Google Cloud

Puneet Gupta, CTO, GlobalLogic

Topic Abstract

Dr. Shankar Ramamoorthy

Harman Connected Services

Puneet Gupta

     GlobalLogic

Manojkumar Nagaraj

    Capgemini

Bapiraju Nandury, Program Director, IBM

Topic Abstract

Testing in DevOps is an approach to software development that places a priority on ensuring code is tested at all stages of the software development life-cycle.This approach seeks to test code on regular basis to achieve near 100% code coverage. Testing in DevOps consistently makes "Testing" a priority thus shifting automated continuous testing to the beginning of each project or release and continuing it throughout the entire software development life cycle. Continuous Testing is a process in software engineering aiming at providing early feedback to developers which helps minimizing defects or issues faced by end user. It targets the best practices in software delivery: frequent integration, constant readiness, short and frequent build feedback, automated testing and so on. A full blown Continuous test process will build, test, analyze and possibly deploy an application. The team members integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible then followed by system and performance testing to detect defects/integration issues as quickly as possible.

For Continuous Testing to succeed, it requires an automated end-to-end testing solution that integrates into the existing development process, eliminating errors and facilitating true continuity throughout the development life-cycle.

Track 1

Ajay Tikare, Sr. Manager and Quality Architect, SAP

Topic Abstract

ChatOps is the use of chat clients, chatbots and real-time communication tools to facilitate how software development and operation tasks are communicated and executed. In this session, we shall talk about our experiences at

• leveraging the power of a digital assistant/ bot and enterprise messaging tools for bringing in a transparent flow
• freeing up capacity by enabling bots to handle CI jobs
• leveraging chatbots for real time monitoring

Track 1

Manojkumar Nagaraj, Director & Testing Delivery Head, Capgemini

As the RPA market continues to grow at CAGR of 41% to reach a $1.0 BN market by 2020, the adoption is fuelled by promise of faster ROI subject to applicability and deployment policies of RPA in each organization. The RPA 4.0 brings in lot of maturity regarding the process and platform Automation along with Self-healing/self-learning capabilities which opens plethora of opportunities not just in Business process automation side but also, on the Software Automation. Although, we have many functional automation solutions and frameworks that supports automation of various platforms like web, mobile, ERP, API and legacy applications, we don’t have capability to address process/platform supporting the Automation flow and services/test data automation along with it. Also, due to disparate technologies and platforms in large enterprises, customer is forced to choose different automation solutions native to different platforms which has increased the cost of Automation and delayed ROI. As a result, customers are thinking about Tool harmonization using single Automation solution across platforms vs multiple technologies. From our experience, the RPA has demonstrated superior execution capabilities based on the OCR capability (Object character Recognition) and delivered better results when compared to existing Automation solutions like Selenium, UFT and Ranorex. Also, we have implemented RPA across technologies/platforms in the E2E business scenario delivering results exceeding expectation. Hence, RPA has evolved to be a next generation Automation solution delivering the promise of Tool harmonization benefits which is long awaited. Due to current Digital Transformation needs, it is important to drive both shift-left and shift-right Test Automation for coverage and reach. Since most bots are non-intrusive, provides better support for shift-right testing in production which is not possible with tradition Automation tools. The paper talks about the Point of view in Automation Approach using RPA in Software Testing both for shift-left and shift-right use cases involving platforms (ERP, Enterprise Apps, Web Apps, Legacy Apps) and Enterprise Automation involving End-End business scenarios cutting across platforms. Besides, will discuss on Hybrid-Automation approach using bots and Traditional Automation tools in a single DevOps pipeline orchestrating the E2E Automation supporting Continuous Testing approach.

Track 1

Sanjay Kumar Ahuja, Vice President, Accenture

Topic Abstract

Industrial Security in the Digital Age, Securing the Cloud with the Power of 3, and Regulatory Adherence. Key topics covered:

• Security challenges in the Manufacturing domain
• Key security concepts that must be considered when assessing and implementing IX.0.
• Key security considerations regarding regulatory adherence with GDPR and NIS
• Few examples of how cybersecurity is implemented in Industry X.0 clients

Track 1

Shubhradeep Nandi, Co-Founder, PiChain Innovations

Topic Abstract

Track 1

Raghuram Mavatur, Principle Consultant, TechMahindra

Topic Abstract

With IoT platforms picking up, it’s not only computers that connects each other but also the “Things” that connect up. IoT playing a pivotal role for taking the automation to the next level in multiple domains like Banking (Contact less payments), Automobile (Connected cars), Manufacturing (factories), healthcare(Personal Healthcare) etc. The volume expectations of these on the systems are logarithmically exponential as high as 4000 requests per second! Most of these systems are green field implementations that include technologies like Cloud, Mobile, Microservices, sensors etc. posing questions on the scalability and performance of these platforms. This paper talks about need for performance testing of Connected Things platforms, the tools, process and best practices to evaluate the performance accurately.

Track 1

Unicom

About Unicom

Dr. Shankar Ramamoorthy, Customer Success Officer, Harman

Topic Abstract

Testers and Engineers work together in SDET model, They can be in same house, joint family like Saas and Bahu together. The author provides 7 effective habits of SDET s..

I am talking of full-stack testers and if they know all this below.. In my opinion, an SDET should have at least the following skills and attributes. He picked up below skills and became SDET ( Software Development Engineer in Test)

• Has a tester mindset, is curious and can come up with interesting test scenarios
• Has a solid understanding of testing principles and methodologies
• Knows that all testing is exploratory in nature and appreciates the difference between testing and checking.
• Can apply appropriate test methods for a given scenario
• knows the difference between testing and QA
• Can code in at least one scripting or programming language (Java and Javascript happen to be the most popular)
• Understands HTTP and how modern web applications are built
• Can write UI as well as API automated tests. One or the other is not good enough!
• Knows Git, Pull Requests, Branching, etc…
• Is agile in nature and knows how testing fits in the agile model
• Can write performance test scripts (Gatling and/or JMeter)
• Thinks about security and is aware of OWASP
• Understands CI/CD and Build pipelines
• Knows the services offered by cloud platform providers such as AWS, Azure and Google Cloud

Puneet Gupta, CTO, GlobalLogic

Topic Abstract

Dr. Shankar Ramamoorthy

Harman Connected Services

Puneet Gupta

     GlobalLogic

Manojkumar Nagaraj

    Capgemini

Suman Mitra, Manager, IBM

Chandrakala Subramanyam, Technical Lead, IBM

Topic Abstract

Makeover story
This presentation addresses the makeover story from the perspective of Eclipse OpenJ9 at AdoptOpenJDK , particularly: - i) challenges involved with the in-house (third-party tools) tooling & testing, such as
a. Tests spread across multiple repositories
b. Adding tests in CSV’s in specific format, located in a specific repository
c. Changing wrappers and variables located in a different repository
d. Maintaining multiple versions of tests
e. Building local sandbox for tests & wrappers, testing them and then commit the changes in repository.
Do they look challenging, time consuming and a bit of manual in nature? Many more challenges to be discussed, same will be explained in detail during the presentation.

iI) how OpenJ9 opensource testing was enhanced to make it more adaptable towards the open-source third-party tools and products?
Our presentation will shed light on how these enhancements were achieved using git, docker and Jenkins.

iii) how the test enhancements were achieved with reduced cost and complexity.
We will present on how these enhancements were done using our opensource Jenkins test framework. While the open testing story is still evolving, the initial benefits of the much-needed makeover far outweigh the costs and serve as an example to inspire improvements and innovation for those facing similar challenges.

Track 2

Anupam Gupta, Head of Engineering & Lead, Robert Bosch

Topic Abstract

Track 2A

Priyesh Ramaiya, Director Of Quality Assurance, NetApp

Topic Abstract

Track 2

Kandeel Chauhan, Testing Lead, Naukri.com (Infoedge India Ltd.)

Topic Abstract

What is the future of Testing? What are the new skill sets the testers must acquire to thrive in the future? These are a few questions frequently asked and addressed in seminars, summits and forums. While I firmly believe that the future of testing lies in shifting the test process left - testers taking up a role of facilitators and building tools to help developers test as early in the cycle as possible, there are a few testing basics that cannot / should not be compromised at any cost. We need to invest in developing the ‘tester mindset’. ‘What needs to be tested’ will always come before ‘how it needs to be tested’.

With the QA teams constantly evolving and moving towards the future, we found a way to raise awareness and keep the team focused on the basics. We called it the ‘Flavor of the Month’. Each month the team was given a flavor for example “usability testing” and the team set out to identify usability issues In the site. In a gamified environment the team was given a monthly task to identify issues related to the current flavor, A ‘tester of the month’ award was given to the best performer. Few of the flavors were: ‘Security testing’, ‘performance testing’, ‘implicit requirements’, ‘compatibility testing’.

Covering various aspects of testing we were able to bring the focus of the team back to ‘What needs to be tested’. We have seen an increase in issues being logged against these themes even after the month of focus was over which leads us to believe that we have been able to make inroads in taking the team back to the basics

Track 2

Subhadeep Chakraborty, Head, Testing Presales, TechMahindra

Dnyanesh Belitkar, Solutioning & Delivery Head, TechMahindra

Topic Abstract

Much of our day to day technology is powered by AI - It is the study of agents those who perceive the world around them, form plans, and make decisions to achieve their goals. Machine Learning is a sub field under AI. Its goal is to enable computers to learn on their own, without explicitly programming for each and everything. In this talk, we will specifically discuss “What does it mean to a testing community, how would it change the way we are testing?”. We will demonstrate our approach on AI/ML based Quality Assurance in TechM in the talk which is design based compliance with following steps – Discover > Learn > Sense > Respond cycle

Track 2

Sanjay Kumar, ChroPath Creator and Product Evangelist, AutonomIQ Inq

Topic Abstract

Join Sanjay Kumar, the creator of the ChroPath. Learn how ChroPath generates the automation script just in single clicks in seconds Learn how ChroPath saves more than 40hrs in a month for a automation developer See why developers calls ChroPath lifesaver and how it became the best XPath extension See why ChroPath has more than 150k users in such a sort time. Get to know the upcoming features in ChroPath

Your Bio :Sanjay Kumar ChroPath Creator | Product Evangelist @AutonomIQ Twitter: @SanjayKumaarr | LinkedIn: https://www.linkedin.com/in/sanjay-kumar-445a9658/

Track 2