When it comes to creating a project we always search for ideas that are open-source, easily scalable, ready to use.

We as humans always have a tendency to grow and expand and when it comes to customizable infrastructure it's a big Yes.

In this talk, we will be focussing on how we can save the cost of actual servers with easily scalable and manageable open-source software using an open-source tool - selenium grid. How we set up the nodes and hub altogether to make cross-browser, multi-platform execution takes place.

This talk will answer the questions "Will you be able to run your automation scripts without connecting the USB cable to your device in a limited range?"

If we have to ask ourselves where is the mobile and when is it required? So the answer would be its 'Everywhere'!!

It's next to possible to imagine a day without looking at mobile or using apps for that matter- Google, Facebook, Whatsapp, etc.

When it comes to using it so testing comes hand-in-hand with it. As we develop applications over a mobile device, be it any platform ios, Andriod and windows we shall also think about usability and end-to-end testing.

In this talk, we will discuss how Appium worked as a bridge between devices and controllers.

Software Craftsmanship is a practice of continuous development and helping others learn the craft. As the world is evolving towards the era of scripting language, we will be sharing our experience of how we have grown as a team of all QA with programming language background to the niche typescript world contributor.
During this talk, we will be focussing on the shift of existing selenium to the actual implementation of Protractor test API. How and when to use a protractor? When to pick protractor as an automation tool for building a framework.

By the end of the session, one will be able to understand how can we start working on end to end tests for any JavaScript and TypeScript based application using Protractor, Cucumber framework, and Page Object Model design pattern.

We will also talk about configuration files, cucumber, typescript, promise handling in protractor.

In manual testing, we play with our application by running the same tests with different input data. This helps testers to increase test coverage and uncover unexpected bugs. This is not true for automation, where we usually hard code the data we wanted to test into our test function. This reduces the efficiency and effectiveness of our automation scripts which keep executing a scenario again and again with the same set of data. As a result, they rarely find bugs after few executions and bugs that are not in the script execution path or data that we are using in the automation. However, if we add randomly generated data, just like manual testing, we increase our chances of finding new bugs or interesting information with every execution. Test Spicer helps to add this spice to our automation.

In this session, we will discover how Test Spicer can be used for common tasks like data generation and help allow teams to find gaps in manual testing.

TestSpicer helps to provide test ideas to make sure that apparent things related to quality are never missed.

In Agile teams, as developers are able to deliver new features even faster, Testers also need to find a way to implement test scripts quicker. Design Patterns can help with that, as they provide a reusable solution to commonly occuring problems. In this session, we would demonstrate the advantages of using patterns and how we can apply Page object model and Factory patterns to speed-up test script creation.