Permalink
Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
489 lines (342 sloc) 36.6 KB

Markus Tiede

> Dipl.-Inf. (FH)
> Softwaredeveloper

An official picture of me - Markus Tiede

* 28.06.1985

bio

en

Markus is a software developer and release engineer with focus on high quality standards. Besides being an open-source Eclipse Foundation committer and Package Maintainer for „Eclipse for Testers“ he holds a Diplom (German degree) in Computer Science from the University of Applied Sciences in Braunschweig.

de

Markus Tiede arbeitet als Softwareentwickler und Release-Engineer mit starkem Fokus auf hohe Qualitätsstandards. Markus ist darüber hinaus Eclipse Foundation Committer, Package Maintainer für „Eclipse for Testers“ und hat einen Abschluss als Diplom-Informatiker von der FH Braunschweig-Wolfenbüttel.

Friend of Eclipse

ToC / Inhaltsverzeichnis

talks / Vorträge paper / Artikel
2018
2017 ...
2016
2015 ... ...
2014 ... ...
2013 ... ...
2012 ... ...
2011 ...
2010 ... ...
2009 ...
2008 ...

talks / Vorträge

talks 2017

en UI test automation using the Jubula API: the why, the how and the what

Join Markus and Alex in this tutorial to learn how to use the Jubula Client API to write good UI test cases for your application. UI tests aren’t often a favourite pastime for developers, but they do provide useful feedback from the user perspective: they let us know whether the desired workflows are possible via the UI. They are a great addition to other test levels for a well-designed test strategy.

Jubula’s main target group is testers without programming skills, but since early 2015, the Client API allows users who can program to write Jubula tests. The Client API offers a wide variety of actions for automating via the UI for Swing, SWT/RCP/GEF and JavaFX.

This tutorial has two main learning objectives:

Working with the Jubula Client API to write automated tests Getting started with the concept of equivalence class analysis to write just the right amount of UI test cases. This part is independent of the tool or testing level used and thereby an universal takeaway.

In this tutorial we’ll cover:

  • An introduction to Jubula and to UI testing
  • Working with the Client API
  • Defining and starting applications
  • Writing tests
  • Analysing test results
  • Equivalence class analysis and how to easily apply and use them for UI tests
  • Integrating Jubula, test design and test automation into your process

en Pipelining quality - best practices, lessons learned and tools for continuous delivery processes

In this talk Markus will share hands-on project experience for building and maintaining CI processes applicable in small and large enterprises projects.

After a short introduction to the project context Markus will focus on best practices, lessons learned and tools used within automated deployment chains based on state-of-the-art Jenkins pipelines.

In this talk you will join the journey of an epic, a user story and a bugfix from

  • its beginning as requirement or defect,
  • over its implementation in source code,
  • to both static and dynamic code quality assurance mechanisms,
  • its rollout in integration and acceptance stages,
  • up to its deployment, monitoring and maintenance in production

This talk aims at anyone interested in general ideas and means for continuous integration techniques in both agile and classic project layouts.

Besides his many years of experience in test automation, Markus recently gained a lot of insights during his daily business working as a release manager and engineer in an ongoing large-scale insurance enterprise project called Galileo at the Basler Versicherungen in Switzerland.

en Getting started with Jubula - an UI test automation framework

Over the last couple of years Jubula has grown to a versatile UI test automation framework which supports

  • a wide variety of application technologies (including JavaFX, SWT/RCP, GEF, Swing, HTML, ...) as well as
  • two very different testing approaches: keyword-based code-free automation in the ITE vs. IDE coding and executing tests directly e.g. as JUnit suites

As with all larger frameworks it is good to know where to start and where to head especially if different paradigms come into play. This talk will give you

  • an overview of Jubula 5.0 (coming with Oxygen) and
  • a 1:1 hands-on comparison (including many demos) of the pros and cons for the two testing approaches.

This talk is suitable for anyone interested in automated testing, regardless of their experience.

talks 2015

en Jubula 101

Come to this talk to get your 101, your 411 and possibly some other important numbers about the Eclipse Jubula project for functional testing.

Jubula is an automated GUI testing tool for a variety of applications (including JavaFX, SWT/RCP, GEF, Swing, ...). The focus of the tool is on improving communication about and through testing, and on providing up to date quality information throughout the development process. It does this in three main ways:

