CitconWiki - User contributions [en]

Test Automation Pyramid Adoption

2015-09-12T11:55:16Z

Viktorclerc:

== Introduction ==
The [http://martinfowler.com/bliki/TestPyramid.html Test Pyramid]: We have all kinds of knowledge of what to test at each level and how to "do" it.

== Problem statement ==
How to also make the developers live and believe in the testing pyramid? How to not let it become a perfect nice document that is just lying around but nobody is following it?

== Discussion ==
Suggestion >> Read the book called "Switch". People tend to be reluctant to stuff they don't know. So try to make this into reversible experiments. But the clue is, these are not reversible experiments, but you're basically "dragged into it".

Find why the attitude of the developers is to "just write code". Find the motivation for the behavioral change. This is inherently difficult, since it ultimately boils down to changing humans' behaviours. Even when the drawbacks of the current approach are pretty clear: bugs into production because no-one even bothers to open a browser to do basic testing when the "tester" is on holidays. The bugs in production requires patches which is deviating developers' attention.

Test Automation Pyramid Adoption

2015-09-12T11:54:13Z

Viktorclerc: Created page with " == Introduction == The [http://martinfowler.com/bliki/TestPyramid.html Test Pyramid]: We have all kinds of knowledge of what to test at each level and how to "do" it. == Pr..."

== Introduction ==
The [http://martinfowler.com/bliki/TestPyramid.html Test Pyramid]: We have all kinds of knowledge of what to test at each level and how to "do" it.

== Problem statement ==
How to also make the developers live and believe in the testing pyramid? How to not let it become a perfect nice document that is just lying around but nobody is following it. One of the key elements is that the

== Discussion ==
Suggestion >> Read the book called "Switch". People tend to be reluctant to stuff they don't know. So try to make this into reversible experiments. But the clue is, these are not reversible experiments, but you're basically "dragged into it".

Find why the attitude of the developers is to "just write code". Find the motivation for the behavioral change. This is inherently difficult, since it ultimately boils down to changing humans' behaviours. Even when the drawbacks of the current approach are pretty clear: bugs into production because no-one even bothers to open a browser to do basic testing when the "tester" is on holidays. The bugs in production requires patches which is deviating developers' attention.

CITCONEurope2015Sessions

2015-09-12T10:59:55Z

Viktorclerc: /* 2:00 Topics */

CITCON Europe 2015 Helsinki Sessions

Back to the [[Main Page]]

== 10:00 Topics ==

# [[Test Tools The Next Generation]]
# [[Advanced Unit Testing]]
# [[One Day To Live Elephant Carpaccio]]
# [[Alerts Everywhere]]
# [[GIT Branching]]

== 11:15 Topics ==

# [[Dynamic CI Automatic Test Scope]]
# [[Performance Testing]]
# [[Why Should I Dockerize My App?]]
# [[Manual QA Without Tears]]
# [[Automation vs Security]]

== Lunch Topics ==

# [[...]]
# [[...]]

== 2:00 Topics ==

# [[Test Automation Pyramid Adoption]]
# [[...]]
# [[...]]
# [[...]]
# [[...]]

== 3:15 Topics ==

# [[...]]
# [[...]]
# [[...]]
# [[...]]
# [[...]]

== 4:30 Topics ==

# [[...]]
# [[...]]
# [[...]]
# [[...]]
# [[...]]

== Table View ==

{| class="wikitable"
|-
! Room name
! 10:00
! 11:15
! 2:00
! 3:15
! 4:30
|-
| Auditorium
| [[Test Tools The Next Generation]]
| [[Dynamic CI Automatic Test Scope]]
| [[...]]
| [[...]]
| [[...]]
|-
| 20
| [[Advanced Unit Testing]]
| [[Performance Testing]]
| [[...]]
| [[...]]
| [[...]]
|-
| 16
| [[One Day To Live Elephant Carpaccio]]
| [[Why Should I Dockerize My App?]]
| [[...]]
| [[...]]
| [[...]]
|-
| 18
| [[Alerts Everywhere]]
| [[Manual QA Without Tears]]
| [[...]]
| [[...]]
| [[...]]
|-
| 14
| [[GIT Branching]]
| [[Automation vs Security]]
| [[...]]
| [[...]]
| [[...]]
|}