Conference program is forming and call for papers was opened. We will publish all submitted talks here after initial review stage. Final version of the conference program will be published on November 1. If you have any questions related to the program and talk submission please send them to email@example.com.
Why testing take so much time?
Continuous Development Pipeline
During this talk I’m going to walk you step-by-step through practical implementation of continuous development pipeline using modern approaches and tools like Gradle (build automation), Jenkins (CI server), SonarQube (code quality analysis), Docker (deployment, containerisation), Ansible (immutable infrastructure) together.
Practical Considerations for Microservice Architectures
But what are the practical concerns associated with running more fine-grained systems, and what are the new things you’ll need to know if you want to embrace the power of smaller services without the new sources of complexity making your life a nightmare?
This talk will delve deeper into the characteristics of well-behaved services, and will define some clear principles your services should follow. It will also discuss in more depth some of the challenges associated with managing and monitoring more complex distributed systems. We’ll discuss how you can design services to be more fault-tolerant, what technologies may exist in your own platform to get you started. We’ll end by giving some pointers as to when you should consider microservice architectures, and how you should go about introducing them in your own organisation.
The responsible developer
What is a responsible developer then?
It is a developer that writes clean, testable and maintainable code. A developer who can explain and describe his work. Someone that knows that he grows by helping his fellow developers and never settles for second best.
I will discuss the properties of a responsible developer and suggest ways you can improve to become a responsible developer.
Beyond breaking bad. The current state of agile in ten easy lessons
Building a micro-services architecture with smart use cases
The Primacy of Testability
In this presentation I will focus on a single quality attribute, testability, and in particular I will explore how maintaining testability will tend to improve many other attributes. Among other things, highly testable code is modular and loosely coupled by nature, is maintainable, supports scaling out development, and can improve feedback loops. By ensuring testability in a system you not only support these and other related qualities, but you also provide an important means to verify that they are being met.
Ultimately, I will look at how testability (and testedness) can be useful and reliable proxy or approximation for a wide range of qualities.
Open Decision in Architectural Evolution
Unit Testing – bug hunting tool or design tool?
Legacy projects: how to win the race
I have a decent experience with such projects and often after some work can be proud because the application receives a new life and a customer/product owner saves some budget. However, only few have the same passion for “deadly sick” projects so I would like to share the knowledge, how-to’s and recipes of handling those fragile but stubborn folks – legacy projects.
New life inside monolithic application
Writing clean and DRY code for executable specifications
A gap between high level system validation requirements and capabilities of component API opens testers for use of different methods and even different programming languages when implementing test infrastructure code. This code is not deployed to production, so testers often get more liberty in choice of frameworks and tools used to validate system behavior. In this talk we will show that such freedom can be turned into an advantage to keep the test code clean and non-redundant. The main focus will be on implementing scenario steps for specifications written in Gherkin – a widely adopted language for specifications and user requirements. We will walk through a series of examples and short case studies.
The talk is technology agnostic but most of examples are taken from systems running on .NET platform.
Quality Built In
Quality of the product team
I will share with you the quality management system, born in our team for a project being the company business core. Step by step we will follow the value system, processes, development practices, solutions for various complicated situations and learning on our own errors process – including all difficulties and backflashes on the way to the set aim.
So, what about you? Do you know the signs of the mature team and product, the same as the moves which will keep you afloat? Let’s verify!
Continious Delivery for a complicated product
I do hope the experience of my team will be very useful to the way of your team’s successful continuous delivery.
How we testing our software “Google way”
Automation testing of responsive design
So the question is how to automate verification of UI features? In general automation testing tools are not smart enough to do this in entire sense of the context. Fortunately Galen Framework gives us a new hope, because it aimed to work with dimensions of web elements depends on browser window size. Hence we can add a new level of automation to our good old functional tests.
A Database story by DevOps
I am going to talk about catching and solving problems in Production Databases – how to increase performance and decrease costs in long time perspective. The talk is based on experience we’ve received in Production.
Toolbelt for pragmatic .NET development: from coding to release
However there are tons of other tools, developed by enthusiasts and used by thousands of developers accross the globe. And may of them are really cool.
In this session Serhiy will share his team’s experience in using tools for development of modern web based solution. We will cover the whole code lifecycle – starting from setting up developers environment, unit and acceptance testing, continious integratoin, and ending with deployment pipeline. List of tools will include not only .NET but frontend part of the system as well.
Integration Testing from the Trenches
However, Integration Testing might seem very complex when put in place for the first several times; I have made many mistakes and have lost much time. In this presentation, I will present tools that helped me tremendously in Integration Testing, as well as proven tactics to get the best out of your tests.
How not to run a Code Review
Teams which don’t follow the basic rules of efficient communication and problem solving during Сode Reviews, have a high risk of being affected by issues, which can lately ruin their team attitude and even personal relations between the colleagues.
Having faced with such negative experiences, I’ve collected a plenty of bad practices running a Code Review and asked my colleagues about their emotions after being “code reviewed” in unproper way.
With all of that we’ll try to understand the most dangerous pitfalls of weak Code Reviews, their influences on team morale and will also leave some place for your experiences with this approach from your side. As a result you’ll have a clear idea about how no to run a Code Review and avoid personal issues in your daily work.