Full Scale Automation Using Selenium

Test Design + Environment Management: Scaling UI Automation for Agile

Test Design: Scaling UI Automation from the Ground Up

Learn Key Insights from The State of Web Application Testing Research Report

Sencha

In a recent study by Dimensional Research of 1,011 development and QA professionals, almost every survey respondent cited that application quality is important, with 84% believing it is very or critically important. Despite this, findings revealed that 94% of teams still face challenges when it comes to conducting adequate QA. View the presentation to learn why organizations must prioritize automated testing and QA practices to deliver high-quality applications and increase customer satisfaction.

Automated Testing with Logic Apps and Specflow

BizTalk360

At Integration Monday, we have had feedback from the audience that people are struggling with understanding how to do automated testing with Logic Apps. Back in the day Mike Stephenson wrote a lot of guidance about automated testing & unit testing for BizTalk. So he took up the challenge of trying to help out on this one. In this session, we will discus some of the challenges around testing Logic Apps and then we will work through some examples of how testing can be performed and finally we will look at an approach which should put us in a solid place to be able to test Logic Apps both as an individual developer and via an automated build.

How to Make Your UI Tests Stable, Scalable, and Maintainable

Manual, Visual, and Automated Testing For Web Apps

Dev ops concept

Professional Guru

XP Injection

How to be proud when you are done

Although all of us speak the same language, each of us uses different meaning of words "soon”, "fine” and "done”. That’s why for one developer "I’m done” means that just a moment ago the part of the code with implemented functionality has been successfully executed, while for another developer it means that code has been committed to repository but without checking if build is green or not on continuous integration server. At the same time "done" of developer-perfectionist means totally refactored and optimized code. And only for "black swan”-developer phrase "I'm done“ means that all tests were passed, new functionality was documented on wiki and a new feature was verified by customer on the demo server. So if you want to decrease a risk of misunderstanding inside a team or between team and customer you should make agreement about common vision of “definition of done“ and then start using it on a daily basis. In order to prevent losing your time and stepping on the hidden rake during discussion of your done criteria we will share our knowledge about creating compact and most effective “definition of done“. We will talk about lifecycle of this document and about approaches that help you to add important items to it. We will discuss doneness on different levels (preplanning, user story and task development, sprint). And of course we won’t forget to tell you how to create “Definition of Done“ which will satisfy not only your team but your customer as well.

Code review

Многие жалуются на качество кода, автоматизированных тестов или продукта в целом, на количество ошибок, найденных конечными пользователями или отделом тестирования. Почему это происходит? Необходимо понимать, что для того чтобы не допустить подобных ситуаций требуются дополнительные усилия – необходимо следить за качеством кода и работать над его улучшением. Code Review является одной из наиболее полезных и эффективных практик для ранней борьбы с дефектами в коде и повышению его качества. Использование Code Review на различных этапах разработки, начиная от дизайна и заканчивая написанием кода и тестов, помогает построить ранний цикл обратной связи и избежать потерь времени в будущем на исправление ошибок. Дополнительным преимуществом применения Code Review является распространение знаний между членами команды и адаптация других командных подходов. Данная практика может быть интересна любому члену команды вне зависимости от его роли в проекте. В докладе будут рассмотрены основные аспекты Code Review, способы проведения, инструменты и техники. Также будут продемонстрированы основные ошибки в использовании этой практики, полезные советы, приемы по внедрению и поддержке.

Machine learning in software testing

Thoughtworks

Wrong Tool, Wrong Time: Re-Thinking Test Automation -- w/ State of Visual Tes...

Applitools