Tests aren’t written in program code, so they are accessible and writable by anyone on the team (even, and especially, members who are not software engineers). Tests aren’t written by recording actions and replaying them, since this leads to redundancies, a great deal of effort, and also means that testing can only begin when the feature is completely implemented. There’s plenty of support for writing good, stable and robust tests by using reusable modules, separation of data and objects from the test workflow, intelligent checks and error handling. Basically, if you want to test that your use cases are actually doable – in the same way that the users will work with your software – but you don’t want to test all your use cases manually, then you should come along to find out more.

This talk will take you on a journey through the "what is Jubula“ via the "how does it work” to a demonstration of the tool including how it plays well with continuous integration and application lifecycle management tools. There'll be time for questions at the end to cover anything else that’s important.

en Jekyll and Hyde with Jubula

Can a test tool have more than one personality? Can a new alter ego develop over time? It turns out, yes!

One of the most salient features of working with Jubula is that tests are created via drag and drop from a library of pre-defined actions. While knowledge about testing and a certain technical affinity / capability to structure and model is required, programming knowledge is not.

Jubula’s main target group is teams with members who don’t program – to ensure that test automation is something that the whole team can work on. The question has frequently been asked though: isn’t there a way to let a developer write tests in Java using the mature Jubula remote control code? We’re pleased to announce that the answer is now yes.

And so we introduce Mr Hyde – the Jubula API. He’s not actually evil, but he is definitely a new and exciting personality for Jubula. This talk will present participants with both aspects of Jubula’s personality:

  • Dr Jekyll: writing tests with the Jubula actions in the ITE
  • Mr Hyde: writing Jubula tests in Java

We’ll show how the steps to start AUTs, write tests and perform test execution can be done using both aspects of Jubula. The talk will be on an introductory level to show participants their way around the tool and its features from both perspectives.

talks 2014

en J2J - JavaFX testing with Jubula

JavaFX is the new black in modern Java based Ul technologies - again. And as of Java 8 a stable and refined JavaFX API is available out-of-the-box for the general public. That said, it's no wonder that we - the Jubula team - have been working very hard to support this new Ul technology for test automation right from the very beginning.

In this session Markus

  • will give a brief introduction to Jubula and its concepts,
  • demonstrate how easy it is to automate Ul tests for JavaFX / e(fx)clipse based AUTs (Application Under Test).
  • point out the current development status of the JavaFX support and its architecture

This talk is primarily aimed at people with a general interest in JavaFX and code-free test automation.

talks 2013

en To infinity and beyond – making Jubula surpass its limits

As the Jubula team, we’re generally quite proud of the out-of-the-box support we have. However, we’ve been involved in enough projects to know that there are sometimes boundaries that are hard to solve when thinking about realizing them with Jubula, for example:

  • working with custom test data and data structures
  • robust UI widget recognition
  • remote controlling custom UI controls
  • addressing GEF figures
  • getting individual test results
  • ...

Even if what you’re looking for isn’t in the tool, there are many ways in which you can extend Jubula to go beyond its limits:

  • Integrated Testing Environment – extending the ITE
  • Adding test data functions
  • Writing your own BIRT reports
  • Providing your own unbound_modules_*
  • Defining your own test style rules
  • Installing your own plugins e.g. Mylyn connectors
  • Writing your own views
  • Remote Controlling – extending the RC
  • Improving UI-widget recognition in Swing, SWT, HTML, iOS
  • Improving GEF testing by enhancing the identifier
  • Supporting custom renderer solutions for Swing, SWT, iOS
  • Adding support for custom monitoring agents
  • Adding support for foreign keyboard layouts
  • Toolkit extensions for “wacky widgets”
  • Adapting your widgets to our toolkit abstraction
  • Supporting your own components, actions and toolkits

In this talk Markus will give an overview of Jubula's concepts and architecture as well as many hands-on examples how to extend all these different aspects of Jubula to make it fit your specific needs.

This talk is aimed at people who have a general interest in UI test automation and Jubula, as well as users who may have already faced some of the limits of test automation. We won’t be losing you in the minute details of each aspect, but we will make sure you know what’s possible and how to go about doing it.

en Jubula Tutorial – Specify, execute, analyze

