The document discusses various testing strategies and tools related to behavior-driven development (BDD) and the testing pyramid, emphasizing the importance of testing in software development. It highlights the use of Gherkin language for writing test scenarios and outlines tools such as Cucumber, test runners, and browsers for executing tests. The document concludes with reflections on the challenges of writing BDD tests and the collaborative nature required beyond just developers.

2. Testa gränssnittet med BDD
Viktor Sarström, Evolve på nForum - 2017-11-23

3. Testning
“If It Ain’t Tested, It Ain’t Fixed”

4. Unit testing
Service testing
Integration testing
Application testing
Acceptance testing
UI testing
End-to-end testing
Performance testing
Exploratory testing
Regression testing
Smoke testing
Manual testing
12+

5. Teststrategier

6. Martin Fowler (Mike Cohn?), TestPyramid
https://martinfowler.com/bliki/TestPyramid.html

7. Alastair Scott, The-evolution-of-the-testing-pyramid
http://james-willett.com/2016/09/the-evolution-of-the-testing-pyramid/

8. James Wade, that testing pyramid
https://wade.be/development/2017/02/20/that-testing-pyramid.html

9. All models are wrong,
but some are useful.
George E. P. Box

10. BDD
Behavior-driven development

11. Gherkin
Business Readable, Domain Specific Language

12. Gherkin
● Beskriva ett beteendet utan att implementera det
● Dokumentation och test
● Finns på 60 språk

13. Some terse yet descriptive.feature

14. Gherkin
● Feature
● Scenario Given, When, Then, And, But (Steps)
● Background
● Scenario Outline
● Examples

15. Cucumber
”Business and IT don't always understand each other.”

16. Cucumber
● Verktyg för att köra tester skrivna i Gherkin
● “A single source of truth for everyone on the team.”
● Implementation finns i .NET (SpecFLOW), Java, PHP, JS, Ruby osv

18. Scribblewall

19. Verktyg
● Test runners
○ cucumber-js, Wallaby, Jest, Karma, SpecFlow ...
● Browser
○ Phantom, Zombie, Selenium, Headless chrome, Nightmare …
● Assertions
○ chai, sinon, shouldJS, Mocha
● Mockning
○ node-mock-server, node-api-server, nock …
● IDE
○ Visual studio 2017, Visual Studio Code, Atom, Eclipse ...

20. Verktyg
● Test runners
○ cucumber-js, Wallaby, Jest, Karma, SpecFlow ...
● Browser
○ Phantom, Zombie, Selenium, Headless chrome, Nightmare …
● Assertions
○ chai, sinon, shouldJS, Mocha
● Mockning
○ node-mock-server, node-api-server, nock …
● IDE
○ Visual studio 2017, Visual Studio Code, Atom, Eclipse ...

21. cucumber-js
test runner

23. Köra samma tester i både frontend och backend

26. /specs/Write on the scribblewall.feature

27. npm run test

28. /app/tests/step_definitions/Write on the scribblewall.js

29. zombie
browser

30. /app/tests/support/world.js

31. npm run test

32. /app/tests/step_definitions/Write on the scribblewall.js

33. npm run test

34. npm run test

35. /app/tests/step_definitions/Write on the scribblewall.js

36. /app/tests/step_definitions/Write on the scribblewall.js

37. npm run test

38. nock
mock

39. npm run test

40. HTML
JS

41. /app/tests/step_definitions/Write on the scribblewall.js

42. npm run test

43. /app/tests/step_definitions/Write on the scribblewall.js

44. npm run test

45. Slutsatser
● Ganska hög tröskel i början…
● … men värt det!
● Gränssnittstunga applikationer
● Logistiken från webben till kodbasen och vice versa är fortfarande knepig
● Skriva BDD-testerna är ett tungt jobb…
● … och bör inte göras av bara utvecklarna

46. Tack för mig!
Mail: viktor.sarstrom@evolvetechnology.se
Github: viktorlarsson
www.evolvetechnology.se