Full webinar recording: Go through this presentation and on-demand session to learn: What Are The World’s Most Innovative Testing Teams Doing That You Are Not? As much as we all hate to admit it, our test automation efforts are struggling. Coverage is dropping. Bugs are escaping to production. Our apps are visually complex, growing rapidly, delivered continuously, and changing constantly - so much so that our functional framework is now bloated, broken, and unable to keep up with Agile and CI-CD release best practices. No wonder that in our latest State of Visual Testing research, the majority of companies surveyed reported that their CI-CD and automation processes are not helping them to successfully compete in today's fast-paced ecosystem, and are not effective in ensuring software quality in a scalable and robust way. But what about those elite testing teams that got it right? What's their secret? Can we copy what they did, instead of setting ourselves to fail? With this presentation, and on-demand session discussing it, learn how the 10% of the world’s most innovative testing teams have reinvented their test automation to support a fully automated CI-CD process, and guaranteed their company's digital transformation was a success. Use these resources to learn: -- Why the majority of test automation efforts are falling behind -- How your QA and testing efforts compare to these elite teams -- via live polling results -- 4 modern techniques that the top 10% of testing teams globally are doing every day, and that you can do too

Preso #5

Andrew Gitlin

Browser Vendors are Reshaping Testing - Are You Ready?

How to Become an Effective Tester by Reusing Tests

Reusable skills and reusability of testing scripts becomes even more important as there is more to test in less time. Especially when Apple, Google, and Microsoft continue to make it easier for developers to deploy the same code across desktop, phone, tablet, or watch. Add to that, the challenge arising from device fragmentation, increased API dependency, or even dealing with variety of inputs like point and click, gestures, or voice. Get the testing skills employers are looking for. Come learn with us how you can deliver quality applications at speed by reusing existing tests and skills in a variety of ways. Highlights include: Testing trends and how to increase your value to get a salary raise How reusable test scripts can help not just testers, but also developers and operations The overlap between functional, performance, and other tests Benefits of reusing test scripts How to build a robust reusable testing framework

Бытовая классификация тестировщиков с точки зрения разработчика

Тестировщики часто говорят о противостоянии и конфликтах с разработчиками. Но ведь есть команды, где все живут в мире и согласии. Видимо что-то тут не так? Я хочу поговорить о том, как тестировщиков видят сами разработчики. В докладе будет проведена забавная классификация. Кроме известного всем тестировщика-обезьянки будут представлены тестировщик-муха, тестировщик-нацист, тестировщик-панда и многие другие герои. Высможете лишний раз задуматься над тем, как вас видят со стороны и, возможно, изменить ситуацию к лучшему. Доклад будет также полезен менеджерам проектов и лидерам команд. Вы сможете быстрее распознавать те или иные шаблоны поведения тестировщикови принимать меры по повышению уровня командной работы. Приходите, будет интересно!

Selenium webdriver interview questions and answers

ITeLearn

What's hot

Continuous Integration

drluckyspin

Selenium and Continuous Intergrationautomated-testing.info

QA Strategies for Testing Legacy Web Apps

Rainforest QA

How to Introduce Continuous Delivery

Dr. Alexander Schwartz

Getting Started With Selenium

Test Design + Environment Management: Scaling UI Automation for Agile

Test Design: Scaling UI Automation from the Ground Up

Learn Key Insights from The State of Web Application Testing Research Report

Sencha

Automated Testing with Logic Apps and Specflow

BizTalk360

How to Make Your UI Tests Stable, Scalable, and Maintainable

Manual, Visual, and Automated Testing For Web Apps

Dev ops concept

Professional Guru

XP Injection

How to be proud when you are done

Code review

Machine learning in software testing

Thoughtworks

Wrong Tool, Wrong Time: Re-Thinking Test Automation -- w/ State of Visual Tes...

Applitools

Preso #5

Andrew Gitlin

Browser Vendors are Reshaping Testing - Are You Ready?

How to Become an Effective Tester by Reusing Tests

What's hot (20)

Continuous Integration

Selenium and Continuous Intergration

QA Strategies for Testing Legacy Web Apps

How to Introduce Continuous Delivery

Getting Started With Selenium

Test Design + Environment Management: Scaling UI Automation for Agile

Test Design: Scaling UI Automation from the Ground Up

Learn Key Insights from The State of Web Application Testing Research Report

Automated Testing with Logic Apps and Specflow

How to Make Your UI Tests Stable, Scalable, and Maintainable

Manual, Visual, and Automated Testing For Web Apps

Dev ops concept

XP Injection

How to be proud when you are done

Code review

Machine learning in software testing

Wrong Tool, Wrong Time: Re-Thinking Test Automation -- w/ State of Visual Tes...