The world needs more acceptance tests. They tell us whether or not the software being developed does what the customer ordered and give us a great opportunity to amend misunderstandings and problems before a product is released. Doing this kind of testing manually is repetitive, error-prone, boring, and also hopeless – there is no way that manual acceptance testing can keep up with development, especially if you aim to have continuous feedback about quality. The Eclipse Jubula Project for functional testing lets you automate these kinds of tests, and it does so without requiring you to write program code, and also without having to resort to recording user actions.

“How does that work?” we hear you ask. How are tests specified to be intelligent and robust? What happens if changes occur? And how do tests fit into the development process? All excellent questions. [...]

en Testing mobile applications with Jubula

After multiple years of experience with testing desktop toolkits, the GUIdancer / Jubula team made their first foray into the world of mobile testing with version 7.0 of GUIdancer. Since the feature-merge in the standalone versions of Jubula and GUIdancer, iOS testing is now available to everyone, and we’ve already started work on other mobile toolkits.

This talk looks at mobile testing both from a technical perspective as well as from the view of a tester of mobile applications. We cover points such as:

  • Transferable knowledge from desktop testing – test design and component interaction
  • New aspects involved with mobile testing
  • increased variety and diversity (platforms, devices, versions)
  • new functions to consider (external applications, GPS, battery)
  • new interactions (gestures)
  • The interesting challenge of cross-platform applications
  • Setup and environment considerations for mobile testing
  • Starting and connecting to applications
  • Communication with an application under test
  • Continuous integration
  • Specialties of mobile robots

The aim of the talk is to present the support in Jubula and GUIdancer for mobile testing, as well as to provide background information on mobile testing in general. Alongside the theory, we’ll also show some demonstrations.

de UI-Testautomatisierung für mobile Plattformen

Die BREDEX GmbH hat als Open-Source Testtoolhersteller für Desktop-Applikationen jahrelang ausgiebig Erfahrungen im Bereich der User-Interface Testautomatisierung sammeln können. Dabei haben sich eine Vielzahl von Konzepten als tragfähige Grundlage für die Qualitätssicherung von Anwendungen bewiesen, um eine nachhaltige und kosteneffiziente Automatisierung betreiben zu können. Zu diesen Konzepten zählen

  • die strikte Entkopplung von UI-Toolkit-Technologie und Testsprache
  • das Bereitstellen von „high-level“ UI-Automatisierungsbausteinen die eine natürlich-sprachliche Testspezifikation ermöglichen
  • die Wiederverwendbarkeit von Tests zu fordern und zu fördern

Dieser Vortrag zeigt am konkreten Beispiel „iOS“ die Probleme und Schwierigkeiten des Transfers eben diese Konzepte in die Welt der mobilen Plattformen zu übertragen und demonstriert zugleich das große Potential der technologieübergreifenden Testautomatisierung auf mobiler Hard- und Software.

de UI-Testautomatisierung für mobile Plattformen – Herausforderung und Chance zugleich!

Dieser Vortrag zeigt am konkreten Beispiel iOS und Windows 8 die Probleme und Schwierigkeiten, die Konzepte der Desktopwelt in die der mobilen Plattformen zu übertragen und demonstriert zugleich das große Potential der technologieübergreifenden Testautomatisierung auf mobiler Hard- und Software. Es werden dabei sowohl die grundlegenden Technologien und Konzepte, als auch konkrete Erfahrungen der mobilen cross-plattform „App“-entwicklung und -testautomatisierung erläutert. Belegt und unterstrichen wird dies durch eine Reihe von Demonstrationen.

en Continuous testing with Jubula – where the rubber meets the road!

You've got software. You've got a list of features to implement. You've got some automated tests. You've got upcoming releases. The only glue that is going to make this scenario work is Continuous Integration. When you're adding and changing functionality, knowing what your changes are doing to your quality on a daily basis can be the difference between a successful release and a horrifically painful one. A project team needs to be able to make qualified decisions based on quality information at any given time, which is why you’ve got to hit the road (the application under test) with the rubber (the automated tests) as often as possible!

In this session Markus will give a full technical walk-through of all the necessary steps to setup Jubula tests in various continuous integration scenarios.

After starting with a super-quick overview of Jubula's concepts and architecture for any Jubula "newbies" in the audience, Markus moves onto a live walk-through of the necessary steps to get Jubula and Hudson playing well together. On the way, we'll look at topics such as:

  • setup, maintenance and teardown of the test environment
  • useful Jubula tools, configurations and settings
  • Hudson options to optimize scheduling and test distribution
  • making the whole system work for more complex test scenarios such as testing multiple AUTs and projects on various architectures and operating systems.

