While mobile native apps provide great user experience, and RWD site offer a similar experience across both mobile and web, there is a new and emerging method of developing digital apps, that is called PWA (progressive web app).

Since this app type is new and works on both mobile and web, but adds unique capabilities when consumed on a mobile device like push notifications, no or limited network connectivity, and more, the testing strategy needs to adjust.

In this session, Eran Kinsbruner will walk through the fundamentals of PWAs, and what are the main differences, pro's and con's between these apps, RWD, and Native apps. IN addition, Eran will provide a test methodology that can help teams who adopt this technology to get started and cover the unique capabilities of these apps, like Service Workers, Manifest file testing, and more.

Sometimes it is hard to know what to test in a web application, and the first step before testing is defining what we want to test. This may sound trivial, but in reality this is often not done properly. We tend to oversee the obvious and we test without knowing what we want to accomplish.

What do we want to achieve? Validate user behaviour? Check if the page design is responsive on different devices? Or maybe to know that our web application looks like we expect.

When we know the purpose of our test, we can start planning, coding, executing and improving our tests. But most importantly, we will know what approach we can use to develop the test.

Functional, layout and visual testing are the three pillars of the UI testing trinity. We can use these approaches to develop focused tests, tests that are asserting a specific aspect of our web application.

But how can we identify what approach to use? When should we combine them? There is an information overflow that presents a huge variety of tools that can help us to test through any of these approaches. Sadly, this large amount of information is making us focus more on the tools instead of focusing on the testing strategy.

The intention of this talk is to break in pieces the process of identifying how to develop a focused test, and more importantly, to understand when it makes sense to combine functional testing with layout or visual testing, and what to consider before using layout or visual testing.

The talk will then go deeper through scenarios and code examples that show how to create layout and visual tests. It will also discuss scenarios where a functional test is not enough, or where a visual test is better than a layout test. This talk’s main goal is to offer a different perspective when testing a web application through the UI testing trinity.

If you are interested in how to integrate layout or visual testing to your current workflow, you should attend this talk!

Note: Thanks to the feedback I got after presenting this topic at SauceCon 2018, I have been able to make nice improvements to the content that will be helpful for the attendants.

Most teams would consider quality activities in cycle as a burden that will cause delays and extra work. The outcome is buggy releases to market, negative impact on the product brand and the business.

In reality, Selenium and other open source components make for a fantastic framework to establish solid, reliable test automation. Being able to achieve the necessary coverage reliably is realistic. Fast feedback loop enables developers to correct defects within minutes of code commit, optimizing time spend by devs. These tools can be used from the requirements/design at the initiation of the sprint, through coding, to include production availability and responsiveness.

In this session Amir Rozenberg, director of product at Perfecto, will offer best practices in placing this methodology in place. The audience will learn:

• What are the main challenges for organizations transforming their test practice into agile?
• How to break old notions and put an agile quality process in place? what are the technological and organizational changes that would assist in this transition?
• What are some success and failure stories from real world examples: hotel chain, health insurance company and top retailer

For many years, we have heard discussions around diversity. You may be tempted to think of just one kind of diversity: Where we have marches in the streets, organizations protesting for their rights, new laws being passed, and new organizations being created.

We see something similar in the software testing industry. We see organizations being created to support diversity. We see articles and focus groups dedicated as well. We are even seeing conferences dedicating specific segments of their program to women in testing and selections being made based on diversity. We have listened to the strong opinions from both sides of the discussion. We have heard their cases, and very likely, we have agreed with some of the points at every angle.

And then there are other kinds of diversities we deal within Software Development and Software Testing. More emanating due to the very nature of the work. Diversity in work could mean whole different world for the line of business. As with the other diversity – we have the protests, debates, and disagreements at work too, but it is important that we understand what is the core problem that we are trying to solve. And are we at the end of day adding value to the business?

There are some underlying factors that could help both the situation and be our guiding force to make the system more productive.

In this session, Smita Mishra, will provide a new and enlightening perspective on the diverse world of software testing. She will share her discussions, research, and findings from all angles and leaders within the software testing community. You will learn both the myths and facts around the need for diversity in our industry. And most importantly, you will leave this session with a new way of thinking around how the future looks for diversity in the workplace.

Note : Can do as a 20 minute talk too