Injecting Acceptance TDD

I!"#$%&!' A$$#p%(!$# TDD )r

w*+ T#,% A-%).(%)r R)/# &, DEAD

@(0z+!&(Saturday, October 12, 13

Test Engineer / Consultant / Trainer

@(0z+!&((0z+!&(.$).

ANDRII DZYNIA

Saturday, October 12, 13

http://adzynia.com

http://adzynia.com

Scrum Team

4 D#v#/)p#r,T#,%#r

T#,% A-%).(%)rB-,&!#,, A!(/+,%

S$r-. M(,%#r


The Flow


The Flow


The Flow


To Do In Development Code Review Testing Demo

User Story

User Story

User Story

User Story

User Story

User Story

User Story

2 Days Before Demo


Daily problems

There is no ID how I can catch the element

How I can test that?

How do you want me to show this on demo?

This is not what business initially wanted


Hidden problemsAcceptance Tests desynchronize with development

Test automator is yesterday tester, CODING skills are not identical to programmer’s

Developers do not own acceptance tests, "it's not our job"


Let’s try Acceptance TDDT#,%-1r,%, !)% %#,%-(2#r


BA Dev Tester

User Story


BA Dev Tester

User Story


BA Dev Tester

User Story


BA Dev Tester

User Story


BA Dev Tester

User Story


BA Dev Tester

User Story


BA Dev Tester

User Story


BA Dev Tester

User Story


Acceptance ScenariosTesting ChecklistTestability Tasks

Outcome




Step 1

test automators to automate tests in parallel with development

HAVE more discussion on user story


New Problems

Requirements are not clear enough

Developers do not own acceptance tests

Test Automator fixing tests all the time


STEP 2

Make internal Acceptance TDD training

Prepare detailed description of the process

Explain how it should be to everyone


CORE Problem

Work as Acceptance TDD is hard

if you never tried TDD (test-first)


Step 3Deep into and make hands dirty

Implement feature in pair with developers

Minimize test scenarios on UI layer


W# r#.)v# %#,% (-%).(%)r r)/#... And yes


Developer’s ExcusesAcceptance tests are slow (write small tests, cover as much as possible on layers below UI, cover on UI at least positive cases that you are going to show on demo)

Writing tests required switching context(Import acceptance test project into the same workspace, start application implementation from Acceptance Test)

Tests are failing because of timeouts (learn web driver deeper, hire web driver expert to the team to coach people and adapting your framework, use JS calls)

I do not have IE on my Laptop (run tests under IE just on server, to debug configure remote web driver)

I do not want to wait until it finished (make tests smaller, use web services as preconditions and post conditions. Use HTTP request call if you do not have web service, minimize tests on UI)

Requirements are not clear enough(how could you start writing code if you do not understand the goal????)


Test Automaton Facts

Software developers are know better to test something on layer

below and can do it during implementation

Test Automator role rise from people who

was trying to automate manual testing


What Test Automators do now?

Support injection of Acceptance TDD

Maintaining Acceptance Testing Framework

Helping to define testability spikes

Moving UI checks on lower layers


Test Automator

==

Software Developer


Test Automator

==

Software Developer(in Test)


Lessons Learned

Define a test strategy

Make you hands duty

Listen to the people

Pitch - not sell

Better to show rather than pitch


Test Automator role is

an excuse for developers

not to do

test Automation


@adzynia

adzynia.com

Email:

[email protected]


mailto:[email protected]






































































To Read


Date post:	05-Dec-2014
Category:	Technology
Upload:	andrii-dzynia
View:	1,181 times
Download:	0 times

Injecting Acceptance TDD

Technology