Preso #5

Browser Vendors are Reshaping Testing - Are You Ready?

How to Become an Effective Tester by Reusing Tests

Viewers also liked

Бытовая классификация тестировщиков с точки зрения разработчика

Selenium webdriver interview questions and answers

ITeLearn

Java Basics for selenium

apoorvams

Автоматизация тестирования. Разбор конкретного примера - продукта XML2Selenium

jazzteam

Сотрудница компании JazzTeam провела ряд лекций в Гродненском государственном университете имени Янки Купалы. После конференции Solit-2013 в рамках ознакомительного тура по Беларуси для одного из англозычных докладчиков, руководство компании посетило Гродненский государственный университет имени Янки Купалы, где состоялось знакомство с руководством кафедры программного обеспечения интеллектуальных и компьютерных систем. В рамках продолжения отношений между компанией и кафедрой представитель компании JazzTeam провела несколько лекции по тематике разработки программного обеспечения. Лекции проходили в рамках заседания студенческого семинара “Информатика – Сегодня”, которые университет и кафедра проводят регулярно. Вторая лекция была проведена 28 марта 2013 года на тему “Автоматизация тестирования. Разбор конкретного примера – продукта XML2Selenium”. Лекция была больше направлена на практические аспекты, общение со слушателями и донесение до них необходимости писать тесты, автоматизировать процесс тестирования проекта, на примере фреймворка xml2selenium – разобрали ключевые проблемы автоматизации тестирования, рассмотрели стадии разработки ПО, Continious Integration, планы фреймворка xml2selenium на будущее. На лекциях присутствовало много людей, начиная от первокурсников до преподавателей. Лекции охватывали большой спектр вопросов, и все моменты были разобраны на примерах. Публика вела себя очень оживленно и интересовалась больше примерами из жизни, практическими навыками. Впечатления о проведенных лекциях остались самые положительные. Спасибо за интересные вопросы и обсуждения!

The modern view on implementation of classic design patterns in Java

Almost every developer heard about design patterns. They was introduced long time ago to solve particular set of repeating problems in systems of different complexity level and size. But there is an opinion that many design patters just filled holes in the OOP languages of that time. Java as one of them has transformed and improved significantly in the last 10 years. So may be we could review design patterns implementation in modern Java world? Some of them are now may be easily replaced with language idioms, some others may be covered with existing libraries and frameworks. I'm sure you know some design patterns that are dead now or became anti-patterns in their initial implementation. Lets make this fun and useful review together!

Foundation selenium java

seleniumbootcamp

Continuous test automation

Viresh Doshi

Automated UI Testing

XPath локаторы в Selenium WebDriver

Илья Кожухов

Realtime selenium interview questions

Kuldeep Pawar

Selenium interview questions

girichinna27

Object Oriented Programming with JavaJussi Pohjolainen

Web Test Automation with Selenium

vivek_prahlad

Automation Testing by Selenium Web DriverCuelogic Technologies Pvt. Ltd.

Selenium ConceptsSwati Bansal

Automation Testing using Selenium

Naresh Chintalcheru

Viewers also liked (16)

Бытовая классификация тестировщиков с точки зрения разработчика

Selenium webdriver interview questions and answers

Java Basics for selenium

Автоматизация тестирования. Разбор конкретного примера - продукта XML2Selenium

The modern view on implementation of classic design patterns in Java

Foundation selenium java

Continuous test automation

Automated UI Testing

XPath локаторы в Selenium WebDriver

Realtime selenium interview questions

Selenium interview questions

Object Oriented Programming with Java

Web Test Automation with Selenium

Automation Testing by Selenium Web Driver

Selenium Concepts

Automation Testing using Selenium

Similar to Full Scale Automation Using Selenium

Practical Testing Strategy for Agile Team

Jen-Chieh Ko

A Lap Around Visual Studio 2010

adrian8three

Continuous Testing - The Final Frontier

Jaco Greyling

CI and CD with Jenkins

Martin Málek

#ITsubbotnik Spring 2017: Anton Shapin, Denis Klykov "Visualization, storage ...

epamspb

