Test design is not an easy task if you want to find tricky bugs without creating an enormous number of test cases.

In the presentation, first Istvan classifies the defects in a new way. The simplest case is when a single data parameter triggers a failure whenever a program point has been reached along any program path from the data entry point. It can occur, however, that the failure only happens if more parameters have specific values in common. If the number of parameters causing the failure together is two, then the bug is a second-order bug, etc.

Myths say testers should only use TestNG when looking for an assertion framework. Myths say only developers use JUnit and that this framework is only suited for unit testing. Myths say a lot of things, but they are just myths.
The truth is both of these frameworks offer a lot of useful functionality for testers, whether they are ‘QA’ testers or ‘developer’ testers. 

Automated SLO-based Testing as a Self-Service with Keptn: SLIs (Service Level Indicators) & SLOs (Service Level Objectives) are what SREs (Site Reliability Engineers) use in production to ensure changes are not impacting system’s health and availability. Successful organizations are also embracing SLIs/SLOs in their delivery pipeline and in their automated testing strategies. In this webinar, Andreas Grabner will show how you can implement Automated SLO-based Testing as a Self-Service with the open source project Keptn.

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.

Agile software development is growing in popularity and the testing team in the agile projects had to keep in pace with development progress. Agile testing tools vary from project management tools to automated testing tools.

This presentation is designed to discuss the fundamental philosophies of agile methodologies, Automation Testing and Testing Nonstop.

The need for this presentation was born from all the hate for Gherkin, and how it is treated in the automation industry. Nikolaj will pay a small tribute to that framework and its help in test automation rolling out by both more testers jumping on board and client’s education on what is test automation and how it works. Nikolaj is not an advocate for gherkin and in most of the case he would choose non-Gherkin framework, but when you end up with one there are ways to make it work. 

The title may sound trivial or even like a cliche. But in today’s world, whether it is environment or work constant change is a fact. And those changes can be difficult to introduce and manage. So, how to embrace and control them? Not without a reason we have something called Change Management, the whole field dedicated to prepare, support and help with changes.

Based on a case study of the world’s biggest justice digital transformation programme the presentation explains why highly valued SDETs are only part of the answer to the challenge of Continuous Deployment, whereas the skills of Exploratory testers are often undervalued.

Serverless cloud applications are rapidly moving into the mainstream. They offer the advantage of lower costs, faster development, and elastic growth. In this model, teams focus on developing and deploying code on a known technology stack and runtime, with fixed interfaces for application, database, and network. But testing serverless applications brings significant challenges to testers. Because the stack is typically maintained by the cloud provider, it is updated with new versions and security patches on a regular basis. Testers have to continuously test the stack interfaces to make sure that interface integrity is maintained. Further, the serverless model usually incorporates an execution runtime engine, abstracting the running code from the rest of the platform. The database can also be abstracted away from actual data calls. While abstraction is generally a good thing, it can also hide important information during traditional testing. This presentation will explain the architectures of serverless systems and applications and look at challenges testers face with serverless applications, why those challenges exist, and how testers can overcome them. It presents a model for testing both serverless components and entire applications with the context of a serverless runtime.

With a plethora of technologies and disciplines flooding the Testing/Test Automation segment in the past 5 years aimed at improving application quality, are organizations setting up test automation using these tools to derive the expected benefits?

You’ve got thousands of automated tests running, multiple test and coverage reports and logs – but you can’t see the forest from the trees. The problem is you don’t know: is it safe to release? With refined, specific metrics, you can define reports (or dashboard) that tell you the real quality of the product. You can then decide what to do about it.

After executing a project to test a cloud-based microservices platform, we experienced a lot of challenges in both of technical and social manners and tried to develop solutions to cope with them. Finally, we have wrapped them up to make a list of golden rules to successfully manage a test project. The purpose of this talk is to give insights about how a test automation project is managed.  “After executing a project to test a cloud-based microservices platform, we experienced a lot of challenges in both of technical and social manners and tried to develop solutions to cope with them.

What looks like a simple choice in a drop down list, it can turn into a nightmare. Integrating an external mapping service can unintentionally make many of your users unhappy. How can we test websites and apps in disputed territories or partially recognized state?

Three years ago Marta decided to change company and look for new opportunities. She never imagined that would work for a huge Ukrainian software house with over 25 years of experience on the market. The one thing that surprised her the most when she joined, was the set knowledge model that was applied to every developer, business analyst and software tester at the company. Marta started to dig deeper into why it is the first company she knows to build such a tool.