End to end testing using Javascript

End-to-End Testing in Javascript has never been easier. Nightwatch.js and Cucumber.js when used as a whole seem to offer the perfect mix of specificity, expressivity, modularity and maintainability. Using such a lightweight toolchain for Javascript automation, one UI dev can easily switch to Automation dev without much of an effort. I share insights of my latest activity - a UI dev turned into a very passionate Automation dev, showing how both hats can easily be worn and switched seamlessly.

Transcript

3. https://github.com/glazar/e2e-testing
4. Do you use 'end-to-end' test to mean: 1) test of full infrastructure stack 2) test of entire customer workflow 26% Infrastructure 74% Workflow Katrina Clokie @katrina_tester
7. The most powerful delivery system ever invented for an idea is a story. Aaron Sorkin Daniel Pink @DanielPink
8. Work Experience
9. Work Experience
10. Work Experience
11. Don't worry about your title, just be the most useful person in the room, and the rest will follow. Molly Graham Peter Komornik @peterkomornik
12. Dev Experience
13. Learning is what most adults will do for a living in the 21st century. Perelman Woody Zuill @WoodyZuill
14. Good Experience
15. Good Experience
16. Good Experience
17. Cooperation is not quite the same as collaboration. Do we have different compatible goals or a shared goal? To me, that's the difference. AntonyMarcano @AntonyMarcano
18. Good Experience
19. Without automated testing, more code = more time & money for testing. In most cases, this is an unscalable business model. Gary Gruver Cory House @housecor
20. E2E Testing in JS
21. Nightwatch.js and Cucumber.js
23. Tests are specifications. They describe how the system should work. Seb Rose @sebrose
24. Nightwatch.js https://github.com/nightwatchjs/nightwatch
25. Nightwatch.js
26. Tests
27. Tags
28. Hooks
29. Page Objects
30. Page Objects
31. Custom Commands
32. Custom Commands
33. Screenshots
34. Parallel Execution of Tests
35. Cucumber.js https://github.com/cucumber/cucumber-js
36. Gherkin Based Specifications
37. Executable Specifications
38. Executable Specifications
39. BDD tools do not allow you to write specs using natural language; they allow you to read them using natural language. It's not the same. Kevlin Henney @KevlinHenney
40. Scenario Implementation
41. Scenario Implementation
42. Step Implementation
43. Feature Background
44. Scenario Outline
45. Tags
46. Hooks
47. Event Handlers
48. HTML Report with Screenshots
49. nightwatch-cucumber https://github.com/mucsi96/nightwatch-cucumber
50. Scenario Implementation
51. Scenario Implementation
52. Step Implementation
53. Step Implementation
54. Page Objects
55. Page Objects
56. Page Objects
57. Screenshots
58. HTML Report with Screenshots
59. Parallel Execution of Features
63. Work Experience
64. Automate repetitive tasks so testers can focus on: 1. Pair programming 2. Exploratory testing Not all testing can be automated. Seb Rose @sebrose
65. Ideal Dev & Test
66. Ideal Dev & Test
67. Ideal Dev & Test
68. To build great products, design features with scenarios - not requirements. Jonathan Abbett @jonabbett
69. E2E Testing in JS
70. E2E Testing in JS
71. Roadmap
72. Cross Browser Testing
73. Coverage Report
74. https://github.com/glazar/e2e-testing Code Examples
75. Code Examples https://github.com/glazar/e2e-testing