“Software runs the world,” according to agile guru Robert Martin.
If that’s not quite true today, it will be tomorrow. Continued advances in robotics, big data and machine learning, coupled with ever cheaper and more compact CPU and memory, have extended the reach of software systems into every aspect of people’s lives. Complex algorithms and learning systems are taking over critical decisions that used to be made by people.
Some software is just fun or harmlessly useful. Systems help us develop and test other software. Software runs our dishwashers and our ovens, our home heating systems and our clothes washing machines.
The potential benefits of all this software are enormous. But so are the risks. With increasing complexity come systems that are difficult to understand, predict the outcomes of, and manage. Safety regulations and standards have not kept pace with the technological advances and sheer ubiquity of software systems. And some very complex and unregulated systems—such as those operating cars—are safety-critical.
Your car may have 100 million lines of software code conveying messages from your feet on the pedals, your hands on the wheel—and its own sensors—to the actual mechanical systems that (just barely) run the car. Such software is not always trouble-free. In one case, investigators of a popular car model found “spaghetti code” with software errors that could cause sudden unintended and uncontrollable acceleration. In another, hackers remotely took control of a car’s brakes and steering via its internet-enabled entertainment system.
Even regulated medical devices such as heart pacemakers have ways they can be hacked. And some experts are concerned that the vast connected electricity grid in North America could be at risk because of the multiplicity of contributing utilities, some of them small and not as cyber-security conscious as they could be. In 2012, safety systems expert Nancy Leveson wrote, “We are attempting to build systems that are beyond our ability to intellectually manage.” We have built many more since then. Where will testers be in a world run by software? What new skills and knowledge will we need? Our roles are changing, but some things haven’t changed. Testers still know that there is no bug-free software. We know that a simple software error like a typo in code or a misinterpreted requirement can sometimes result in disaster. We have the mindset to imagine what could go wrong before a catastrophe happens and help to prevent it.
In this keynote talk, Fiona Charles will talk about what we can do to test for a safer world, and what we need to do to get there.
Continuous Delivery and Continuous Testing concepts are here for a while now. They sound nice and easy but in practice they are dirty and sometimes hard to apply because they require a sense of pragmatism and giving up to perfectionism. We still test unnecessary scenarios just to be sure and we still create unit tests just because this is what developers must do, and we are still looking for 100% test automation coverage just because this sounds seductive. The result: delayed releases, waste, downtimes, frustration.
In this talk, Dana Aonofriesei will present several software quality principles, according to her own personal discovery and research, which arise when applying Continuous Delivery, DevOps and Continuous Testing philosophies. She’ll show you ideas and examples of successful and concrete actions towards testing in the world of fast and continuous delivery.
The Futureproof Tester: How to deal with blockchain-based applications
Blockchain is open source, decentralized and disruptive. Due to the cryptocurrency hype, an explosion is expected for software using this technology in 2018 and mainstream use by 2023.
Testers need to be ready to assess specific risks associated with software based on decentralized tokens like Bitcoin and Ethereum. We need to be future-proof! The main feature of this technology is decentralization. It’s book-buying without Amazon, taxi-sharing without Uber and especially it will be software development without outright ownership of a database.
In this talk, Saane Visser will show testers how to stay ahead of the game and not get disrupted from the business. She will explain the unique risks of decentralized applications (dApps) using familiar attributes availability, integrity, maintainability, etc. and will show you how to take advantage of this, develop a new specialism, and become a blockchain tester!
Sanne will share her excitement about blockchain, where you will become familiar with the building blocks for testers, understanding the blockchain framework. After this talk, you will have a solid framework for assessing dApps, where you will be able to explain the trade-offs between traditional databases and decentralized databases. But most of all, you’ll leave this talk being excited about blockchain and its potential.
CognitiveQA: Artificial Intelligence assistants for testing, the new reality!
Artificial assistants with the intelligence to learn, evaluate alternatives and make decisions are now-a-days an expanding reality, that have so much potential for different areas. Can you imagine an assistant with artificial intelligence to support the testing and quality of the software? Are you ready for this new reality?
The accumulation of data in the activities of development, testing, analysis of user experience, and customer support can be converted into analysable information with Business Intelligence (BI), thus opening the door to prediction, to the use of techniques of artificial intelligence (machine learning, neural networks, statistical components, etc.), and to test automation, to automatically attend the activities of quality assurance in an intelligent way.
Now-a-days we have enough experience (data accumulation) and reasoning ability to work with predictive models to automate actions conditioned to previous cognitive processes. With this, we can now select candidate tests to be automated, optimally allocate execution resources for iterations, prioritise the execution of test sets according to associated risk.
In this talk, Albert Tort will present an innovative CognitiveQA solution to increase the efficiency of your testing and to anticipate tests in iterative contexts and in DevOps environments.
Key factors of integrated test automation in DevOps
Agile approaches and the DevOps culture have transformed the testing activities and the software's own quality. We must reformulate both the objectives of the tests and how to conceptualize and implement them.
In this talk, Aurelio Gandarillas will expose the key elements that guide the automation of tests to be integrated into a DevOps pipeline as well as presenting the available options to approach the common difficulties of test automation projects.
Microservice architectures have changed how companies develop and deploy applications, and have therefore in turn affected the testing process as well. New techniques have now emerged and others have been enhanced, while old testing techniques (used in monolith) drive us to a dead-end when we try to apply them to a microservices architecture.
In this master class, Alex Soto will introduce some testing techniques, such as service virtualization, contract testing and testing in production to increase deployment velocity from 1 week to N times per day and deploy each service independently without worrying about breaking the compatibility between services. He will show you several examples in Java but will also point out resources for other languages as well.
After this theoretical and live code master class, you'll understand how to test microservice architectures and reduce the friction between trying to apply old testing techniques to a new paradigm.
Why software security has gotten worse? And what can we do about it?
As technology evolved, software security faced huge challenges and as the years passed, the world has seen drastic changes far too quickly. And along with these advancements, even black-hat hackers or malicious hackers have evolved also very well. Today, the internet is the place for everyone where hackers dwell almost all the time. Every day new applications are released to the web and users start using them and even get addicted to them due to outstanding UX. But, wait! Did someone think about the "security" layer of these applications? Well, we often don’t and most of the applications today suffer from "beggarly / bad security".
In this talk, Santhosh Tuppad will focus on the pitfalls of bad security and why software security has failed in a pretty way. He will also shed light on how your users may be facing bigger problems than you can imagine due to bad software that lacks security testing. He will also demonstrate some of the lethal problems that exist in the industry and will talk about technical impact, business impacts like reputation damage, revenue loss and a lot more.
Not only that, Santhosh won’t end his talk without some hacking demonstrations that will for sure wow you. Finally, he will tell you how you can start security testing from day 1 and start contributing in terms of building secure software.
From this talk, you will gain an understanding about the problems that a lack of security testing presents and you find out about tool-assisted security testing; performing security tests through questioning. After the talk, you will be able to start identifying risks and report common vulnerabilities giving you a feeling of “I can do this”.
Automating performance testing: a challenging but rewarding journey
In 2014, Joost Donkers set out on a journey to fully integrate performance testing into the automated testing process where he worked, in Ortec. Along the way, some very difficult challenges needed to be conquered, most of which turned out to be non-technical. After a bumpy road, he now has a stable and useable automated performance testing platform, which is a crucial part of all software developments within Ortec.
It turns out that every part of your organization must be aware of how performance testing is used, how the infrastructure is maintained and above all, how valuable it is for the quality of your products. From manager to developer to system administrator; it’s key to get all people on board and up to speed!
In this talk, Joost Donkers will give you an insight into the process of embedding automated performance testing into the development process. By sharing his experiences, he’ll show you how to kick start the automation of your performance testing.
Experts agree that the main challenges for DevOps appear around the adaptation of the human team to a new way of working based on constant communication and transparency. However, it is common to find companies that shift their attention to discussions on the technology to be implemented for DevOps, losing the focus of what is important. The DevOps platform must be complete, reasonably cheap and easy to implement and operate.
In this talk, Fernando Pérez will present a new DevOps Suite from Micro Focus that will help your teams be productive more rapidly by using this first class platform, completely in the cloud and natively integrated from the very beginning.
From the talk, you will get an insight of DevOps Micro Focus suite in the cloud that will help you in project management, manual tests, defects, deployment pipelines management, test automation, performance testing and application monitoring.
Do you spend too much time preparing data to test your applications? Do you have the impression that your data isn’t sufficient for your test cases? Would you like to automate test cases and not suffer from data not being available? Is proper checking of test results at database level just too cumbersome? Is it a challenge sharing data in your testing environments?
You may not be aware of it but, if you regularly execute regression tests, you may have already come a long way in achieving effective management of test data but if you answered YES to all or some of the above questions, join Enrique Almohalla in his talk where he’ll show you how to cut your data provisioning time and data result checking time to CERO with Icaria Lean Tester, the TDM platform developed by netZima.
From this talk, and as a bonus feature, Enrique will also show you some powerful data masking capabilities that will help you comply with the new Data Protection Law GDPR requirements.
★ Keynote: Evolving Role of Software Testers in the Era of DevOps, IoT, AI and UX
The world is changing rapidly, technology advances in the blink of an eye, systems are getting more and more complex, and businesses need to ‘innovate' to remain competitive in this challenging world. This brings out the ’Software Tester 2.0' model, which defines the evolving role of a software tester in the era of Complexity, Digitalization (IoT, AI, AR/VR), Agility and User Centricity.
In this challenging era, customer needs are also changing rapidly. Therefore, companies should change the way they think, the way they initiate and manage the change in their organizations. They need to adapt to change, focus on strategy, value and innovation. For this reason, the role of Software Tester stands at the heart of the future success for companies. For the last few decades, software testing is one of the fastest growing market instruments in the IT world, so as test automation. As more and more complex applications go into production; traditional software testing approaches failed to fulfill the needs, consequently organizations are looking for smart and easy solutions to address their testing requirements, especially in the new era of Internet of Things (IoT), Artificial Intelligence (AI) and User Experience (UX).
In this keynote talk, Baris Sarialioglu set’s out to assist software testers to carry out paradigm shifts in their mind-set about Software Testing and Software Tester's role. He’ll help you set practical standards for the future of the software testing profession, with a special focus on User Centricity, User Experience (UX) and Usability Testing.
Delivering good quality with trainees in your team
Working with trainees with no prior testing experience is always an exciting up-and-down rollercoaster of high expectations, set goals, hard work, emotional reviews & retrospectives and floating quality results. But is it possible to achieve everlasting and good quality of your software products while on boarding new trainees, in just a few weeks and enabling them to be productive, successful and happy?
Told from the experiences of a QA lead, working for a company who supports vocational training of the future IT professionals, Maja Schreiner will tell a story of delivering good quality while coaching new trainees in testing every 6 months.
In this talk, Maja Schreiner will present techniques and checks she introduced to solve the problem of doing good testing work while training people on the job. She’ll discuss the kind of activities that were going on at the same time, the activities she was using to teach people, the risks there were with the approach as well as the kind of results and problems she encountered.
You will leave this talk knowing how to build trust, carry out proper time management and accept different personalities and work attitudes. You will also see how to apply different techniques as well as being able to significantly improve your leadership skills, inspiring and injecting your young team members with a passion for testing and at the same time creating a base for future QA leads.
Yes, we can. Integrating test automation in a manual context
“Two years ago, I was offered a job with a mission: introduce test automation in a company that only knew manual testing with a culture nowhere near ready for test automation. Regardless, I started that job armed with past test automation experience and an unwavering enthusiasm for testing and test automation.”
In this talk, Andreas Faes will tell the story of how he started off, what choices he made along the way and how this initiative triggered a team-wide switch towards automation in the broadest sense.
He’ll talk about how after two years, his team started relying heavily on continuous testing, integration and deployment insofar that the traditional barriers between testing and development collapsed. He’ll explain what worked well and what didn’t work using anecdotes and real project experiences.
From this talk, you’ll see that there is more to test automation than 'the technical stuff' and that only when it is embedded into the whole process it achieves its awesomeness. Although test automation can be scary for non-technical testers, once testers get over the initial buzz, you’ll see how it can be well managed and success can be achieved by involving the entire team, which in fact should be part of the test strategy when implementing test automation.
Most of the coding within software projects rely on patterns far more specific then common language coding patterns. As a large part of the software issues stem from architectural or project design decisions, rules for quality must be considered for the complete Software Quality lifecycle and such Quality Rules must become a first-class citizen in the SPD, from its development and configuration to the detailed analysis of results.
Many actors such as the Software Rule Designer, the Rule Developer and Configurator, the Code Inspector / Publisher and finally the Rule Analyst all play an important part in the process and several tools help put in place and integrate the actions of these actors. Many current processes fail to place emphasis on the extremes of this chain: Rule Development and Rule Analysis phases, but are in fact a success factor for achieving high Code Quality.
So, what are the specific issues that needs to be covered? Why does a bug appear? How can we relate a bug to the project’s history and team? Can we predict where it will appear again?
In this talk, Carlos Machado will present a reference model for QA tools and activities that deals with all the above concerns. Join Carlos in this talk to learn how to effectively improve the quality of your code.
From user stories to automated acceptance tests with BDD
Is User Collaboration your favourite mythological animal in Software Development and Testing? Have you heard about BDD but think it is just a new buzzword being added to the list of fashionable terms? Do you think that by using Cucumber you already practice BDD? Is documenting a tedious and worthless task? Do you think your code does not have to reflect your business objectives and goals?
If you have answered yes to any of these questions, this talk is for you!
In the talk, Eduardo Riol will show you how BDD contributes to developing more valuable software, while reducing costs, and how your team can get the most out of applying BDD by using the best tools currently available. Eduardo will also include a practical demonstration on applying BBD using such tools.
“We'll test software live on stage and while doing that, will explain what we are doing and why!”
Much has been said and written about exploratory testing. Unfortunately, it appears that exploratory testing is still often misunderstood. Some claim that exploratory testing is unstructured and ad-hoc. Just playing or cruising through the software clicking stuff without a plan. We think this because it might simply look that way. Excellent testing done by a real professional looks easy from the outside. But what is really going on?
There is a lot going on when we test and by narrating and framing what is going on, we create understanding. By knowing what skills and tactics we use, it helps us focus on the right things and it enables learning them.
In this practical talk, Huib Schoots will test software live on stage and while doing that, will explain what he is doing and why. He will give insight in the techniques, skills and tactics that are being used. In the talk, you will be engaged in the demo by observing and trying to figure out what is really going on.
No tester wants to hear a developer say, “it works on my machine!” because what it being said is: “since it worked on my development environment I assume it also works on your test environment hence you cannot possibly have found a bug”.
We know this not to be true, yet we make the same assumption between environments in a later stage: We test our software on test environments and assume that our test results carry over to production. We are not testing the software in the setting where our users are facing it. To top it off, we spend a considerable amount of money trying to copy production. Managing test environments is often hard, complex and needs a lot of maintenance effort.
A lot of people are already using techniques, which take testing into production like Beta Testing, A/B Testing or Monitoring as Testing. We intend to push the envelope a little further and additionally move acceptance testing, automated checks or exploration to the production stage. To do so we need to take several things into consideration, such as making sure test data does not mess up production data and analytics, as well as hiding untested features from customers.
In this talk, Marcel Gehlen and Benjamin Hofmann will show you some popular techniques for testing in production. They will also present various strategies, which help tackle common constraints faced when testing in production and they’ll also provide you with an approach to gradually shift your testing to production.
ATDD: towards continuous delivery of value. A real case.
TDD, BDD, ATDD are well-known concepts frequently discussed by all those dedicated to software development. When putting such techniques in place, even for large scale projects, we face many difficulties as commitment from all involved parties within the project is key to achieving success.
In this talk, Javier Bel, Jorge España and Miguel Ángel Alonso, as members of the Quality Enablers team in the Rubik project for ING Group, will explain how to enable a software quality strategy based on ATDD and TDD methodologies for a global and large-scale agile project.
During the talk, they will discuss the challenges and solutions they found for succeeding when applying the strategy, where concepts like definition, development and quality were all merged into a single concept that was transversally applied to the whole organization, that it, delivering continuous value to their customers.
Automation Architecture testing. The cornerstone to reusability and maintenance (or the art of “divide and rule”)
In the current context, test automation has become a necessary activity that may not be isolated from the rest of the software life cycle process. Its implementation and further development goes beyond the classic approach based on automation tools and scripting, and for this reason, it’s necessary to take the leap from automation framework to automation architecture.
In this talk, David Tejero y José Urbano will show you a general automation architecture, based on the ISTQB model, that focuses on reusability that permits adaptation to any type of technology and tool. They’ll explain how the definition of the automation architecture and its implementation, as a project solution, improves the classic vision of test automation (thanks to the integration of tools, strategies and frameworks) and how it can be achieved by separating the different responsibilities of automation activities into levels or layers, that allows for the adaptation of different technologies, operation by different users, integration with other tools and processes, while sustaining growth of your automation.
Initiating from the automation architecture model proposed by ISTQB, this talk is dedicated to those who are considering implementing automation into test processes or even those who are using it and want to take the leap to having a reusable automation environment for different projects.
THE GREAT DEBATE : Industry vs Experts vs Public
Sponsored by Micro Focus
Track 1 | 17:25 - 18:25
What is it?
The great debate is an opportunity to voice your opinion, as a conference speaker, sponsor or attendee on 4 lightening talks (2 minutes each) based on a number of software testing topics, namely, test automation & tools, training & certification, Artificial Intelligence, software security.
Where & when?
The debate will start at 5:25pm on the 5th of June and will run for 60 minutes.
How it works?
There will be 4 rounds in the debate, each lasting 15 minutes and based on one of the lightening talks. There will be a group of participants debating each round: sponsors, speakers and attendees and the audience will also get a chance to vote for particular answers to each round, by using Kahoot.
If you want to participate as part of the audience, please, let us know at the reception, providing us with your name and the company where you work. Remember to sit in the first row of the debate room (track 1) before the start of the debate.
- Tools and automation, where will it lead to? - A certification doesn’t train you! - Artificial Intelligence, only the best testers will survive! - Security is a word every tester must be able ‘to spell’!