Тема нашего доклада - «Visualization, storage and comparison results of performance testing by using Grafana and InfluxDB». При тестировании у многих возникают вопросы о том, как визуализировать результаты прохождения тестов, как сравнивать результаты разных тестовых прогонов, и где хранить результаты тестов. Мы ответим на эти и вопросы и расскажем о бесплатных инструментах, которые помогут в работе.

Product quality in agile project

Nhan Nguyen

Automated Testing of Web Applications

jonatankronqvist

Testing is an important part of all software projects – and so is keeping sane. In order to not make the developers and testers lose their minds while verifying that a huge amount of features still work, the testing should be automated. What’s worse, the complexity of the underlying technologies often make it more challenging to test web applications than conventional software. This talk will show you some tools and methodologies for automated testing of web apps and especially the user interface layer of web apps. It will discuss how to architect a web app for easy testing and what kind of tests should go where and in which situation. We’ll even have a look at how the customer requirements can be automatically tested and verified to work – exactly as specified by the ones paying the bills.

TCE Automation

Tikal Knowledge

5 Steps to Jump Start Your Test Automation

Sauce Labs

With the acceleration of software creation and delivery, test activities must align to the new tempo. Developers need immediate feedback to be efficient and correct defects as those are introduced. The path to achieving this vision is to build a reliable and scalable continuous test solution. All beginnings are hard. Having a well-defined plan outlining the approach for your organization to create test automation is key to ensure long term success. Join Diego Molina, Senior Software Engineer at Sauce Labs as he discusses: The importance of setting up the team correctly from the start Choosing the right Testing Framework for your organization Identifying the right scenarios and workflows to test Learning to avoid common pitfalls at the beginning of the transformation journey

Project Management in 3 Slides

Lonnie Sorrells

ЄРМЕК КАДИРБАЄВ & АЛЕКС РИБКІН «How we train QAEs to join automation» Online ...

QADay

Modern software testing and processes 2019

Karim Fanadka

The Holy Trinity of UI Testing by Diego Molina

Sauce Labs

The first step before testing is defining what we want to test. This may sound trivial, but in reality this not done often properly. We tend to oversee the obvious and we start testing without knowing what we want to accomplish. Do we want to validate the user behavior? Do we need to check that the page design is responsive on different devices? Knowing what is important and what needs to be validated can help us enormously to have a clear purpose. When we know the purpose of our test, we can start planning, coding, executing and improving our tests. But overall, we will know what approach we can use to develop the test. Functional, layout and visual testing are the three pillars of the UI testing trinity. These are three approaches we can use to develop focused tests, tests that are asserting a specific aspect of a web application. But how can we identify what approach to use? When should we combine them? This SauceCon 2018 session will help attendees to define what they want to test and what approach to use when developing the test. It will go deeper through scenarios and code examples that show how to create tests with great assertions and clear purpose, tests that give value to the team. It will also discuss scenarios where a functional test is not enough, or where a visual test is better than a layout test. This talk’s main goal is to offer a different perspective when testing a web application through the UI testing trinity.

Developer Productivity Engineering with Gradle

All Things Open

Presented by: Justin Reock & Sterling Greene Presented at the All Things Open 2021 Raleigh, NC, USA Raleigh Convention Center Abstract: In 2007, Hans Dockter invented the Gradle Build Tool because he felt that developers deserved less friction in their toolchain. The prevailing build technologies of the time were adequate but inefficient, not taking advantage of possible acceleration technologies and, with some exceptions, very limited in their language and framework support. Gradle is now one of the most widely used build tools available, downloaded about 25 million times a month as of September of 2021. It’s the default build tool in Android Studio, and is trusted by millions of developers to create their artifacts quickly and cleanly. The principles that originally guided the Gradle build tool towards its current popularity have continued into an emerging practice known as Developer Productivity Engineering or DPE. DPE is a new software development practice that uses acceleration technologies to speed up the software build and test process and data analytics to optimize the impact of acceleration technologies and make troubleshooting more efficient. Leading technology companies are using this practice today to accelerate feedback cycles by over 90% in some cases, improving the developer experience and increasing team velocity. Join Sterling Greene, Lead Software Engineer for the Gradle Build Tool, and Justin Reock, Field CTO of Gradle Enterprise, to learn why DPE is swiftly becoming the most important movement in software development since the introduction of DevOps. Attendees will walk away from this presentation with a better understanding of: ● The importance of fast feedback cycles and how to achieve them using build and test acceleration technologies ● Using build and test data to make troubleshooting and problem root cause determination more efficient. ● The importance of leveraging failure analytics to improve toolchain reliability, including managing avoidable failures like flaky tests. ● How to continuously improve performance and guard against regressions through trend and metric observability. ● The Cost of Inaction (CoI) by not investing in developer productivity across your local build environments and CI/CD pipelines in terms of engineering cost, TTM and software quality. ● How to elevate the strategic priority of DPE in your organization.

