Critical Analysis Of KDT — a reply to Nikolay Advolodkin

Introduction

What is KDT?

Nikolays Critics and the reply

0: non-squitter

1: “Almost nobody in the world is doing KDT any more”

2: “Unnecessary code must be written to read some external source like Excel”

3: “More complexity by introducing external teams”

4: KDT forces you to create your test runners

5: “KDT forces your tests to be written with interaction commands in mind”

imperative Vs declarative

On a final note

--

--

--

Automation and RPA developer, python developer.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

The Pitfalls of the Logic Sandbox

What’s new from Google I/O 2019

Easy onboarding for iac code repo

Patract Weekly Report#8 (10th-14th,May)

Introduction to Functional Safety for Self Driving Cars

Windows 11 Testers Get Taste of New Mail, Calendar, and Calculator Apps

Windows 11 Testers Get Taste of New Mail, Calendar, and Calculator Apps

Lambda Functions and Parallel Processing

Install CentOS in Virtual Box

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Eldad Uzman

Eldad Uzman

Automation and RPA developer, python developer.

More from Medium

Solving XOR problem using dynamic weights

Kubernetes yaml Overview

Mutual TLS in Action

Mutual TLS in Action

Phantombuster’s googlesheet templates: How to handle heavy files?