As software testers, we accept that each new role will require us to learn new technologies and skills. We also know that we often feel the need (or are told of the need) to provide value to the project quickly. Both of these competing expectations are normal to a certain degree. When Christian joined a new project about testing an API against a European Union standard for payment services, he had to do both to an extreme that he never experienced before.

“The Swag of Performance Testing” shows 4 easy ways to create test suites with different open source tools. From the OpenAPI interface we will create a performance suite into Postman then Jmeter and finally Blazemeter, fully automated and fully functional.

Effective test automation is a key factor in achieving continuous integration, and ultimately, success with a DevOps development approach. However, many organizations continue to point to testing as a bottleneck in their pipeline. The culprit is often the inability to incorporate stable automation in their testing practices. They fall victim to common traps including misunderstanding what test automation is, automating the wrong tests, focusing on UI level automation and failing to provide a stable execution environment. 

Have you ever heard of ‘code smells’? This term expresses the situation in which a certain code characteric might indicate a much deeper problem. Things may seem okay at first sight and everything might appear to work fine, but if you dive in more deeply, it starts to smell more and more and code may even be rotten with low maintainability and bad performance as possible results, just to name a few.

Why IMO QA automation should die as a profession in the future? Dead patterns that are often used by QAs and how to improve test codebase. In short: we will talk about the professional growth of the QA engineer from the perspective of the developer. And is it possible to work together and enjoy this work?

Isn’t is amazing. Stakeholders drop software on our desk and expect us to test it with no requirements, no design and no product knowledge whatsoever. About the only clear thing is the absurd and unrealistic deadline. We are expected to bend over backward, spread magic pixie dust and heroically test quality into a product we never heard of before. But testing in the dark is not impossible – and as Rob Sabourin shows it can even be a very valuable and fun experience.

Developers are testing. This is a fact today. And it’s a good thing. Actually, it’s an amazing thing, as experience has shown that the closer the tests are to the code, the better they are. In this talk I will explain why shifting-left is a good strategy, I will discuss the best practices in frontend and backend development, including the types of tests that give value (unit, component, integration, e2e) in both frontend and backend development, and finally show how developer testing has affected the development and testing workflows in companies that have shifted left.

Are you afraid of testing in production? Do you test in production? Do you use real data? By definition testing in production is hard. This talk puts together Jorge`s experience testing in production a large scale system that affects millions of users. Experience, ideas, limits, roadblocks, tips and more. 

Companies around the world want to accelerate software delivery by implementing or optimizing their DevOps pipeline. Teams focus on things like code pipelines, CI/CD, and deploying to Docker containers, but they often overlook the critical nature of automated testing. Without true Continuous Testing, no amount of DevOps effort can get quality software released any faster.