Cars.com – revolutionizing continuous integration with selenium rd

Richard Darcy

DevOps Indonesia Meetup at PT. HM Sampoerna, Tbk - DevOps + QA Automation wit...

DevOps Indonesia

End-end tests as first class citizens - SeleniumConf 2020

Abhijeet Vaikar

[India Merge World Tour] Coverity

Perforce

Best Practices in Object Oriented Analysis and Design

nguyencraft01

Agile2015 short paper presentation: Development of Complex Software with Agil...

Alan Braz

Agile Software Development (ASD) has been on mainstream through methodologies such as XP and Scrum enabling them to be applied in the development of complex and reliable software systems. This paper is the end result of the Master’s dissertation of the main author, and proposes a solution to guide the development of complex systems based on components by adding exceptional behavior modeling practices to Scrum, resulting in the Scrum+CE method (Scrum with Exceptional Behavior). In order to evaluate the proposed method, a synthetic controlled experiment was conducted with three groups.We compared the efficiency of the new process in relation to plain Scrum and the results were the production of a better quality software but with less features implemented during the same amount of time.

Similar to Full Scale Automation Using Selenium (20)

Practical Testing Strategy for Agile Team

A Lap Around Visual Studio 2010

Continuous Testing - The Final Frontier

CI and CD with Jenkins

#ITsubbotnik Spring 2017: Anton Shapin, Denis Klykov "Visualization, storage ...

Product quality in agile project

Automated Testing of Web Applications

TCE Automation

5 Steps to Jump Start Your Test Automation

Project Management in 3 Slides

ЄРМЕК КАДИРБАЄВ & АЛЕКС РИБКІН «How we train QAEs to join automation» Online ...

Modern software testing and processes 2019

The Holy Trinity of UI Testing by Diego Molina

Developer Productivity Engineering with Gradle

Cars.com – revolutionizing continuous integration with selenium rd

DevOps Indonesia Meetup at PT. HM Sampoerna, Tbk - DevOps + QA Automation wit...

End-end tests as first class citizens - SeleniumConf 2020

[India Merge World Tour] Coverity

Best Practices in Object Oriented Analysis and Design

Agile2015 short paper presentation: Development of Complex Software with Agil...

More from Andrii Dzynia

Continuous Delivery as you want it

Continuous delivery makes an agenda for many engineering teams. When there are not that many unknowns in the web world, the embedded software domain is worth exploring. With such diversity of different partner integrations(speakers, consoles, tv’s, cars, etc) Spotify is not an exception. We set ourselves on a journey to reach a state when releases of Spotify’s eSDK is rather a routine and doesn't require anything more than a push of a button. The end goal is clear and sounds easy but challenges are all over the place and every single one needs to be addressed individually. This talk is about how we managed to setup releases of Spotify’s embedded SDK on a predictable schedule and keep improving towards being able releasing on-demand going forward. Our challenges and solutions. What worked, what did not. Pain, tears, joy, and smiles.

Test coaching your agile team

