Please enable JavaScript.
Coggle requires JavaScript to display documents.
Testing Matters - Don't let users test your code, Testing Matters Too …
Testing Matters - Don't let users test your code
Unit Testing
Integration Testing
e2e Testing
Why?
Don't let users test you code
Test script take time to right and run though
Continuous Integration etc
your Confidance that shipped code is fully tested
Great to easily re-test when refactoring or updating code (new breaking or alt packages etc)
Good inpression to customers that it just works.
Fast, repeatable and consistant
Tools
Some include -out-of-the-box with productsion/frameworeks
Angular - e2e = Protractor
React?
Vue
Why Cypress?
Timemachine
Framework agnostic
API Testing builtin
Extensible via Javascript plusings
Paid offering
Up-to-Now alabout modern frameworks, but what about other stuff like regular HTML5 or even XPages. What about those?
Third party tools
Cypress
Others???
demos
Simple e2e demo
unit
integration
Data
Consistent and resettable - you've all got thight. Right?
Mocking/Faking
What not too test?
e2e
Everything - be selective and foccle on top 5 bits egc, menus and core functions
Integration
Everything, just key interactons, api, data feeds etc
Unit
Other colleagues unit code - they should test their own!
All of a third party lib, except for stuff we actively use
Questions: (to gauge interaction and level)
Who tests their code?
Manul script
Half way there alreayd!
Automated script
Pipeline test with automatic release?
Who does no specific testing other than a simple well it loads on my machine, and thus lets user test their code?
Rerports counts, and lets see if we can inprove thsi situation!
Giveaways
Rpi
Books
Methodology
Test Driven Development
Design Driven Development?
Other Types?
Intro - from this first
paragraph
Next step after 2e2 is CI Continuous
Integration
then CD Continuous Deployment
Testing Matters Too - Stop testing my code! (unit testing)