Skip to content

Commit

Permalink
Fix testing (#30)
Browse files Browse the repository at this point in the history
* break testing into backend and frontend

* remove duplicated text
  • Loading branch information
rasheedamir authored Jun 28, 2019
1 parent de9ca2d commit d08c1ac
Show file tree
Hide file tree
Showing 3 changed files with 34 additions and 28 deletions.
3 changes: 2 additions & 1 deletion .vuepress/config.js
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,8 @@ module.exports = {
{
title: 'Testing',
children: [
'/testing/testing'
'/testing/backend',
'/testing/frontend'
]
},
{
Expand Down
27 changes: 0 additions & 27 deletions testing/testing.md → testing/backend.md
Original file line number Diff line number Diff line change
Expand Up @@ -234,33 +234,6 @@ Tests should be automated as part of the build, release, run (delivery) pipeline

These three sets of tests, combined, should provide an extremely high level of confidence that any introduced change has not broken existing functionality.

# Frontend Testing (Microfrontends)

Usually question arises how to test frontend?

### 1 Unit Tests

- Business logic unit tests

### 2 Component Tests

- e.g. click on button should open a date picker

### 3 Integration Tests

- Most of the tests should be written at this level
- Test/verify the accepted user scenarios
- CDC from frontend to backend?

### 4 E2E Tests

- Recommended to use Cypress

### 5 Best Practices

- Test as a user; never test underlying implementation details; so, one can easily switch the technology
- https://testing-library.com/

# References

* https://martinfowler.com/articles/microservice-testing/
Expand Down
32 changes: 32 additions & 0 deletions testing/frontend.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# Frontend Testing (Microfrontends)

Usually question arises how to test frontend?

### 1 Unit Tests

- Business logic unit tests

### 2 Component Tests

- e.g. click on button should open a date picker

### 3 Integration Tests

- Most of the tests should be written at this level
- Test/verify the accepted user scenarios
- CDC from frontend to backend?

### 4 E2E Tests

- Recommended to use Cypress

### 5 Best Practices

- Test as a user; never test underlying implementation details; so, one can easily switch the technology
- https://testing-library.com/

# References

* https://martinfowler.com/articles/microservice-testing/
* https://www.thoughtworks.com/insights/blog/architecting-continuous-delivery
* https://vrockai.github.io/blog/2017/10/28/cypress-keycloak-intregration/

0 comments on commit d08c1ac

Please sign in to comment.