Testing is probably the most misunderstood concept in software engineering. Many still believe that testing is simply a verification of actual and expected results in pre-defined set of test scenarios. I wish to know earlier how wrong this statement is. Conversations about testing can be seen wide, ambiguous, and hard to facilitate. But when done properly show prominent results. You start from quality. Addressing questions like. What does quality mean for us? Who owns it? Who is responsible for quality improvements? There is no single answer to every team. Each has to come up with their own definition, which works in their particular situation. Testing is not a measure for quality, but rather a set of activities and preparations to increase a level of confidence before releasing. You cannot simply state that after verifying 1000 test scenarios the whole product behaves as expected. During this presentation I will share key findings which I think are the most important ones to get almost any engineering team on the right track towards improving productivity and released product quality. There is no single rule to rule them all, but experience-based patterns.

Testing at Spotify

What does it mean to be a test engineer?

Test engineering is hard, even harder than software development. Being test engineer puts you in a wider context, with no clear boundaries. You have to find those by yourself. This requires courage. Courage to take action, courage to make mistakes. As a test engineer, you do mistakes every day. You do them so often that sometimes you feel you can predict the future. Scientific explanation to this phenomena is patterns recognition. It is an ability of our brain to match the information from a stimulus with information retrieved from memory. Defect prevention is hard. Together with technical skills one have to develop high social awareness. Working on safety nets never was so important, different types of checks on different levels to make sure software is reliable and serves its purpose to the variety of everyday use-cases. We know that life is so complex and sometimes complicated which makes it impossible to predict all possible outcomes and scenarios. But striving for excellence never was so important as nowadays in such an open, transparent and competitive environment. Goal of my talk will be to show you my everyday job as a test engineer. Not only how to look for defects, but how to prevent them from happening. Not only how to automate tests(noun), but how to build safety nets to minimize end-user impact. Not only how to inform testing status but how to influence quality on company level.

Exploring your unit tests

As a developer, most of the time, you are being focused on solving concrete problems. This process get’s all your attention on implementation details to make it just work. If time persists you might spend some time on writing tests for your code, but not going far into details on all the edge cases. It is very hard to verify your own creation in all possible ways. Stepping out of comfort zone and think like a consumer is what test engineers are good at, thinking from the end. During this session I’m going to share my daily tricks on how to help developers writing better tests which leads to less bugs and more testable architecture.

Hermetic environment for your functional tests

What are the most common problems with testing environments? - You are not the only one who is using it. - Test failures are not repeatable. - Test data can be easily messed up due to tests overlap. Those problems are introducing flakiness in your tests, increase frustration level and decrease confidence in quality of a product you are building. Forcing your development team to have a testing queue increases delivery time dramatically. Creating zillions of environments does not sound as cheapest solution either. At Spotify we experimented with different approaches on how testing environments can be configured: from shared environment to mocks, stubs and hermetic servers. During my presentation I will share the lessons we learned, what worked, what not and what is the direction we are pursuing in order to stabilise our testing suites.

Quality Built In @ Spotify

Most of the people think that quality in software development is limited to manual testing on the latest stage before releasing a product. That might be true 20 years ago in the industrial era. But current world is much more dynamic than before. Time to market became the most crucial metric nowadays. Releasing code to production need to be done faster and faster. How to maintain quality on a sufficient level in this fast paced environment? How to find a time to work on quality improvements? Those are two main questions I want to answer during this talk. Do not expect a silver bullet or even receipt to success. But definitely expect a lot of information about continuous delivery/deployment/improvements with a case studies and lessons we learned at Spotify. Spotify Engineering Culture: https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/ https://labs.spotify.com/2014/09/20/spotify-engineering-culture-part-2/ Scaling Agile @ Spotify http://blog.crisp.se/2012/11/14/henrikkniberg/scaling-agile-at-spotify Scaled Agile @ Spotify http://vimeo.com/111131934

Applying testing mindset to software development

Software Development is a creative activity that requires focus. During coding session you as a programmer tends to make so many decision that sometimes force you to neglect 'unimportant details' that might sounds like specific use cases, unclear statements or somethings that won't gonna happen. In most cases the system even so complex that is not that easy to step out and see the whole picture, even from user's point of view. Historically software developers used to trust other people called testers to verify those 'details' from user's perspective before deploying into production. In order to have proper alignment inside the team dedicated 'QA step' added to the process. That obvious solution have some quick-wins with outcome of found bugs before releasing the software. But there are some tradeoffs, such as: slower delivery cycle, extra test documentation and GUI automated tests that are not that easy to maintain. During my talk I would like to share some insight and lessons we learned @ Spotify that helps us improving team's development productivity without losing quality of the product. Hopefully that will help your team as well or at least show one of the directions you might want to follow. Spotify Engineering Culture: https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/ https://labs.spotify.com/2014/09/20/spotify-engineering-culture-part-2/