This talk is designed to give a detailed technical road-map for successful continuous testing with Jubula.

talks 2012

en UI testing with Jubula - wacky widgets

Standard widgets and usage concepts are great. They are known by users, respond in expected ways, and are generally testable out-of-the-box with UI automation tools like Jubula.

Apparently though, standard widgets are boring, that table-in-a-combo-box-with-a-tree-in-it is the new black. Joking aside, the temptation (or necessity) to stray from the standard path will happen to all of us at one time or another. Good examples for that can e.g. be found in the Nebula project. You may well ask yourself what that means for UI testing ...

In this session Markus will give a brief introduction to Jubula and its toolkit concepts, as well as demonstrate how easy it is to extend Jubula to support custom UI widgets.

talks 2011

en Starting an Eclipse Project: The first 90 days… and the year that follows

What are you getting yourself into by deciding to host your project at Eclipse? From the decision to open source your software, to the formal processes for intellectual property and development, all the way up to the generation and care of the community, the road may contain more twists and turns than you expect. Unless of course, you have a map – which is what we’d like to try and give you.

This talk looks at the steps for hosting your project at Eclipse from various aspects, and through two sets of eyes. Wayne Beaton combines his knowledge of the Eclipse and IP processes with the recent experiences of Markus Tiede, a committer on the new Jubula project. Together, they navigate through the “why” of open sourcing software, the “how” it is done at Eclipse, the “what” else to expect, and the “who” of the project – the community.

talks 2010

de Automatisiertes Testen mit Jubula

Ab März werden Kernteile von GUIdancer als Open Source Projekt in der Eclipse Foundation veröffentlicht. Das Jubula Functional Testing Tool Projekt ermöglicht die Erstellung und Ausführung automatisierter Akzeptanztests anhand von den bekannten Best-Practices aus der Softwareentwicklung (Lesbarkeit, Modularität, Wartbarkeit) ohne jeglichen Programmieraufwand. Das Verfahren des Keyword-Driven Testings erlaubt außerdem eine frühzeitige Testfallerstellung, welches die Einbindung in agilen Prozessen unterstützt. In diesem Talk stellen wir das Jubula Projekt vor und geben eine Vorführung des Tools.

talks 2009

en Write Once, Test Everywhere? Cross Platform Development and Testing with Eclipse

How platform independent are Eclipse applications in practice? This talk looks at some of the differences between operating systems supported by Eclipse with respect to RCP applications and examines their effects on usability, development and testing.

This webinar is aimed at developers, project managers and testers (automated and manual) working on RCP applications that are intended to run on more than one platform. Participants will learn about large and small differences between the platforms. Some of these differences must simply be considered in the development and testing process, others mean that testing, documentation and development are affected.

Some of the points raised include:

  • How widgets can behave differently on the platforms
  • Variation in the library support for each platform
  • Other GUI considerations such as tooltips, toolbars, buttons and focus
  • Automated testers will also benefit from the information and examples in the talk. Ideally, only one automated test should be necessary to test all versions of an application. Some of the differences between the platforms make this aim difficult, and some differences mean finding a lowest common denominator to be able to write tests. The variation between the platforms is therefore something which must be considered at the test planning stage, and in the test design itself.

Participants will learn to consider and deal with any variations between platforms to make cross-platform projects a success.

talks 2008

en Best Practices for the Creation of Automated Agile GUI Tests

This class uses insights and project experience from agile development processes to suggest requirements and solutions for automated agile test design. Begin by looking at the agile development process to determine the requirements for agile testing. Then hear practical solutions to achieving these goals within a project based on real industrial project experience with automated agile testing. Aimed at testers and project managers, the class offers a set of practices that enable tests to grow alongside product development, ensuring that both new and old functions are tested at each release.

en Automated GUI Testing - common misbeliefs

This 5-minute lightning talk emphasised spotting the spam when thinking about UI test automation tools.

paper / Artikel

paper 2015

de Jubula goes JUnit – Eine Einführung in das Jubula-Client-API

Seit nunmehr zehn Jahren verfolgen wir im Jubula-Team das Ziel, Testautomatisierung für grafische Benutzeroberflächen zu ermöglichen, ohne dabei zwingend notwendig über tiefgehende Programmierkenntnisse im zugrunde liegenden UI-Toolkit oder im internen Aufbau der AUT (Application under Test) zu verfügen. Und auch auf unserem Weg zu Mars haben wir trotz der Einführung eines Java-API für Entwickler stets darauf geachtet, dieses Ziel nicht aus den Augen zu verlieren. [...]

