HackSoftware/Django-Styleguide
1
1
Fork 0
mirror of https://github.com/HackSoftware/Django-Styleguide.git synced 2024-11-11 04:06:46 +03:00
Code Issues Packages Projects Releases Wiki Activity

Highlight important rules of thumb

Browse Source
This commit is contained in:
Radoslav Georgiev 2021-09-25 19:26:23 +03:00
parent ce05847710
commit 7886bfa432
No known key found for this signature in database
GPG Key ID: 0B7753A4DFCE646D
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -470,9 +470,9 @@ Since services hold our business logic, they are an ideal candidate for tests.
If you decide to cover the service layer with tests, we have few general rules of thumb to follow:
1. The tests should cover the business logic behind the services in an exhaustive manner.
1. The tests should hit the database - creating & reading from it.
1. The tests should mock async task calls & everything that goes outside the project.
1. The tests **should cover the business logic** in an exhaustive manner.
1. The tests **should hit the database** - creating & reading from it.
1. The tests **should mock async task calls & everything that goes outside the project.**
When creating the required state for a given test, one can use a combination of: