One of the painful problems in Selenium automated testing is determining whether a HTML page has been loaded. This is especially the case when web application uses a JS  heavy framework such as the popular AngularJS.

During this talk we will discuss how to handle Selenium Page Object pattern better with Loadable Component.

The Loadable Component helps test case developers make sure that the page or a component of the page is loaded successfully. I will share my experience about the concept of the Loadable Component and Page Object patterns.

Building a Test Automation Framework is easy - there are so many resources / guides / blogs / etc. available to help you get started and help solve the issues you get along the journey.

However, building a "good" Test Automation Framework is not very easy. There are a lot of principles and practices you need to use, in the right context, with a good set of skills required to make the Test Automation Framework maintainable, scalable and reusable.

Design Patterns play a big role in helping achieve this goal of building a good and robust framework. 

In this talk, we will talk about, and see examples of various types of patterns you can use for:

1. Build your Test Automation Framework
2. Test Data Management
3. Locators / IDs (for finding / interacting with elements in the browser / app)

Using these patterns you will be able to build a good framework, that will help keep your tests running fast, and reliably in your CI / CD setup!

Problem we faced

Our current project is a mobile app for iOS, Android and Mobile web, which is a mixture of pure native screens and webviews. Each platform has its own tools for UI automation like Calabash for iOS/Android and Watir-Webdriver for Mobile Web. But we wanted to create a generic automation framework which could support each of the  above UI automation frameworks but still reuse as much code as possible and avoid duplicating code between them.

Page Object Model

Page Object  Model was again a natural fit for this framework. Most implementations of POM recommend different POMs for each platform. But we wanted to have a single Page Object Model for all the 3 platforms to ensure maximum code reuse and reduce overall time spent in adding new automation.

Single Page Object Model across platforms

This was complicated because we had native screens as well as webview screens and so it was not possible to use the same Page Object. To solve this, we introduced abstractions for the elements on the screen and encapsulated the respective native driver implementations.

This also allowed us to implement common automation tasks in one place for e.g waiting for new pages to load, so that this code is not repeated across multiple step definitions and platforms. This helped us move to thinking in higher domain level concepts than in terms of low level UI interactions.

Today businesses are changing rapidly and they need to support rapid innovations and changes. Agility in responding to change is the key to success for every business. IT industries are adapting agile software delivery approach and one of the recent and most acknowledged such practice is DevOps. DevOps helps accelerate the TTM, reduce risks and provides continuous feedback. Continuous Testing is the most important and crucial aspect of DevOps which emphasises continuous process improvement.

Today we don't just need test automation. Times today demand a method which will help measure the risk of business failure, and not just a report which show if tests have passed or failed. This impacts not just changes (or upgrades) in technology and tools, but also a change in quality management culture is observed.

Test automation helps us test faster, and provides a mechanism to detect software defects. Though automation can be considered as a pre requisite to continuous testing, continuous testing is much more. It helps provide process improvements that can prevent future defects from occurring. It plays an important role in providing continuous feedback for your software.

BigData with its slew of technologies and terms has been the most talked about area in last couple of years. This has evolved in Big Data Science, Analytics and now on the IoT and automation side. There is a need for testers and QA team to not only get used to this new age digital transformation area but at the same time embrace the technology to their own advantage. We have experimented and successfully used Big Data Technologies – Hadoop and MapReduce for a recent testing engagement. The actual application was implemented using classic technologies like CentOS and C++. Testing team implemented Hadoop and MapReduce to help in quick turnaround for the testing. We would like to showcase the entire case study on how the tools and technologies came in handy for a High Frequency Trading (HFT) application and had we not implemented the same what would we have missed. We would also share the entire CentOS/Hadoop/MapReduce VM with the participants. This would require the attendees to bring their own laptop with at least 4GB RAM (Available) so that they do some hands on exercises that we would like to share.

We see two upcoming trends in the world of software delivery.

1.Docker is becoming a standard for managing infrastructure using containers.

2.Testing code and its infrastructure starts to grow at scale with more complexity, dependencies and technology diversity.

A container is an entire portable runtime environment: an application, plus all its dependencies, libraries and other binaries, and configuration files needed to run it, bundled into one package. By containerizing the application platform and its dependencies ,all differences in OS distributions and underlying infrastructure are abstracted away which makes it easy to share and execute anywhere.