paper 2014

de Jubula goes JavaFX: Technologietransfer leicht gemacht

Pünktlich mit Java 8 hat Oracle im Frühjahr dieses Jahres eine grundlegend überarbeitete Version der Benutzeroberflächentechnologie JavaFX veröffentlicht. Dieses auf multimediale Inhalte und Effekte optimierte UI-Toolkit gilt bereits seit einiger Zeit als Nachfolger von Swing und erlaubt es, mit Leichtigkeit moderne, reaktive und ansprechende Benutzeroberflächen zu gestalten. Für uns, das Jubula-Team, bedeutete das: neues Jahr – neues Toolkit! Standen für uns im letzten Jahr mobile Plattformen wie iOS im Fokus, so war es im „Luna“-Jahr die einfache und zuverlässige Anbindung zur Fernsteuerung und Testautomatisierung von JavaFX-Oberflächen. Wir geben einen detaillierten technischen Einblick in die notwendigen Grundlagen zur Anbindung von JavaFX-Applikationen in Jubula und zeigen die notwendigen Schritte des Testtechnologie-und Know-how-Transfers von bekannten Jubula-Toolkits wie Swing und SWT zu JavaFX. [...]

en Automated Acceptance Tests for Mobile Applications: Thoughts on Test Strategy

First impressions count when it comes to apps, be they tailor-made enterprise apps or apps from a store. It has never been so easy to try out new applications – and then uninstall them if they are not suitable or acceptable. The consequences can be much worse than just losing one customer or user; public feedback systems and disappointed customers can damage the reputation and image of an app, as well as of the company behind it.

For this reason, the user perspective is of utmost importance when developing mobile applications. Acceptance tests help teams to recognize early whether an app behaves as expected and does not produce any unwanted side effects during use. As for any project, we need to decide what to test, how to test, when to test, and how much to automate. However, automation in particular can be a tricky subject for mobile applications, and the specific challenges should be taken into account when defining a test strategy. [...]

paper 2013

de Automatische Akzeptanztests für mobile Anwendungen - Überlegungen zur Teststrategie

Ob individuell entwickelte Enterprise-Apps oder Apps aus dem Store – die Meinung zu einer App wird schnell gefällt. Noch nie war es so einfach, eine Anwendung auszuprobieren und bei Nichtgefallen zu deinstallieren. Die entsprechenden öffentlichen Bewertungen oder das Feedback vom Kunden können den Ruf und das Image der App und auch der dahinter stehenden Firma schnell verbessern oder verschlechtern.

Die Benutzerperspektive anhand von Akzeptanztests zu vertreten ist deshalb für mobile Anwendungen besonders wichtig. So kann man frühzeitig feststellen, ob eine App einerseits das gewünschte Verhalten besitzt und andererseits keinerlei unerwünschten Nebeneffekte bei der Bedienung auftreten. Wie für jedes Projekt muss dafür eine geeignete und angemessene Teststrategie einschließlich Testarten und -methoden, Automatisierungsgrad und Zielplattformen definiert werden. Besondere Herausforderungen lauern allerdings beim automatischen Testen mobiler Apps, die – so viel sei schon vorweg gesagt – Auswirkungen auf Ihre Teststrategie haben werden. [...]

de Tip, Tap, Test: Automatisierte Tests im mobilen Umfeld – der Umstieg aus der Desktopwelt

Im privaten Bereich ist der mobile Zugang zu Daten und Diensten schon alltäglich – im Arbeitsumfeld noch nicht überall. Aber gerade dort kann der direkte Zugang zu aktuellen Daten und Diensten enorm vorteilhaft sein. Für den Kunden sowie für den Dienstleister ist also ein Umdenken erforderlich – insbesondere beim Thema Testen. Welche Besonderheiten gibt es beim automatisierten Testen? Und mit welchen Techniken und Technologien lässt sich erfolgreich Qualitätssicherung betreiben? [...]

paper 2012

de Open Sourcing and Release Engineering @ Eclipse.org - The Making of an Eclipse Project

