You are here

Puupakusaal

Mobile Test Automation Using Cify Open-Source Framework

Nowadays developing apps, or any other software, requires a smart testing approach. Because of that testers, test leads and any professionals in charge of a testing projects have to answers some basic questions before they start. What tools do use? How to automate on different platforms? What’s the smartest way to approach the project? Usually it means some form of compromise - changing a tool, framework or learning a different approach. What if it was possible not to make compromises, but instead use the skills and tools you know and love? 

It is.

FOB Solutions managed to run one test across simulators, emulators as well as android and iOSs devices using Cucumber and Cify open-source test automation framework. And now we are going to teach how to create cross-platform UI tests as well!

You can see a preview of what we will teach if you follow this webinar https://saucelabs.com/resources/webinars/cucumber-and-sauce-labs-a-non-compromise-duo

Key takeaways:

Building cross platform test automation framework

  • More similar user flows on software built on different platforms
  • For underlying technologies we chose to use open source components:
    • Appium
    • Selenium
    • Cucumber
    • Groovy/Java
    • Gradle

Using cross platform test automation framework

  • Behaviour driven approach - building tests using cucumber
  • UI types/different screen sizes

Executing cucumber level tests on cross device-farm approach using SauceLabs example

  • Executing same tests on different device farms (saucelabs/test object)
  • Integrating cucumber with saucelabs/testobject

 

Prerequisites:

  • Computer with a pre-done setup - instructions will be added 2 weeks before the conference

CSS Selectors: From Zero to Awesome

When writing Selenium tests, you need to identify the page elements by using some kind of selectors. XPATH, although much more complicated than CSS, seems to be preferred by many. Either because testers have tools that automatically extract them, or because they seem to clearly specify the path of the element.

In this workshop i will go over the benefits of using CSS instead of XPATH. I will show a ton of examples (with Java), from the easiest and simplest, to the most complex or even impossible. The purpose of the workshop is to get hands-on experience with identifying the CSS selectors for a wide range of cases, which will lead to you dropping XPATH altogether.

Key takeaways:

  • The purpose of the workshop is to familiarize the participants with the concept of CSS selectors, and inspire them to use them (instead of Xpath selectors) in all their Selenium tests
  • The workshop focuses on identifying the CSS selectors, from the most basic and easy ones, to the most complex ones, and to use them as part of automated tests
  • This will be a technical workshop, with exercises that the participants can do on the stop, or they can follow as i do them. There will also be room for questions and exercises proposed by the participants

Save time: use Selenium Grid

We know Automation Test bring value to the Quality of our project, but the projects are every day get more complex. We, as QA Automation Engeeniers, have to embrace complexity. One basic step to get an Automation Test Suite which bring real value is to parallelize our tests and reduce x2, x5, x10 the duration of them. 

In this workshop, we will cover the theory behind Selenium Grid (How is working, what is a hub, what is a node) in the first part. In the second one, we will put hands-on and teach how to configure and connect the Nodes with the Hub. Last part of the workshop will cover how to connect a basic Automation Test Suite (which we will provide) to the Hub.

Key takeaways: 

  • Theory about Selenium Grid.
  • Configure and connect the Nodes whit the Hub.
  • Run the Hub and Nodes on Docker Images.
  • Setup a Test Suite to run on the Nodes.
  • Tips and tricks to avoid usual mistakes.

Unit testing for non-coders

Unit testing is a fundamental part of software development, providing fast feedback and driving the design of the code. Despite that, in many places it is considered to be a “developers only” domain. The commonly ignored truth is that testers can contribute to unit tests and get a lot of value in return - even if they don’t code.

In this workshop  we’ll learn how to approach unit tests, how to scope our focus and and use our testing expertise to make them better. We’ll practice reading unit tests like English and review them for missing or excessive parts as well as some tricks to quickly add some tests to an existing suite.

Not convinced yet? Come and see how unit tests are also a great tool for code-review, for improving your coding skills and you’ll be surprised by the amount of  bugs that can be found and dealt with earlier than ever, leaving everyone around with more productive time.

During the workshop the participants will be going over (java) code, revewiewing unit tests to spot multiple types of issues both in the unit tests and in the application code through it and even add some tests of their own. 

Key takeaways: 

  • Strategy for reading unit tests
  • What can a (non-coding) tester contribute, and how?
  • Why care about unit tests if I’m not a coder
Subscribe to Puupakusaal