The document discusses the necessity of test-driven development (TDD) for Java developers, emphasizing that testing allows for easier code refactoring and maintenance. It highlights the consequences of not testing software and presents statistics on the acceptance of TDD in various companies. The author also asserts that developers are ultimately responsible for the quality of their code.

1. {
„Heutiger“ Stand
von TDD
Alexander Orlovsky
Freiberufler
Oracle Certified Java Professional Programmer
Oracle Certified Web Component Developer
Fachinformatiker (IHK) Anwendungsentwickler

2. DISCLAIMER
I am not claiming that i know how to solve all software engineering problems.
Neither you should follow all of my advises,
this is my personal opinion about software development in general.
THERE NO SILVER BULLET TO SOLVE ALL IT PROBLEMS!
Use common sense and seek support in your dev teams first!

3. Why we as Java
developers must test our
software?

4. Why we should think
about consequences when
we don’t test our
software?

8. Why we write our
test's?

9.  We write test to impress our
manager, colleguess, QA, stake
holders?
 We write test because it is policy of
our company?
 We write test because we ensure that
our design architecture is right?
 We write test because we must
ensure that we implement recent
feature request from our
customer/client?

10. THE REAL REASON WHY WE WRITE
TEST‘S IS:
WE WANT TO BE ABLE TO
REFACTOR OUR CODE ANYTIME,
BECAUSE WE DON‘T WANT TO
CREATE A MESS !
LETS REPEAT IT AGAIN!!!
WE WANT TO BE ABLE TO REFACTOR
OUR CODE ANYTIME!

11. Code examples

12. Not convinced?
What about Enterprise ?
For example Java EE (Remote EJB),
Spring, Spring Boot ?
• Alien which can help us!
http://arquillian.org/

13. Code example

14. What actually business
demand from us?

15. We as java developers must care
about software:
• Consistency
• Stability
• Accuracy
• Provide high customizable software
• Our software must be easy to maintain , easy
to extend and deploy

17. Reality

18. Stats:From ca. 100 companys with witch i had
personal discussion about TDD:
ca. 50% Rightaway decline my offer of
TDD!
ca. 25% Will think and still think about
it!
ca. 25% Agreed but with very shortterm
and almost imposible conditions i still
negotiate the final terms with them!!!!

19. Barry Boehm und Victor R.
Basili
“Finding and fixing a software
problem after delivery is often
100 times
more expensive than finding
and fixing it during the
requirements and
design phase. “

20. Example what one company
told me in 2018:
* Testgetriebene Entwicklungsverfahren".
Das ist bei uns im Moment nicht möglich
und auch in näher Zukunft nicht umsetzbar.
Es ist zwar geplant, aber diesen Punkt
können wir frühestens in einem Jahr in
Angriff nehmen. Wenn Sie direkt mit
"Testgetriebener Entwicklung" bei uns
anfangen möchten sind aber unsere Kollegen
noch nicht so weit.

21. Firmenaussagen in 2018:
*wir arbeiten derzeit nicht mit einem
klassischen TDD - dennoch achten wir auf
eine ausreichende Test Coverage

22. Conclusion!
• Who is responsible for our code which
we as Java developers write?

23. • We, the developers are
responsible for our work!
Copyright source http://memory-alpha.wikia.com/wiki/Heart_of_Glory_(episode)

24. Any feedback,
suggestions, questions?
• Contact (i am always open for interesting
work and hire):
Email: javaprofi@gmx.de
Xing: https://www.xing.com/profile/Alexander_Orlovsky
Linkedin: https://www.linkedin.com/in/alexander-orlovsky-44570b6/
Youtube: https://tinyurl.com/y736ldgh