UNIT

 

TESTING

 

Wstęp

O czym będzie mowa?

TDD

junit

mockito

assertJ

clean code

refactoring

Po co

testować?

Co czujesz kiedy robisz refactoring?

Szybszy

development

https://zeroturnaround.com/rebellabs/java-ee-container-redeploy-restart-turnaround-report/

Jak pisać testowalny kod

Co testować?

TDD 

TEST DRIVEN DEVELOPMENT

https://www.slideshare.net/nikitakova/tdd-test-driven-development-53289914?qid=f7d1ba7b-eaa8-4bb6-a895-ffbdd17d1a13&v=&b=&from_search=51

Requires discipline

Quality of design

Quality of implementation

documentation by example

gives confidence

validate your design

constant interation

you are more productive while coding

cleaner code

safer refactoring

fewer bugs

living documentation

make small incremental changes

KATA 

Kata is a Japanese word describing detailed patterns of movements practiced either solo or in pairs

Best practises 

F.I.R.S.T

Fast
Independent
Repeatable
Self-validating
Timely

 

FAST

GIVEN

WHEN

consisent test structure

THEN

Treat your test code like production code

Paulo Testillo

Junit 5 

Kolejność wykonywania testów

AssertJ 

Mockito 

Koniec 

unit-testing

By Kamil Lolo

unit-testing

  • 993