Gergely Ágnecz
Hungarian Telekom (HU)

Biography

As a Test Automation Specialist, Gergely works at the Hungarian Telekom and supports the development teams to create the next generation of the company’s web services. Has a Master's degree (University of Hertfordshire, UK) in Software Engineering, and has been working in Quality Assurance and Development for about 9 years. During his career at several multinational companies, like EPAM, Nokia and BlackRock, he got experience in various domains (finance, healthcare, telecommunication, etc.). On most projects he was responsible for test automation: High-level tasks like build up or improving test automation, Low-level tasks, creating and automating test cases, scenarios. Mostly done in Java and the common SDLCs (Waterfall, V-model and Agile). As he believes that knowledge is power, he strives to learn new things and share his knowledge, experience on meetups and conferences, on company trainings with others. For him, teaching the engineers of the future is very important. Has been a regular guest speaker for years at several famous Hungarian universities like Óbuda University, Pázmány Péter Catholic University and Eötvös Lóránd University, holding lectures about mobile test automation and software testing.

About the presentation

Presentation: The good, the bad and the Agile – Stories of the past

 

In Agile Software Development, all participants must be agile and reactive to handle the different requests and to provide the best quality that we can.

– How could we develop something in the right way if we do not even know what is the expectation of the stakeholders?
– We all know that exhaustive testing is not possible, but how can we be agile as a QA?
– How does Agile work with the test plans, test strategy and other documents that should be common?

By this talk, Gergely wants to help people to understand how user stories are connected to not just to developers, but to the testers as well. Through an example user story, we will approach the problem with improper/unclear stories and see different ways to add meaning to these. When we have the clear picture, we check how it affects the test planning, efforts, and methods, how RBT is helpful and applicable in such cases.

The goal is the broaden the view: clear user stories affect our testing efforts and by gathering all the necessary inputs, we can set up a clear traceability that can speed up our work and increase the overall quality as well.