Replies: 2 comments 5 replies
-
|
I think a good test workflow for us is to have: 1 or 2 developer testing the API Consider that we need to do integration tests, end-to-end (e2e) and unit tests. We should be using the official Jest documentation for the most part to learn from, however there are a number of great tutorials. https://www.youtube.com/watch?v=5QRx-i5jVNw It might take doing a few tutorials to understand. I would not expect a single person to do all of our testing, but it will be a big benefit. If you are only able to test whether the element is present in the DOM, that is a good start. If you use Visual Studio Code or Visual Studio, there is a Jest extension you should install, just search for Jest in the marketplace and in the Extension search in VSCode. |
Beta Was this translation helpful? Give feedback.
-
|
There are tutorials, especially on Youtube that cover the topic of integration, unit and e2e testing as an overview, not Jest specific. I would also suggest looking at some of those. At some point we should require all tests pass before we merge. This will mean that before the PR gets sent, all required tests must pass, and when we review the PR, the tests must pass. We report back to the developer doing the PR, if there are any tests not passing. This will help us immensely with making sure that especially when we are adding new features, it will help keep from breaking changes, especially any new code that would break old code/features. |
Beta Was this translation helpful? Give feedback.
-
|
I found some more video resources: https://www.youtube.com/watch?v=9Yrd4aZkse8 |
Beta Was this translation helpful? Give feedback.
-
|
https://www.youtube.com/playlist?list=PLC3y8-rFHvwirqe1KHFCHJ0RqNuN61SJd <Playlist of 52 videos on Jest> I folllowed this playlist |
Beta Was this translation helpful? Give feedback.
-
|
it's pretty good. I am on the 4th video of the list |
Beta Was this translation helpful? Give feedback.
-
|
Yes I agree test at this point, is very important, as the app is really growing fast. But, it may be a bit tricky seeing that some of us are still new to test. Nevertheless, I'll begin looking into testing small parts of the app to understand what it is, and ultimately make more test contributions. |
Beta Was this translation helpful? Give feedback.
-
|
I am well aware people may be new to testing. We can start out making our testing simple and grow as needs come about and as people are learning testing. The more people we have that are able to at least understand testing the better our developer experience witll be. I suggest going through the tutorials I included here and doing a few of their examples to get some knowledge as well as videos/tutorials about unit testing, e2e testing and integration testing. Create React App gave us App.test.js which was meant to test the rendering of App.js, so it could ideally be used to test App.js itself. We should create a test folder in the most logical place, and install jest as a devDependency. with -D or --save-dev. I think we should also primarily be using Postman to test our API. |
Beta Was this translation helpful? Give feedback.
-
Hii @gbowne1
I am learning testing with jest....
I now ready with tesing the backend apis
But when it comes for frontend I am only clear to write the test about wheather the element is present in the DOM or not
I can't able to figure out how the fronted flow is tested with jest
Can you have any tutorials or blogs or documentation for Unit test
Wheather we have any Collabarator who knows testing?
Beta Was this translation helpful? Give feedback.
All reactions