TestCon Vilnius 2018

Victo, Poland

Bogdan Bereza

Programmer, tester, psychologist, qualitologist, business analyst, traditionalist, agilist and explorator. Pragmatic to the bone and visionary dreamer, all in one person. Combines testing with requirements engineering, mixes enthusiastic agile and exploratory approach with cautious pre-emptive planning and links practical project work with book-writing and teaching. Bogdan has experience from different domains, IT and otherwise, as well as from different countries. Appreciated by students for his fondness to make difficult subjects straightforward. Enjoys being 60 years old since it gives him the ability to distinguish between bogus, refreshed semi-novelties and real novelties, and helps to create true value.


Business Process Testing

A chaotic process is never charismatic, it’s annoying – business process testing may change this.

At the end of the 20th century, a phenomenon occurred, that influenced testing profoundly: the emergence of internet technologies, which made dramatically novel business approaches possible.

1. On one hand, this created the situation, where rapidly changing requirements
demanded shorter product life-cycles, and were often incompatible with traditional methods of software development. This meant the advent of XP and, to some extent, of exploratory testing, also referred to as context-driven or rapid testing.

2. On the other hand, the enormous business potential offered by the new
technologies created demand for tools enabling you to describe, optimize, automate, or even obliterate and replace, business processes accurately, flexibly
and fast. This demand created new, more powerful process modelling methods,
including BPMN.


Test @ Agile

In both agile and traditional projects, the notorious difficulties of deciding
requirements’ priorities are convincing symptoms of the lack of any thought
given to risk beforehand.

The agile-like approach is far older than most 25-years old enthusiasts of lean startup and continuous integration realize: it was first defined in Tom Gilb’s Evolutionary Project Management (EVO) in 1970s, and re-appeared to some extent in every iterative methodology since then. However, two factors gave XP, TDD and agile a real kick forward. They were the internet-based process re-engineering revolution of late 90s and early 2000s, and the spread of mobile technologies and smartphones. The need to create working applications very fast, without really knowing in advance the business process they were supposed to support, resulted in a full-blown, comprehensive agile revolution.