Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

When you are writing Selenium tests to check for elements on your page, by taking the classic approach (checking for each element’s properties at a time), you might get to a large number of assert steps, one per each property you are checking. This increases the lines of code your tests have, make the tests difficult to maintain and tricky to read.

Wouldn’t it be nice if the actual checking part of the test would be small, perhaps one line of code? With the approach I am going to present, you can do just that. Hence your tests will be small and clean. All you will need to do is model the pages/modules/items by using an Object Oriented approach within your actual tests.

A workshop on Selenium and Java.

Key takeaways:

Representing the modules or pages to test as Java objects;

Generating the expected and actual results for your tests based on these objects;

Comparing the actual objects with the expected ones will lead to a very short number of assertions in your tests.

Prerequisites:

Participants are required to bring a laptop with appropriate software setup - please see instructions from here:https://goo.gl/S5RwwZ.

United Kingdom

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

The rise of new architecture styles such as SaaS and microservices leads to an increase in popularity of API testing. With this, automating the API testing is a natural next step. Yet, how to manage this properly so that the benefits outweigh your general equivalent WebDriver solution in terms of ease and stability? Join this workshop to learn how to put together the basics of an API checking framework that is robust, easy to read, and eliminates the brittleness in your checks. The workshop covers making GET, POST and more advanced HTTP requests, setting custom request headers, easily building payloads and parsing responses, and tying all this together in scenario-based checks.

Key takeaways:

Participants will learn:

How to build a framework that can execute a series of HTTP requests that can be asserted on

How to use DRY techniques when structuring the framework to build a framework that is robust and easy to maintain

How to execute complex scenarios that require multiple HTTP requests and sharing data across requests

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

As mobile devices, tools, operating systems, and web technologies rapidly evolve, testers must quickly adapt their thinking in this changing domain. Testers often struggle to find important vulnerabilities and bugs in mobile applications due to lack of guidance, experience, and the right resources. During my career in the mobile testing field, I've come across numerous bugs related to mobile native applications. Looking at these bugs, I started categorizing them, and have since come up with a mind map. This mind map helps to do a quick tour of your mobile application and find vulnerabilities as quickly as possible (http://www.rajsubra.com/2015/01/16/native-app-testing-cheat-sheet-quick-... ). This could be used for doing smoke testing, acceptance testing or even production testing after your application is live on the different App stores. This session will give attendees hands-on experience by using these mobile testing approaches in real applications to get quick feedback.The different topics covered and format of the workshop would be as follows (There will be hands-on exercises in different sections of this workshop)

Basics of the mobile eco system

Will quickly cover what are web, native and hybrid apps with live examples

Testing Approaches to get quick feedback on the mobile application

Will cover the following testing approaches with exercises and screenshots of real life defects

Interrupt testing

Wi/Fi 4g switching

Testing end user scenarios

How to use logs and what kind of information we can get in both iOS/Android

Looking for Consistency

What are different types of keypads in mobile applications and how to identify these differences

How to do performance testing in iOS/Android

Why are User Reviews important and what kind of issues can be uncovered

Installation Testing

Battery Life/Storage

Will touch upon the following topics

Mobile security

How to make apps smarter

Automation tools available for free

Will cover Appium framework on a high level

Show a demo of an app automated using Appium and how it works

De-mystifying Internet of Things

Cool things coming up in mobile and how it can impact our testing

Questions will be handled throughout the session in an interactive manner.

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

Code that grows over time without refactoring can get quite messy and hard to test. The same applies for to test code, and curiously, they often appear together. Not always is it possible to fix the design problems first, creating a need to write clean tests for hard to test code.

In this workshop, participants will learn some techniques to clean up messy JUnit tests to make them more readable and easier to change.

After a short introduction and an example refactoring, participants will work in pairs to refactor some example unit tests and learn how to write better ones from scratch.

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

- Q: How much JavaScript can you learn in just 2 hours? And in such a small amount of time what could you use it to do?

- A: You can learn just enough to be dangerous, and you can use it to do things you're not supposed to do. And because we're learning this to improve our testing, that will all be just fine.

To make things fun, some of the things we will do are:

interact with simple example games using JavaScript

cheat in 'real' browser based games, e.g. infinite lives etc.

And to justify this to your boss, we will:Use real JavaScript applications, written in frameworks such as React and Angular, and manipulate them, and their data, from the browser console.

By doing this you will add a powerful, and incredibly underused, set of capabilities to your testing skill set.

All in only 2 hours. Prepare to move fast.

Requirements To take part:

you WILL need a laptop

you WILL need an updated browser installed e.g. MS Edge, Firefox, Chrome. I recommend Chrome and it will be used in all the demos in the workshop, the basic techniques will work in any browser but if you are new to using JavaScript and Web Developer tools then you will find it easier to follow the instructions if you have Chrome installed.

we WILL need an internet connection to the outside world - but you don't have to worry about that

United Kingdom

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

The rise of new architecture styles such as SaaS and microservices leads to an increase in popularity of API testing. With this, automating the API testing is a natural next step. Yet, how to manage this properly so that the benefits outweigh your general equivalent WebDriver solution in terms of ease and stability? Join this workshop to learn how to put together the basics of an API checking framework that is robust, easy to read, and eliminates the brittleness in your checks. The workshop covers making GET, POST and more advanced HTTP requests, setting custom request headers, easily building payloads and parsing responses, and tying all this together in scenario-based checks.

Key takeaways:

Participants will learn:

How to build a framework that can execute a series of HTTP requests that can be asserted on

