GibCasa/GameServerSupervisor
3
0
Fork 1
Code Issues 7 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

unit-testing #19

Merged
calm-steam merged 5 commits from calm-steam/GameServerSupervisor:unit-testing into master 2025-02-18 19:07:38 +01:00
Conversation 1 Commits 5 Files Changed 3 +45 -12
calm-steam commented 2025-02-16 11:42:29 +01:00
Member
Copy Link

each feature branch should work on the unit tests of the files it touches.
I recommend writing the test of the functionality before implementing the feature (TDD).
tests for existing functionality should be written retroactively.

tests in django follow this scheme: https://docs.djangoproject.com/en/5.1/topics/testing/overview/

to note:

  • differentiating tests by test labels
  • test database handling

I recommend to organize unit tests by:
src/module/class
src/module/test_class

mirroring the project structure can lead to problems when restructuring the project.
keeping them in a separate directory makes it inconvenient to develop.

to consider:

  • avoid test database creation (use of mock)

HOW TO TEST

./manage.py test

each feature branch should work on the unit tests of the files it touches. \ I recommend writing the test of the functionality before implementing the feature (TDD). \ tests for existing functionality should be written retroactively. tests in django follow this scheme: https://docs.djangoproject.com/en/5.1/topics/testing/overview/ to note: - differentiating tests by test labels - test database handling I recommend to organize unit tests by: \ src/module/class \ src/module/test_class mirroring the project structure can lead to problems when restructuring the project. \ keeping them in a separate directory makes it inconvenient to develop. to consider: - avoid test database creation (use of [mock](https://medium.com/@sabya.nandy14/quick-unit-testing-of-django-models-with-mock-3fb0d966726c)) HOW TO TEST `./manage.py test`
calm-steam added 5 commits 2025-02-16 11:42:30 +01:00
pratyush approved these changes 2025-02-18 16:39:49 +01:00
calm-steam merged commit 8251fecf9a into master 2025-02-18 19:07:38 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
pratyush
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GibCasa/GameServerSupervisor#19
No description provided.
Delete Branch "calm-steam/GameServerSupervisor:unit-testing"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?