Skip to content

Commit 406b7e8

Browse files
committed
add outline of integration tests workshop
1 parent 3744069 commit 406b7e8

1 file changed

Lines changed: 51 additions & 0 deletions

File tree

integration-tests.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,53 @@
11
# Integration tests
22

3+
- about webdev / testing
4+
- outline
5+
- unit tests recap
6+
7+
- integration tests motivation
8+
- unit tests for business logic
9+
- "testing integration of your own and third-party modules"
10+
- test components / modules / dependencies links
11+
- examples:
12+
- external library / dependency calls, function signatures
13+
- child DOM subtrees / components
14+
- API calls
15+
- file system calls
16+
- database calls
17+
- logging / tracking ?
18+
19+
- 90's books definitions
20+
- big bang approach
21+
- top-down (gradually un-mock more and more components)
22+
- bottom-up
23+
- sandwich (top-down + bottom-up)
24+
25+
- fowler's definitions and narrow vs broad integration tests
26+
27+
- best practices
28+
- separate unit / integration (and know the difference!)
29+
- integrate into ci
30+
31+
- snapshots demo
32+
- shallow vs mount
33+
- travis config
34+
35+
- cypress demo
36+
37+
38+
- concl
39+
- how to connect to backend for e2e tests?
40+
- use fake api service like Apiary
41+
- dockerized fake backend
42+
- requests to real backend on testing/production
43+
- what approach to integration tests should we take (common sense again)
44+
45+
- teaser for next week
46+
- more complex Cypress tests
47+
- adding Cypress to CI
48+
- automated E2E testing fails / history / future
49+
- user testing sessions
50+
51+
- resources
52+
- https://martinfowler.com/bliki/IntegrationTest.html
53+
- https://www.youtube.com/playlist?list=PLZ66c9_z3umNSrKSb5cmpxdXZcIPNvKGw

0 commit comments

Comments
 (0)