Skip to content

Automated testing strategy for backend #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
s1monj opened this issue Mar 31, 2025 · 1 comment
Open

Automated testing strategy for backend #48

s1monj opened this issue Mar 31, 2025 · 1 comment
Assignees
@travis-sauer-oltech
Labels
backend Python and SQL code

Comments

@s1monj
Copy link
Collaborator

s1monj commented Mar 31, 2025

  • Whatever is Django standard/minimum to achieve decent coverage for this kind of app
  • Don't need to write all the tests now but just start with a couple then we can work on the rest over the next few weeks/months
@s1monj s1monj added the backend Python and SQL code label Mar 31, 2025
@s1monj s1monj moved this to Ready in jupyterhealth-exchange Mar 31, 2025
@travis-sauer-oltech travis-sauer-oltech moved this from Ready to In Progress in jupyterhealth-exchange Apr 1, 2025
@travis-sauer-oltech
Copy link
Collaborator

travis-sauer-oltech commented Apr 20, 2025 •
edited
Loading

@s1monj

PR: #69

I was able to clean up some of my pagination logic with these tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@travis-sauer-oltech travis-sauer-oltech

Labels
backend Python and SQL code
Projects
jupyterhealth-exchange
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@s1monj @travis-sauer-oltech