SpaceToStudy project is a platform where experts in various fields share their knowledge and students can learn from the best. Here you can find the proper training course, find a tutor, or find students and receive feedback from them.
[] [] []
- All the
coderequired to get started
- NodeJS (18.14.0 LTS)
- Clone this repo to your local machine
install npm packages
$ npm install- Open terminal.
- Run
npm run startto start application.* - Open http://localhost:3000 to view it in the browser.
* - to run the project you need an .env file in root folder
To run unit test open terminal and run npm run test in it.
- Redux
- For each entity we should have separate folder
- In each folder we should have different files for actions, reducer
{modelName}.actions.jsor{modelName}.reducer.js
- Configuration
- Configuration is done via
.envfile where environment variables are located
- Configuration is done via
- Styles
- For styling function
makeStylesfrom@material-uishould be used and all styles should be located inside separate component.
- For styling function
- Components
- Components that are connected to Redux should be located inside
containersfolder. Components without connection to Redux should be located insidecomponentsfolder. - Each individual page that is accessed via
react-routershould be located insidepagesfolder. All components that are used inside particular page should be located inside folder for the specific page. - Each component should have at least three files:
index.jswhere we export anything from the whole folder{component-name}.jsx- file where component is located{component-name}.styles.jswhere all styles are located
- Components that are connected to Redux should be located inside
Order of testing components:
- simple stateless components that are used in multiple places
- components that depends on other components but not connected to Redux and don’t have any state
- components that have internal state but are not connected to Redux
- components that connected to Redux
- third-party libraries
- constants
- static css styles
- related components (test only one specific component at the specific moment of time)
- testing using snapshots (actual ui)
- testing logic of component (dynamic)
Snapshots allow us to compare actual UI with saved one and throw an error if it has accidentally changed. We can use flag “updateSnapshot” to update save snapshots of a component. It is appropriate for presentational components but doesn’t cover any logic
- Properties
- default properties
- custom properties
- Data types (use library “jest-extended”)
- Conditions (what if)
- State
- default state
- state after some event has happened
- Events
- with parameters or custom props
- without arguments
Flow:
- Set up the conditions of our test
- Mock the actual HTTP requests
- Instruct the saga to run through everything and finish its business
- Check that the expected side effects have happened (actions are dispatched, selectors are called, etc)
Link to the full article about proper saga testing: https://dev.to/phil/the-best-way-to-test-redux-sagas-4hib#:~:text=To%20test%20that%20the%20saga,selector%20into%20the%20following%20gen.
We test action creators as simple pure functions that just take an arguments and output proper arguments
We test reducers as simple pure functions that just take an arguments and output proper arguments Checks:
- valid default state
- changes of state when action is dispatched for different values of state
- Use
data-cyas selector
You're encouraged to contribute to our project if you've found any issues or missing functionality that you would want to see. You can add in Issues tab and after that click on New issue. There you can see the list of issues and create a new issue after clicking on New Issue.
Before sending any pull request, please discuss requirements/changes to be implemented using an existing issue or by creating a new one. All pull requests should be done into develop branch.
There are two GitHub projects: Space2Study-node-Client-mvp for frontend part and Space2Study-node-BackEnd-mvp for backend part. Every project has it's own issues.
Every pull request should be linked to an issue. So if you make changes on frontend or backend parts you should create an issue with a link to corresponding requirement (story, task or epic). Every issue should have its own branch. Every branch name should start from task type (feature, bugfix or test), task number and short description. e.g. feature/125/create-adminPanel
All Pull Requests should start from prefix #xxx-yyy where xxx - task number and and yyy - short description e.g. #125-createAdminPanel
We have main , develop and feature branches.
All feature branches must be merged into develop branch!!!
Only the release should merge into the main branch!!!
.svg?cdnVersion=1312)
-
Option 1
- 👯 clone this repo to your local machine
-
Option 2
- create new branch from development branch
- add some commits to your new branch
- 🔃 create a new pull request in this repository
- go to Issues and click
New issuebutton
- when creating issue you should add name of the issue, description, choose assignee, label, project. If issue is a
User Storyyou should link it with corresponding tasks, and corresponding tasks should be linked to issue.
- if issue is in work it should be placed in proper column on dashboard according to its status.
- How do I do specifically so and so?
- No problem! Just do this.
- MIT license
- Copyright 2023 © SoftServe IT Academy.