Was steckt eigentlich hinter einem Eclipse-Projekt? Welche Entscheidungen sind zu treffen, welche Bedingungen zu erfüllen, wie läuft das alles? Das Eclipse-Jubula-Team berichtet in loser Folge über seine Erfahrung beim Open Sourcing von Jubula. Dabei geht es nicht nur um Technik, sondern auch um Strategien, Abläufe und schwierige Entscheidungen. [...]

paper 2010

de Refaktorisieren von Tests - Erfahrungen aus der schlüsselwortgetriebenen Testentwicklung

Tests und Testautomatisierung sollen helfen, Kosten zu sparen und die Softwarequalität zu erhöhen. Damit das mittel- bis langfristig gelingt, müssen auch Tests „gehegt und gepflegt” werden. In diesem Artikel erfahren Sie anhand ausführlicher Beispiele, welche Möglichkeiten des Refaktorisierens dabei helfen, dieses Ziel zu erreichen und es nachhaltig zu sichern. Der Artikel basiert auf mehrjährigen Erfahrungen im Bereich des schlüsselwortbasierten Testens, gibt konkrete Hinweise zum erfolgreichen Refaktorisieren in diesem Umfeld und verdeutlicht diese an einer Beispielapplikation mit dazugehörigem Test. [...]

en Test design for stubborn applications - Event handling in automated acceptance tests

At the beginning of any test automation project for acceptance tests, the focus is usually on creating a set of running tests to cover the most critical or newest aspects of the software being developed. Such acceptance tests see the application as a black-box, testing the business logic through the GUI. Once a good base of runnable tests has been produced, however, it quickly becomes critically important to ensure that events that affect one part of the test do not lead to all other tests subsequently failing (due to “inherited” problems from the first failure), or not running at all (because the whole test has been aborted) . The discovery of errors in an application is a natural and desired effect of automated acceptance tests; however, the other aim of acceptance testing should always be to have the most comprehensive knowledge of the software quality. If 90% of the tests cannot run because an event occurred in the first 10%, this aim cannot be achieved. The quality will suffer as a result, and the costs to fix any subsequent untested errors will increase as more time passes between introducing the error and finding and resolving it.

A well thought-out system of event handling is therefore necessary to ensure that the quality of the whole software project can be monitored despite problems in individual areas. In addition, adding event handling to the project can make it easier to find and reproduce errors to allow them to be fixed in a short time. This article offers strategies and suggestions on introducing robust and understandable event handling in automated acceptance tests. [...]

de Modellbasiertes Testen grafischer Benutzeroberflächen: Ein Erfahrungsbericht

Taschenbuch: 108 Seiten
Verlag: VDM Verlag Dr. Müller
Erscheinungsdatum: 21. März 2010
Sprache: Deutsch
ISBN-10: 3639239334
ISBN-13: 978-3639239331

Dieses Buch beschäftigt sich mit dem Thema, aus Modellgraphen, die Informationen zur Funktionsweise eines Systems beinhalten, Testabläufe zu generieren. Das Buch erläutert dabei das zugrundeliegende Datenmodell der Modelle und zeigt, wie auf dieser Basis Testabläufe erstellt und gepflegt werden können. Auch die zur Umsetzung verwendeten Frameworks, wie das "Eclipse Modeling Framework" (EMF), das "Graphical Modeling Framework" (GMF) und die "Eclipse RCP" werden detailliert vorgestellt. Softwareergonomische Aspekte und Anwendungsbeispiele der Software schließen das Buch ab.

other qualifications / weitere Qualifikationen

2018: Certified Professional for Software Architecture – Foundation Level (iSAQB)

Erfolgreiche Zertifizierung zum "Certified Professional for Software Architecture" des iSAQB CPSA-F®


My iSAQB CPSA-F®

2013: Certified ScrumMaster®

Erfolgreiche Zertifizierung zum CSM¹.


My CSM certificate

¹ Certified ScrumMaster is a certification mark of Scrum Alliance, Inc. Any unauthorized use is strictly prohibited.

2009: IHK Ausbilderschein

Erfolgreich absolvierte Ausbilder-Eignungsprüfung der IHK Braunschweig.


My AEVO certificate

other references / weitere Referenzen

LinkedIn:   https://www.linkedin.com/in/markus-tiede
XING:       https://www.xing.com/profile/Markus_Tiede
Twitter:    https://twitter.com/MarkusTiede
this:       https://raw.github.com/MarkusTiede/about/master/me.md

==========================