Appium Mobile Test Automation like WebDriverAndrii Dzynia

How to Manage Testing in Dynamic WorldAndrii Dzynia

ExtJS WebDriverAndrii Dzynia

10 правил agile тестировщика IT-BrunchAndrii Dzynia

Working Software Over Comprehensive Documentation

Не один десяток раз каждый из нас видео этот пункт Agile манифеста. Кто на официальном сайте Agile Manifesto, кто в книгах или статьях, кто на тренингах или конференциях. Звучит правильно очевидно и просто, но на практике возникают некие сложности с его реализацией. Как определить какие документы писать нужно, а какие не стоит? Как поддерживать документы с наименьшими усилиями? От каких документов нужно отказаться или заменить на более простые решения? Что стоит документировать тестировщику, разработчику, бизнес-аналитику в Agile проектах, для того чтобы презентовать результаты своей работы. На все эти вопросы я постараюсь ответить в своем докладе, закрепляя примерами которые вы сможете попытаться применить на своих проектах.

«Самоорганизуй» себя, пока не «самоорганизовали» тебя

«Возможно ли управлять временем? Спорный вопрос. Время идет и мы ничего не можем поделать. Но в наших силах научиться управлять собой, своими привычками, идеями. При этом, очень важно, чтобы мы управляли своими собственными идеями, а не теми которые кто-то придумал за нас. Учиться самоорганизации можно по-разному и каждый находит свой индивидуальный путь обучения. На докладе я расскажу о своем пути развития Self Management System(SMS), о тех практиках которые применял и продолжаю применять ежедневно».

Как не нужно писать Gherkin сценарии

“Очень часто, внедряя Behavior Driven Development на проекте, думаешь только о быстрых выгодах и о краткосрочной перспективе. На первый взгляд нету ничего сложного в том, чтобы написать приемочный сценарий в стиле Given When Then, простым языком и дальше связывать эти конструкции с языком программирования. Но как показывает практика у многих возникают сложности с составлением непосредственного сценария. Если написать сценарий не правильно, это может повлиять на весь процесс разработки как приемочных тестов, так и на логику работы самого приложения. В докладе я расскажу о том с какими проблемами сталкивается каждый проект, внедряя практику Acceptance Test Driven Development используя Gherkin синтаксис для написания приемочных тестов. На примерах мы рассмотрим частые ошибки при написании приемочных сценариев и разберем основные правила, которые нужно использовать для того, чтобы Acceptance Test-ы помогали каждому члену команды. Доклад будет интересен как тестировщикам, так бизнес аналитикам и разработчикам.”.

iOS and Android Mobile Test Automation

Мир мобильных телефонов очень сильно изменил нашу жизнь. В наше время невозможно представить современного человека, без этого чудо устройства. На рынке появляется все больше устройств и приложений. И чтобы удобнее пользоваться этими приложениями пользователи выбирают “умные” телефоны, или как их еще принято называть смартфоны. В своем докладе я хочу поделиться своим опытом автоматизации приложений под Android и iOS. Я расскажу о том, какие инструменты автоматизации я использовал. Поговорим о недостатках этих инструментов и какие из них стоит использовать у себя на проекте.

10 правил Agile тестировщика

Тема тестирования в Agile очень большая. Ведь теперь за качество отвечает не отдельный QA департамент, а вся команда разработки. Но не стоит забывать, что на тестировщика ложится намного больше обязанностей и требуется набор новых навыков и умений. Уже немало докладов было на эту тему. Я не хочу повторять предыдущих спикеров, а лишь подведу итог своей работы тестировщиком в Agile командах в простых 10 правилах.

Что такое Exploratory Testing?Andrii Dzynia

Software testing 2.0Andrii Dzynia

Тестировщики Vs Программисты