What value do we provide as testers? The short answer is that testing has no value in itself, testing is a service we provide to our teams so that our company can deliver value-adding products or services. In this talk, Joel will briefly review the forces pushing forward the changes in the way we create and deliver products today. He will introduce (for those who have not heard about them before) the Modern Testing Principles. And he will review them to understand their challenges and breakthroughs! 

Prometheus, one of the ancient titans of Greece, once stole the fire from the Gods and taught people how to use it. Likewise, in this talk, Finn will describe how you as QA-Titans can teach Quality to designers and stakeholders and pair with developers and business. He will also share the secret how to keep quality in everyone’s mind on the way from idea to production for every individual story as well as the entire product.

As in the movie HomeAlone, it seems that Dev and Ops have gone on a journey and forgot to take testing/QA with them. We hear big companies tell stories that they have no more testers, all testing is done in production, everything is fully automated by dev, etc. The actual truth lies somewhere in between these statements!

The acceleration of our digital transformation challenged us on our capability to deliver fast and reliable software. Our e-commerce platform being at the center of our UX, delivering on a weeks basis was not acceptable. We will share the journey and learnings leading us to deliver with confidence on a daily basis our platform with 6000+ functional and automated tests.

After presenting his session “Eight Ways to Ruin Your 1-on-1s” at Stareast and SQuADCon Denver in 2019, attendees told Jason one particular area of discussion needed more attention: feedback. This session will be the session everyone knows they should attend but would like to avoid! Providing feedback is a necessary skill for individuals, teams, and organizations to grow, yet studies suggest 69% of managers are uncomfortable communicating with their employees and 37% of business leaders are afraid to give performance feedback. Although these numbers only address managers, we all need to show leadership by providing feedback to those around us in all directions.

We’re known for breaking things and testing the limits, and patience, of our team and our systems. We advocate for quality in all things and we advocate for the end user. But, none of us actually think about how our varied backgrounds influence what we do and how we test. In this session we’ll explore how our previous (and current) experiences subconsciously affect our testing and how to bring those experiences to the forefront in order to be better testers all around.

Unit testing is fine, but without proper integration testing, especially if you work with external resources like databases and other services, you might not know how your application will actually behave once it has been deployed to the real production environment.

Before Docker, configuring the environment for integration testing was painful – people were using fake database implementations, mocking servers, usually it was not cross-platform as well. However, thanks to Docker, now we can quickly prepare the environment for our tests.

Testing a well known software like Elasticsearch is not too different to any other software. In this session we will peak into the different testing strategies for unit and integration tests including randomized testing, how we leverage gradle, how we do packaging tests, how we test the REST layer, what our CI infrastructure and tooling around that looks like and finally what happens in order to release Elasticsearch and other products of the Elastic Stack.

Software testing is becoming increasingly important because more and more products are software intensive. Cars, for example, contain Electronic Control Units (ECUs) that is networked with each other. However, software problems can delay commissioning by months, even years, because the different components are not coordinated with each other. A timely system test would help, but there is a lack of time and resources. The functionality of the software is simply too great for manual testing. So, you must automate.