Cloud computing has a large momentum and new cutting-edge technologies are available compared to traditional on-premises architecture. Benefits are numerous and include lower upfront costs, impressive scalability, faster setup and many more. That’s why a large number of projects are being migrated to the cloud. At the same time, a vast majority of new projects use cloud services. Even though cloud technology provides a lot of benefits, the challenge of testing these systems still exists, especially in testing business logic. Azure is a cloud computing service created by Microsoft — one of the biggest cloud providers at the moment. Milovan will share his experience in working on an Azure-based solution and in this presentation he will:
– Provide ways of monitoring what is going on in the Azure cloud
– Explain the differences between traditional and cloud testing
– Provide ways to automate cloud testing

Good software practices don’t end just because you’re building a thick client in the browser. The JavaScript community is a flourishing boutique of high-quality tools and techniques. We’ll dig into some of the more popular open-source JavaScript patterns that have emerged from the Node community. We’ll see mocha, chai, karma, and headless Chrome in action, look at some great techniques and patterns for browser development, and brush up on things that make JavaScript is a phenomenal place to work.

Creating and maintaining a mobile device lab is a high priority while developing and testing modern mobile apps. Should you build your own or use the cloud solutions, or maybe you should create a hybrid solution to use both in house and cloud solution? Sargis will share our experience of building a mobile lab.

It is becoming more and more challenging to test mobile apps on different devices, with different screen sizes, running different operating systems. During the development of a mobile app, we can easily verify and test the app on a mobile simulator or emulator. However, only simulator or emulator testing isn’t enough, we need to make sure that our app works on devices that our users carry with them in their pocket.
Creating a in house Automation Mobile Lab will be a good decision if you’re looking to do automated testing, for example with Selenium and Appium.

In this topic Nikolay is going to share how to build an automation framework which can be used by everyone. Main technologies behind it are java / cucumber / testNG. Testcon participants will see main principles building an automation framework in a way any QA will be able to learn / use and contribute. On top of that any non technical person will be able to consume and write UI tests. 

Rick wants to explore the world and value of testing that lies more in the creative, exploring, interpersonal and empathetic side, and see if we can shine a light on all the other parts of testing that make it a unique, powerful and downright fun thing to do.

The processes employed in software development are a reflection of the culture of the organization. The things team members do and the way they do them reflect their belief systems. As the processes are shaken out, the culture adjusts itself appropriately, so the processes and process change are a natural part of team activities in most organizations. Attempts to improve processes without corresponding culture changes generally fail because team members will revert to the old ways when exceptions come up and the new processes fail. This is especially true when the processes are forced on the team.”The processes employed in software development are a reflection of the culture of the organization. The things team members do and the way they do them reflect their belief systems. As the processes are shaken out, the culture adjusts itself appropriately, so the processes and process change are a natural part of team activities in most organizations. Attempts to improve processes without corresponding culture changes generally fail because team members will revert to the old ways when exceptions come up and the new processes fail. 

We spend a lot of energy and time on automation, yet often we struggle to reap the benefits. Automation is one of the pillars of DevOps. Automation is also difficult and often approached in a bad way. This talk will cover why and some strategies for successful automation.

In this talk, Nicolas will explain how Code Coverage is computed and what its inherent flaw is. Afterwards, he will describe how Mutation Testing work and how it helps pointing out code that is tested but leave out corner cases. He will also demo PIT, a Java production-grade framework that enables Mutation Testing.

If you are an agile shop and a software based service or a product company, then millennials would be beneficial and apt for the QA team, because you not only get people who love automation but also a team packed with innovative ideas and energy. Owing to the inquisitive nature of this generation and the next, their thirst for innovative testing will yield efficient results.

Not so long ago those of use working in .Net were stuck. We were stuck on Windows OSs. We were stuck paying high licensing costs for Visual Studio. We were stuck with closed source support libraries. We were just stuck.

Join Paul Grizzaffi as he walks through how layers can be a valuable part of an automation implementation, some caveats that should be considered when layering an architecture, and several examples of layered architectures of which he’s been a part. Come and learn ways to stack the deck in YOUR favor.

Marcel will share with you how test automation market is changing, what are the current hot trends, and what new opportunities these will bring to us. Some of the most interesting innovations relate to improving scope selection, execution and maintenance of the automated test pack, powered by AI and ML.

Take aways:
– Participants are much more comfortable with Testing and Test Automation for CI/CD Pipelines
– Participants understand the importance of the Testing the CI/CD Pipelines
– Get familiar with Github Actions and Workflows
– Participants understand how to build testable CI/CD Pipelines

BDD (which states for Behaviour Driven Development) is one of the best knows abbreviations for IT people. We assume, that at least 80% of familiar with its concept. The very simple concept to be honest. However, with simplicity comes responsibility…

For decades we have been evolving strategies to test monolithic systems. The importance of concepts like the test pyramid was iterated over and over again. However, with the growing adoption of microservices, there’s a need to revisit these practices to adapt them to the complexity brought by distributed systems.

This talk shows that testing concepts are more important than ever, in a time where tools promise to do everything, we focus less on what and how to test, and more on using tools to test. It outlines how a test strategy can leverage a continuous testing setup. Finally, it shows that failing is ok, but failing again for the same reasons is not.

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