At this talk we will learn how to leverage the container technology to solve the challenges of growing testing infrastructure and continuous delivery with key focus on below items.

• Basics of the containers technology and specifically it’s application on the test automation. 
• How Docker can reduce the time of test execution, ease the setup of clean test environments and drastically reduce the differences between the development, acceptance and production environments leading to the higher quality of the released software.
• Examples to containerize entire testing stack together consisting of major automation tools (selenium, appium, phantomjs), performance tools (jmeter,gatling) with cucumber. 
• Integrating and managing testing container with other application containers to achieve easily manageable continuous delivery pipeline.
• Best practices and patterns for docker success.

A mobile app for every small aspect in our life is the in thing today. Be it talking to your family millions of miles away or simply clicking a picture and letting the whole world know in a matter of few seconds "how good a photographer you are!", there is an app for everything.Business rely on these apps to build brand value, to spread their wings farther and most importantly, to make their customer’s life easy. While, these apps are a great way for the customers to interact with the businesses, it is extremely annoying to the customers when these apps do not function the way they are supposed to. Testing these apps becomes extremely important before of in most cases even after the customer has started using the app. GUIDABLE INCLUSIONS is not just a mnemonic but a framework which lets you explore your app in the best possible way giving you results which you would have normally missed. It helps you look beyond the UI aspect or as they say the "look and feel" of the app and notice how your apps react in response to the way you interact with them or vice versa.
This session dives deeper into the following,
G – Gestures
U – User Scenarios and Usability
I – Integration
D- Devices and Platforms
B- Browsers
L – Location
E- Efficiency

I – Interrupts
N – Notifications
C- Compliance
L- Localization
U –Updates
S – Synchronization
I – Interaction
O- Orientation
N – Network
S- Security

On a Thursday night few months ago, I arrived home for a family dinner, greeted at the door by my mother. It took no more than a few seconds for her to notice that I wasn’t my usual cheery self. She knew the exact remedy to liven me up: a bowl of Mum’s delicious soup and our favorite '80s playlist, which got both of us grooving and singing along. Before long, I was laughing joyfully, my worries and concerns temporarily suspended. These simple steps were so obvious to my mother, yet completely out of the realm of possibility for a computer. Computing applications primarily respond to what you explicitly direct them to do. They can’t observe your mood or feelings and respond intuitively. I couldn't help but wonder back then whether it might be possible to introduce this whole realm of human interaction to human - computer interaction. Could technology be developed that not only understands what you direct it to do, but also knows how to respond to your moods, and emotional cues?

So my the topic goes with " Mind Control Testing " in which their will be a detailed presentation and a demo of 1. What is mind waves? 2. How to read the mind waves and use it to test a quality of application? 3. How it can be used in end user acceptance testing ? 4. How mind waves can be used to improve the quality software and production at the end user level And finally a small demo of my software which will read the brain waves and plot a graph and with a result saying 1. How attentive the user is 2. How cool the user is 3. How many times the user is blinking the eyes While using the application And a lot more fun & interesting things will be added on during the presentation...!

Oculus Rift is a VR system. At the moment it is the market leader in this field. There are other contenders in the VR market such as Gear VR, Cardboard, HTC Vive, but this talk will concentrate on Oculus Rift. Although the testing principles discussed in this presentation will apply to testing in other VR systems.

This talk will cover all the things I have learnt since beginning my testing with Oculus Rift.

Using some of the topics I've talked about on my blog; I will collate these together to give a picture of my "story so far" with VR. Everything I have learnt and what more needs to happen.

I will present different the different scenarios I have encountered and what they have taught me.

I would like to give talk on How the Quality Assurance and Testing is different in DevOps and SecOps World.

Following is the flow of the talk:

• Continuous Delivery and Continuous Testing
• DevOps and SecOps
• Literature Review - A brief about some of the best practices
• System Thinking and How to build Quality and Security into the system
• Architecting for Continuous Delivery
• Build Pipeline and how to make it effective
• Static and Dynamic analysis and inputs to the testing
• Running Security in the Build Pipeline
• Bringing the Operations perspective up in the life cycle
• Continuous Deployment and Monitoring
• Upcoming /Happening Trends (Microservices, Containerization and others)
• Summary and Way forward