How to use DRY techniques when structuring the framework to build a framework that is robust and easy to maintain

How to execute complex scenarios that require multiple HTTP requests and sharing data across requests

Prerequisites:

There will be a voting done in the beginning of the session which will determine which language will be used in this workshop - Java or Javascript. Participants need to be prepared for both outcomes. So participants are required to bring a laptop with following setup done:

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

When you are writing Selenium tests to check for elements on your page, by taking the classic approach (checking for each element’s properties at a time), you might get to a large number of assert steps, one per each property you are checking. This increases the lines of code your tests have, make the tests difficult to maintain and tricky to read.

Wouldn’t it be nice if the actual checking part of the test would be small, perhaps one line of code? With the approach I am going to present, you can do just that. Hence your tests will be small and clean. All you will need to do is model the pages/modules/items by using an Object Oriented approach within your actual tests.

A workshop on Selenium and Java.

Key takeaways:

Representing the modules or pages to test as Java objects;

Generating the expected and actual results for your tests based on these objects;

Comparing the actual objects with the expected ones will lead to a very short number of assertions in your tests.

I started writing this while downloading MacOS Sierra, the first MacOS including the intelligent personal assistant and knowledge navigator Siri. I'm expecting a lot from it and not the least a boost to my productivity. Well, not exactly. It's all about fun isn't it? Well, perhaps a little bit of both. :)

The reason why I'm writing this to Nordic Testing Days is that I'm going to start using Siri as my co-pilot when doing exploratory pair testing. Yes, my co-pilot will be one of the most advanced, if not THE most advanced commercial AI solution in the world, and I'm going to make her work her a** off. We'll have good days, bad days, educational days and above all, fun days ahead of us. We will present the fruits of our work, and invite everyone to the ultimate mob testing session, where Siri's capabilities to work as our teammate will be put to the final test.

Key takeaways:

At least I'm excited to see how well Siri fares as a co-pilot in pair testing, and I believe someone else might be too. Of course the participants will leave with a good understanding on how pair testing (and mob testing) works and how it could be used in everyday lives, but the meat is to bring AI to the game. I've never done anything like this, so anything can happen. :)

Note:

Bring your Mac laptop (with Siri), if you have one. All Siris are welcome.

We know that testing depends on context. We need to apply context also in our testing strategy, depending on where we are in the process – Are we in the beginning of the project, or towards the end? Are we testing for user experience, or functionality? Do we need automation at all, or maybe we’ve got so much automation, we’re already thinking on how to test our app on production servers?

The way we’re thinking strategically about tests is at the heart of this workshop. We’ll talk how to plan testing in different scales – from a “release”, to a feature, from stories to a micro-drop. We’ll discuss testing MVPs, the risks in the specific level, and testing in production. When our context changes, so does testing.

In the workshop, we’ll do planning exercises at the appropriate scale for the different stages, and discuss the differences and nuances we’re interested in. The discussion is collaborative and everyone brings their own experience – the best way to learn.

In the end, you’ll learn on how to choose the right resolution for testing, and pick the right strategy, level of reporting and focus in order to make the most of our already limited testing time.

Key takeaways:

Making a test plan is about ROI, making use of limited time and resources

We should plan testing efforts in the context of where we are in the development process

The information we need to give based on our testing and its resolution also relies on where we are

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

Code that grows over time without refactoring can get quite messy and hard to test. The same applies for to test code, and curiously, they often appear together. Not always is it possible to fix the design problems first, creating a need to write clean tests for hard to test code.

In this workshop, participants will learn some techniques to clean up messy JUnit tests to make them more readable and easier to change.

After a short introduction and an example refactoring, participants will work in pairs to refactor some example unit tests and learn how to write better ones from scratch.

Key takeaways:

create complex objects easily with the builder patternuse hamcrest matchers to improve your assertionsdiscover the power of JUnit rules

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

As mobile devices, tools, operating systems, and web technologies rapidly evolve, testers must quickly adapt their thinking in this changing domain. Testers often struggle to find important vulnerabilities and bugs in mobile applications due to lack of guidance, experience, and the right resources. During my career in the mobile testing field, I've come across numerous bugs related to mobile native applications. Looking at these bugs, I started categorizing them, and have since come up with a mind map. This mind map helps to do a quick tour of your mobile application and find vulnerabilities as quickly as possible (https://goo.gl/JtJU7w). This could be used for doing smoke testing, acceptance testing or even production testing after your application is live on the different App stores. This session will give attendees hands-on experience by using these mobile testing approaches in real applications to get quick feedback.The different topics covered and format of the workshop would be as follows (There will be hands-on exercises in different sections of this workshop)

Basics of the mobile ecosystem

Will quickly cover what are web, native and hybrid apps with live examples

Testing Approaches to get quick feedback on the mobile application

Will cover the following testing approaches with exercises and screenshots of real life defects

Interrupt testing

Wi/Fi 4g switching

Testing end user scenarios

How to use logs and what kind of information we can get in both iOS/Android

Looking for Consistency

What are different types of keypads in mobile applications and how to identify these differences

How to do performance testing in iOS/Android

Why are User Reviews important and what kind of issues can be uncovered

Installation Testing

Battery Life/Storage

Will touch upon the following topics

Mobile security

How to make apps smarter

Automation tools available for free

Will cover Appium framework on a high level

Show a demo of an app automated using Appium and how it works

De-mystifying Internet of Things

Cool things coming up in mobile and how it can impact our testing

Questions will be handled throughout the session in an interactive manner.